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

A hash table is a data structure that supports fast lookup, insertion, and deletion by using ahash functionto map keys to positions in an underlying storage structure. In Python, the built-in data structure that provides hash-table behavior is thedictionary, written with curly braces like {"a": 1, "b": 2}. Dictionaries store key–value pairs and are designed so that accessing a value by key, such as d["a"], is efficient on average. Textbooks typically describe this expected efficiency as average-case constant time, often written as O(1), assuming a good hash function and a well-managed table size.

Tuples and lists are sequence types. Lists provide indexed access by integer position, not hashing by arbitrary keys. Tuples are immutable sequences and likewise do not provide key-based hashing semantics. “Array” is not the core built-in mapping structure in Python; while Python has an array module and NumPy has arrays, neither is the built-in hash table abstraction for general key–value storage.

Python dictionaries require keys to be hashable, meaning the key’s hash value is stable during its lifetime (common examples: strings, numbers, tuples of hashable items). This requirement is directly tied to hash-table implementation. Dictionaries are used throughout computer science applications: symbol tables in interpreters, caches and memoization, frequency counting, indexing, and implementing graphs via adjacency maps.

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.

In programming, a function takes inputs, performs computation, and may return an output. The standard term for a function’s inputs isarguments(also commonly discussed alongside the closely related termparameters). Textbooks typically distinguish the two:parametersare the names listed in the function definition, whileargumentsare the actual values supplied when the function is called. For example, in def f(x, y):, x and y are parameters. In the call f(3, 5), 3 and 5 are arguments. Many introductory materials use “arguments” informally to refer to the inputs overall, which matches the wording of this question.

Options A, B, and C do not fit the textbook definition. “Variables” is too broad; inputs can be literals, expressions, or variables, but the conceptual role is “arguments.” “Procedures” are callable units of code (often used in some languages to mean functions without return values), not the inputs. “Outputs” refers to returned results, not what you pass in.

Understanding arguments is important because it connects to call semantics, scope, and correctness. Different languages support positional arguments, keyword arguments, default values, and variadic arguments (e.g., *args, **kwargs in Python). This flexibility shapes API design and influences how programmers structure reusable code.

Quicksort is a divide-and-conquer sorting algorithm. It works by selecting a pivot element, partitioning the array into two subarrays (elements less than the pivot and elements greater than the pivot), and then recursively sorting those subarrays. In the average case, the partition step splits the array into roughly equal halves, so the recurrence is commonly written as (T(n) = T(n/2) + T(n/2) + O(n)), where (O(n)) is the cost of partitioning. This solves to (O(n \log n)), which is why quicksort is widely taught as an efficient general-purpose sorting method.

However, textbooks also emphasize that quicksort has a worst-case time complexity of (O(n^2)) when partitions are extremely unbalanced (for example, repeatedly choosing the smallest or largest element as the pivot on already sorted input). Practical implementations reduce the likelihood of worst-case behavior using randomized pivots or “median-of-three” pivot selection. Despite the worst-case, quicksort is often very fast in practice because it has good cache performance and low constant factors, and it sorts in place with only (O(\log n)) average recursion stack space.

Among the provided options, the correct expected complexity for quicksort (average-case, and commonly cited in coursework questions) is (O(n \log n)). The other options are too small to represent the cost of sorting arbitrary data.

Python has a built-in boolean type named bool, which has exactly two values: True and False. These are language keywords/constants and are case-sensitive. Therefore, the correct representation of a boolean value is True (capital T, lowercase rest) or False (capital F). This is consistently taught in introductory programming textbooks because it affects conditional statements (if, while), logical operations (and, or, not), and comparisons.

Option A, "True", is a string literal, not a boolean. While it visually resembles the boolean constant, it behaves differently: non-empty strings are “truthy” in conditions, but "True" == True is false because they are different types (str vs bool). Option B, "true", is also a string, and it differs in casing as well. Option D, true, is not valid in Python; it will raise a NameError unless a variable named true has been defined.

Textbooks also stress that boolean values often result from comparisons, such as x > 0, and that booleans are a subtype of integers in Python (True behaves like 1 and False like 0 in arithmetic contexts). Still, their primary use is representing logical truth values for control flow and decision-making.

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

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.

The NumPy library provides arrays and efficient numerical operations, including sorting. However, NumPy doesnotprovide a function named np.quicksort. That is the API misuse in the code, making option A the correct answer. In NumPy, sorting is commonly performed using np.sort(arr) (which returns a sorted copy) or arr.sort() (which sorts in-place). If a specific algorithm is desired, NumPy exposes it through the kind parameter, such as np.sort(arr, kind="quicksort"), kind="mergesort", or kind="heapsort". Textbooks present this as a typical design: a single sorting interface with selectable strategies, rather than separate top-level functions per algorithm name.

Option C is correct and necessary: import numpy as np is standard convention. Option B is also correct: printing a variable is valid assuming it exists. Option D, written as arr = np.array([3, 2, 0, 1]), is valid NumPy usage for constructing a 1D array from a Python list.

A subtle point taught in scientific computing courses is that library APIs matter as much as syntax: you can write perfectly valid Python that still fails if you call a function that the library does not define. In this case, the fix is to replace np.quicksort(arr) with np.sort(arr) or np.sort(arr, kind="quicksort") depending on whether you need to specify the algorithm.

The primary advantage of NumPy arrays in data analysis is their support for fast, vectorized computation over whole collections of numeric data. A NumPy `ndarray` stores elements in a contiguous memory block with a single, fixed data type, enabling efficient low-level operations implemented in optimized C/Fortran code. As a result, expressions like `arr + 5`, `arr * arr`, or `np.mean(arr)` operate over the entire array without explicit Python loops. This style is commonly called **vectorization**, and it is a central theme in scientific computing textbooks because it is both clearer to read and significantly faster for large datasets.

Option A describes a property of Python lists, not NumPy arrays. Python lists can mix types freely, but this flexibility comes with overhead. Option B is true—NumPy arrays typically hold a single dtype—but it is not the main advantage; it is more of an implementation feature that enables speed and memory efficiency. Option D is not a defining advantage; both lists and arrays can be concatenated, and NumPy provides dedicated functions such as `np.concatenate`, but concatenation is not the core reason NumPy dominates data analysis workflows.

# Because NumPy operations are applied element-wise across entire arrays and can leverage CPU vector instructions and efficient memory access patterns, they form the foundation for higher-level tools like pandas, SciPy, and many machine learning libraries. This is why the best answer is that NumPy arrays can perform calculations over entire collections of values.

Operating systems contain many files that are essential for booting, hardware support, security enforcement, and core services. These are generally referred to assystem files. Textbooks explain that system files are often protected by permissions and special attributes because accidental modification or deletion could destabilize the OS, break device drivers, prevent applications from running, or even stop the machine from booting. Therefore, standard (non-administrator) users are typically restricted from accessing or altering them, and the OS may hide them by default to reduce the risk of user error.

Examples include kernel-related components, shared libraries, driver files, configuration databases, and critical service executables. Modern OS designs enforce protection through user accounts, access control lists, and privilege separation. This ensures only trusted processes and administrators can change system-critical components.

Log files record events and are sometimes protected, but many logs are readable by users or administrators depending on policy; they are not necessarily “meant to be inaccessible” in the same strict sense. Backup files are important for recovery but are not inherently system-critical for day-to-day operation, and their accessibility depends on organizational policy. “Extension files” is not a standard category; file extensions describe formats rather than a protected functional class.

Thus, the files intended to be inaccessible to standard users yet critical for functionality are system files, reflecting core OS security principles such as least privilege and integrity protection.