Foundations-of-Computer-Science Exam Dumps - WGU Courses and Certificates Questions and Answers

Python usesdynamic typing, a core concept emphasized in programming language textbooks. In dynamically typed languages, a variable name does not permanently “own” a type. Instead, theobjectcreated by an expression has a type, and the variable becomes a reference to that object. Therefore, the type associated with a variable at any moment is determined by the value assigned to it. For example, after x = 7, x refers to an integer object. After x = "seven", the same name now refers to a string object. The type changes because the binding changes, not because the variable’s type declaration was edited.

Option A describesstatic typingsystems (common in languages like Java, C, or C++), where programmers declare types and compilers enforce them. Python does not require such declarations for ordinary variables. Option B is incorrect because type assignment is deterministic, not random. Option C is incorrect because Python does not default variables to strings; it assigns whatever type results from the right-hand-side expression.

This model is closely tied to Python’s runtime behavior: type checks occur during execution, and functions can accept values of different types as long as the operations used are valid (often discussed as “duck typing”). This flexibility supports rapid development, but also motivates careful testing and, in larger systems, optional type hints for documentation and tool support.

TheHardware Abstraction Layer (HAL)is a software layer that sits between the operating system kernel and the physical hardware. Its purpose is to hide hardware-specific details behind a consistent interface, allowing the OS to be more portable and easier to maintain across different hardware platforms. Textbooks explain that without abstraction, the OS would need extensive device- and architecture-specific code scattered throughout the kernel, making updates and cross-platform support far more difficult.

The HAL typically provides standardized functions for interacting with low-level components such as interrupts, timers, memory mapping, and device I/O. With a HAL, the OS can call general routines (for example, to configure an interrupt controller) while the HAL handles the platform-specific implementation. This supports a key systems principle: separate policy (what the OS wants to do) from mechanism (how hardware accomplishes it).

The other options are not correct. A boot loader runs at startup to load the operating system into memory; it is not the general interface layer during normal operation. The task scheduler is a kernel subsystem that manages CPU time among processes, not a hardware-independence layer. The file system layer manages storage organization and access semantics; it is not the general abstraction for all hardware interactions.

Therefore, the programming layer that enables generalized OS interaction with hardware is the hardware abstraction layer.

Python provides built-in type conversion functions that construct a value of a target type from a supplied object when possible. To convert an integer to a string, Python uses the constructor function str(). For example, str(42) produces the string "42". This operation is fundamental in programming textbooks because it enables tasks like formatting output, concatenating numbers into messages, building file names, or preparing numeric values for text-based storage and transmission.

Python distinguishes clearly between numeric types (int, float) and text type (str). You cannot concatenate an integer directly with a string (e.g., "Age: " + 30 raises a TypeError) because the types are different. Using str(30) resolves this by converting the integer into its string representation: "Age: " + str(30) becomes valid. Modern Python commonly uses f-strings (f"Age: {30}"), which perform conversion automatically, but str() remains the canonical and explicit method.

Options A, B, and C are not standard Python built-ins for conversion. While some libraries define helper functions with similar names, the language’s standard approach is str(...). Textbooks also highlight that str() is not limited to integers: it can convert many objects into readable string representations, often by invoking the object’s __str__ method. This ties conversion to Python’s object model and supports consistent display and logging across programs.

NumPy arrays are not a built-in Python data structure. In a default Python installation, the interpreter includes core types such as int, float, str, list, tuple, dict, and set, plus the standard library. A NumPy array, typically created as numpy.ndarray, is provided by the third-party NumPy library. Therefore, if a “default Python configuration” does not recognize a NumPy array, the most likely cause is thatNumPy is not installed or not available in the active environment. This happens often when a user has multiple Python environments (system Python, virtual environments, conda environments) and installs NumPy into one environment while running code in another.

Option B is incorrect because Python’s standard-library array module is different from NumPy. Importing array does not create or enable NumPy’s ndarray type. Option C is possible in rare cases,but the typical, textbook-aligned explanation is missing dependencies rather than an incorrectly configured interpreter. Option D is also unlikely: while very old Python versions may cause compatibility issues with modern NumPy releases, the symptom described—NumPy arrays not being recognized at all—more directly indicates the package is absent in the running environment.

In practice, verifying import numpy and checking the installed packages for the current interpreter resolves the issue.

Python lists are mutable sequences, which means elements can be changed in place after the list has been created. The expression list1[0] = "California" uses indexing to target the element at position 0 (the first element, because Python uses zero-based indexing) and assignment (=) to replace that element with a new value. As a result, the list keeps the same length, but its first entry becomes "California".

This operation does not create a new list (so option A is incorrect); it modifies the existing list object referenced by list1. It also does not append to the end of the list (so option C is incorrect). Appending would use methods like list1.append("California"). Option D is not meaningful in Python list semantics; assignment to a single index replaces exactly one element rather than “adding a second element to the line.”

Textbooks highlight this difference between mutable and immutable sequence types. For example, strings are immutable, so you cannot assign to some_string[0]. Lists, however, are designed for collections that change over time, supporting updates, insertions, deletions, and reordering. Index assignment is fundamental for many algorithms: updating an array-like buffer, modifying a dataset row, replacing incorrect values, or implementing in-place transformations efficiently.

Reshaping is the operation of changing the “view” of an array so that the same elements are arranged with new dimensions. In NumPy, reshaping is possible when the total number of elements stays the same. A 2x3 array contains 6 elements, so a 1D array data of length 6 can be reshaped into shape (2, 3) without adding or removing values. Textbooks stress this invariant: the product of the dimensions must equal the original size.

NumPy provides two standard reshaping interfaces: the function np.reshape(data, (2, 3)) and the method data.reshape(2, 3) (or data.reshape((2, 3))). Option A is correct because it uses the official NumPy function with the proper arguments: the original array and the target shape. The shape is passed as a tuple describing rows and columns.

Option B is incorrect because np_reshape is not the correct NumPy function name, and it references an unrelated identifier list. Option C is incorrect because NumPy arrays do not provide a set_shape method like that. Option D is not valid NumPy syntax for reshaping.

Reshaping is fundamental in data analysis and machine learning: it converts flat vectors into matrices, prepares batches of samples, and aligns dimensions for matrix multiplication and broadcasting.

Python is a dynamically typed language, meaning variables do not require explicit type declarations; instead, objects carry type information at runtime. To inspect the type of an object, Python provides the built-in function type(). When you pass a variable or value into type(), it returns the object’s class, which represents its data type. For example, type(5) returns , type(3.14) returns , and type("hello") returns . This is commonly used in debugging, learning exercises, and when writing functions that must behave differently depending on input types.

Textbook discussions often pair type() with Python’s object model: everything in Python is an object, and each object is an instance of some class. type() reveals that class. In addition, type() can be used in more advanced ways, such as dynamic class creation, but its foundational educational use is type inspection.

The other options are not correct because GetVar(), Show(), and Data() are not standard Python built-ins for type checking. While developers can define functions with those names, they are not part of Python’s core language or standard library in the sense required by the question. For typical coursework and professional Python usage, the correct and universally accepted function is type().

In a 2D NumPy array, indexing is written as array[row_index, column_index] using zero-based indices. The array np_2d = np.array([[1, 2, 3, 4], [10, 20, 30, 40]]) has two rows (indices 0 and 1) and four columns (indices 0, 1, 2, 3). The value 40 is located in the second row and the fourth column. Using zero-based indexing, that corresponds to row index 1 and column index 3. Therefore, np_2d[1, 3] returns 40.

Option A attempts to access row 3, which does not exist and would raise an IndexError. Option C attempts to access column 4 in row 0, but valid column indices are only 0 through 3, so it would also error. Option D likewise refers to a non-existent row 4. Only option B uses valid indices and points to the correct location.

Textbooks emphasize multi-dimensional indexing because it underlies matrix operations, dataset manipulation, and feature extraction in data science. Correctly interpreting rows and columns is essential when rows represent observations (like people) and columns represent attributes (like age, weight, height). This question tests precise control over row/column addressing, which prevents subtle bugs in numerical analysis.

Selection sort works by growing a sorted portion of the list one element at a time. The algorithm conceptually divides the array into two regions: asorted prefixon the left and anunsorted suffixon the right. At the beginning, the sorted prefix is empty and the entire list is unsorted. The first step is to consider position 0 as the target location for the smallest element. The algorithm scans the unsorted region (initially the whole list) tofind the smallest valueand records its index. That action is exactly what option C describes: determine the lowest value starting from the first position.

After identifying the minimum element, selection sort swaps it into position 0 (if it isn’t already there). Then it repeats the process for position 1, scanning the remaining unsorted suffix to find the next smallest element, swapping it into place, and so on. Textbooks emphasize that the key characteristic of selection sort is the repeated “select min (or max) from unsorted region and place it into the sorted region.”

Option A is not the standard first step; finding both min and max is unnecessary. Option B describes an unrelated swap that doesn’t ensure progress toward sorting. Option D is not a “first step” but rather a different ordering goal; selection sort can be adapted for descending order, but the canonical version begins by selecting the minimum for the first position.

NumPy slicing uses the same start/stop rules as Python sequences, and it also supports negative indices to count from the end. In a 2D array, slicing is written as array[rows, columns]. To get thelast two rows, you use -2: in the row position, meaning “start two rows from the end and go to the end.” Similarly, to get thelast two columns, you use -2: in the column position. Combining these gives array[-2:, -2:], which selects the bottom-right 2×2 subarray.

Option A, array[-2:, :], selects the last two rows butall columns, so it is not restricted to the last two columns. Option D, array[:, -2:], selects all rows but only the last two columns. Option B, array[-1:, -1:], selects only the last row and the last column, producing a 1×1 (or 1×1 view) subarray, not a 2×2.

This kind of slicing is widely taught because it is essential for matrix operations, extracting submatrices, working with sliding windows, and manipulating image or time-series data where “take the last k observations/features” is common. Negative indexing reduces errors and makes code clearer, especially compared with computing explicit indices like array[rows-2:rows, cols-2:cols].