Pass the WGU Courses and Certificates Foundations-of-Computer-Science Questions and answers with CertsForce

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().

Ahypervisoris the software layer that enables virtualization—running multiple operating systems concurrently on the same physical hardware as separate, isolated virtual machines (VMs). Operating systems textbooks describe the hypervisor as managing and multiplexing core hardware resources such as CPU, memory, storage, and I/O devices among multiple guest operating systems. Each VM behaves as if it has its own hardware, while the hypervisor enforces isolation and schedules resource usage.

Hypervisors come in two broad categories.Type 1 (bare-metal)hypervisors run directly on the hardware (common in data centers), whileType 2 (hosted)hypervisors run as applications on top of a host OS (common on desktops). In both cases, the hypervisor is the key tool that makes “more than one OS at a time” possible.

System Restore is a recovery feature, not a virtualization platform. A partition manager can split a disk into multiple partitions, which can support dual-boot setups, but that runs only one OS at a time, not concurrently as VMs. A bootloader selects which OS to start at boot time; again, that is not simultaneous virtualization. Therefore, the correct tool that allows running multiple operating systems simultaneously as virtual machines is the hypervisor.

Python provides the built-in function `type()` to determine the data type (more precisely, the class) of an object. Because Python is dynamically typed, variable names are references to objects, and the object itself carries its type information at runtime. Calling `type(bmi)` returns a type object such as ``, ``, or `` depending on what value is currently bound to the name `bmi`. This is the standard, textbook-approved method for checking an object’s type in Python.

Option C, `typeof(bmi)`, is common in JavaScript, not Python. Options A and B are not standard Python built-ins; they might exist in user code or other languages, but not in Python’s core language. In typical coursework and professional usage, `type()` is the correct function.

Textbooks also discuss how `type()` differs from `isinstance()`. While `type()` directly reports the object’s class, `isinstance(bmi, float)` is often preferred when you want to allow subclass relationships. For example, in object-oriented programming, a subclass instance should often be treated as an instance of its parent class, which `isinstance` supports. However, when the question asks specifically for the function used to “check the data type,” the expected answer is `type()`.

# Understanding type inspection helps with debugging, writing robust functions, and reasoning about operations that are valid for different data types.

Selection sort is the algorithm that repeatedly scans the unsorted portion of a list to find the lowest (or highest) value and then places it into its correct position in the sorted portion. It begins at the first index (position 0) and treats that as the boundary between sorted and unsorted regions. On the first pass, it moves a scanning pointer through the entire list to determine the minimum element and swaps it into position 0. On the second pass, it starts from position 1, scans to the end to find the next minimum, and swaps it into position 1. This continues until the list is sorted.

This matches the question’s description: “starts at the first position and moves the pointer until the end of the list, determining the lowest value.” Textbooks often describe selection sort with two indices: one for the current boundary position and one for scanning the remainder of the list to find the minimum. The algorithm is simple and uses O(1) extra space, but it is inefficient for large lists because it performs O(n²) comparisons regardless of input order.

The other options are not standard algorithm names in typical computer science curricula. While many sorting algorithms exist (insertion sort, merge sort, quicksort, heap sort), “incremental,” “progressive,” and “pointer sort” are not canonical textbook algorithms in this context. Therefore, the correct answer is selection sort.

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.

NumPy arrays use zero-based indexing, meaning counting starts at 0 rather than 1. In a 2D NumPy array, indexing is typically written in the form array[row_index, column_index]. The first index selects the row, and the second index selects the column. Therefore, the “first row” corresponds to row index 0. Within that row, the “third element” corresponds to column index 2, because the columns are indexed 0, 1, 2, 3, and so on.

So, np_2d[0, 2] directly selects the element at row 0 and column 2, which is the third element in the first row. This is considered an “alternative” to approaches like two-step indexing (np_2d[0][2]), and it is the standard idiom taught for multi-dimensional NumPy arrays.

The other choices point to different locations. np_2d[1, 3] is the fourth element of the second row, not the third element of the first row. np_2d[2, 0] and np_2d[3, 1] attempt to access the third or fourth row, which would often be out of bounds in a small 2-row example and would raise an IndexError. Correct indexing is a cornerstone of array programming because it determines which observation, feature, or matrix entry your computations will use.

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.

In data structures and algorithms,traversalrefers to systematicallyvisiting nodesin a tree or graph in order to process them. “Visiting” typically means performing some operation at each node, such as reading its value, marking it as seen, computing a property, or collecting it into an output structure. Traversal is foundational because many algorithms—search, path finding, connectivity checks, topological analysis, and evaluation of expressions—are built on traversal patterns.

Intrees, traversal has classic forms: preorder, inorder, and postorder depth-first traversals, as well as breadth-first traversal (level-order). Each defines a rule for the order in which nodes are visited relative to their children. Ingraphs, traversal must additionally handle the possibility of cycles and multiple paths; textbooks therefore emphasize maintaining a “visited” set to avoid infinite loops. The two principal graph traversal strategies areDepth-First Search (DFS)andBreadth-First Search (BFS). DFS explores along a path as far as possible before backtracking, while BFS explores layer by layer outward from a start node.

Options A, B, and C do not define traversal. Changing values may happen during traversal, but it is not what traversal means. Removing all nodes is deletion, not traversal. Connecting all nodes is not a standard traversal concept. The correct definition is the process of visiting all nodes (typically reachable from a starting node, or all nodes in the structure if fully connected).

A central rule in NumPy is that an ndarray has a single, fixed data type called itsdtype. That dtype is chosen when the array is created (for example, int64, float64, etc.), and it normally does not change just because you assign a new value into one element. When you attempt an assignment, NumPy tries tocastthe assigned value into the array’s existing dtype. If the cast is possible, the assignment succeeds; if the cast is impossible, NumPy raises an error.

So, if you have a numeric array such as arr = np.array([1, 2, 3]), its dtype is an integer type. Trying arr[0] = "hello" cannot be converted into an integer, so NumPy raises a ValueError (a casting/conversion error). This is exactly the behavior textbooks highlight when contrasting NumPy arrays with Python lists: lists can hold mixed types freely, but NumPy arrays trade that flexibility for speed and memory efficiency via uniform typing.

Option A is a common misconception. While NumPy may “upcast” values to a more general dtype at array creation time when mixed types are provided (e.g., numbers and strings in the same constructor), a pre-existing numeric array will not automatically convert itself into a string array during a single-element assignment. Options C and D do not reflect NumPy’s assignment rules.

A linked list is a dynamic data structure made up of nodes, where each node typically contains two components: a data field (the value being stored) and a link field (commonly called a pointer or reference). The pointer’s role is to store the memory address (or reference) of the next node in the sequence, thereby maintaining the logical order of the list even though nodes may be scattered throughout memory. This is a key contrast with arrays, which store elements contiguously and rely on index arithmetic to locate the next element.

Because each node explicitly points to the next node, linked lists support efficient insertion and deletion operations compared with arrays. To insert a node, you allocate it and then adjust pointers so it fits into the chain. To delete a node, you redirect the pointer of the previous node to skip over the removed node. Traversal is performed by starting at the head node and repeatedly following the pointer until a null reference indicates the end of the list.

The other options do not correctly describe what stores the location of the next node. An index is used in array-like structures, not in a standard linked list node. The value is the payload data, not the link. The “header” (often called the head pointer) is an external reference to the first node, not the field inside each node that links to the next. Therefore, the correct answer is the pointer.