Free Practice Questions for the WGU Courses and Certificates Data-Management-Foundations Exam (2026 Updated)

An attribute type refers to a single, specific value within a table, such as Salary, Age, or Price.

Example Usage:

A screenshot of a computer AI-generated content may be incorrect.

CREATE TABLE Employees (

EmpID INT PRIMARY KEY,

Name VARCHAR(50),

Salary DECIMAL(10,2)

);

Salary is an attribute type with individual values for each employee.

Why Other Options Are Incorrect:

Option A (Glossary) (Incorrect): Refers to documentation , not database values.

Option B (Entity type) (Incorrect): Represents a class of objects (e.g., Employees), not individual values.

Option D (Relationship) (Incorrect): Defines connections between entities , not attributes.

Thus, the correct answer is Attribute type , as it represents an individual data value .

A Transaction Manager ensures ACID (Atomicity, Consistency, Isolation, Durability) properties in database transactions. It manages concurrent transactions, ensuring no conflicts occur and logs modifications to support recovery mechanisms.

Option A (Incorrect): Query optimization is managed by the query processor , not the transaction manager.

Option B (Incorrect): The transaction manager is a component of the database architecture but is not composed of the entire system (query processor, storage manager, etc.).

Option C (Correct): The transaction manager logs transactions like INSERT, UPDATE, and DELETE, ensuring consistency and recoverability.

Option D (Incorrect): The storage manager is responsible for translating queries into file system commands.

An aggregate function performs a calculation over multiple rows and returns a single value . Examples include SUM(), AVG(), MAX(), MIN(), and COUNT() in SQL.

Option A (Correct): Aggregate functions compute values over a set of rows , like summing total sales or averaging grades.

Option B (Incorrect): Selecting rows that appear in one table but not another is done using set operations (EXCEPT or MINUS in SQL) .

Option C (Incorrect): Eliminating columns is done using the PROJECT operation or SELECT with specific columns .

Option D (Incorrect): Combining rows from two tables refers to a JOIN operation , not aggregation.

This query performs a join operation where records from the Make table and Model table are combined based on the condition Make.ModelID = Model.ID. This condition tests for equality , which is the definition of an EQUIJOIN .

Types of Joins in SQL:

EQUIJOIN (Correct Answer) :

Uses an equality operator (=) to match rows between tables.

Equivalent to an INNER JOIN ON condition.

Example:

sql

SELECT *

FROM Employees

JOIN Departments ON Employees.DeptID = Departments.ID;

NON-EQUIJOIN (Incorrect) :

Uses comparison operators other than = (e.g., < , > , BETWEEN).

Example:

sql

SELECT *

FROM Employees e

JOIN Salaries s ON e.Salary > s.MedianSalary;

SELF JOIN (Incorrect) :

A table is joined with itself using table aliases.

Example:

sql

SELECT e1.Name, e2.Name AS Manager

FROM Employees e1

JOIN Employees e2 ON e1.ManagerID = e2.ID;

CROSS JOIN (Incorrect) :

Produces Cartesian product (each row from Table A combines with every row from Table B).

Example:

sql

SELECT *

FROM Employees

CROSS JOIN Departments;

Thus, since our given query uses an equality condition (=) to join two tables , it is an EQUIJOIN .

Cardinality defines the minimum and maximum number of occurrences of one entity in relation to another.

Example Usage in an ER Model:

One-to-Many (1:M) : A customer can place multiple orders , but each order belongs to only one customer.

Customers (1) ——— (M) Orders

Cardinality notation:

(1,1) → One-to-One

(0,M) → Zero-to-Many

(1,M) → One-to-Many

Why Other Options Are Incorrect:

Option B (Physical design) (Incorrect): Focuses on storage and indexing , not relationships.

Option C (Attribute minimum) (Incorrect): No such formal term in database modeling.

Option D (Partition) (Incorrect): Refers to dividing tables , not relationship constraints.

Thus, the correct answer is Cardinality , as it defines min/max constraints on relationships .

A relationship in an ER model defines how two separate entities interact .

Example Usage:

A screenshot of a computer AI-generated content may be incorrect.

CREATE TABLE Customers (

CustomerID INT PRIMARY KEY,

Name VARCHAR(50)

);

CREATE TABLE Orders (

OrderID INT PRIMARY KEY,

CustomerID INT,

FOREIGN KEY (CustomerID) REFERENCES Customers(CustomerID)

);

Customers and Orders are separate entities , related via CustomerID.

Why Other Options Are Incorrect:

Option A (Reflexive relationship) (Incorrect): Used for self-referencing entities , not two different entities.

Option B (Entity type) (Incorrect): Defines a class of objects , but does not establish relationships.

Option D (Attribute) (Incorrect): Attributes describe entities but do not connect them.

Thus, the correct answer is Relationship , as it connects two separate entities .

In a one-to-many (1:M) relationship , the foreign key is placed in the table on the "many" side to establish the relationship with the primary key of the "one" side.

Example Usage:

A screenshot of a computer AI-generated content may be incorrect.

CREATE TABLE Departments (

DeptID INT PRIMARY KEY,

DeptName VARCHAR(50)

);

CREATE TABLE Employees (

EmpID INT PRIMARY KEY,

Name VARCHAR(50),

DeptID INT, -- Foreign key on the "many" side

FOREIGN KEY (DeptID) REFERENCES Departments(DeptID)

);

Each department can have many employees → DeptID is a foreign key in Employees.

Why Other Options Are Incorrect:

Option A (Reflexive relationship) (Incorrect): Refers to unary (self-referential) relationships , not 1:M relationships.

Option B (Binary relationship) (Incorrect): A binary relationship involves two entities , but does not define where the foreign key is stored.

Option C (Weak entity) (Incorrect): Weak entities depend on a strong entity , but not all "many" sides are weak entities.

Thus, the correct answer is Foreign key , as it is placed on the "many" side of the relationship.

A primary key uniquely identifies each row in a table. When a primary key consists of only one field , it is called a Simple Primary Key .

Types of Primary Keys:

Simple Primary Key (Correct Answer):

Contains only one column .

Example:

sql

CREATE TABLE Students (

StudentID INT PRIMARY KEY,

Name VARCHAR(50)

);

Composite Primary Key:

Uses multiple columns to ensure uniqueness.

Example:

sql

CREATE TABLE Orders (

OrderID INT,

ProductID INT,

PRIMARY KEY (OrderID, ProductID)

);

Surrogate Primary Key:

A system-generated unique identifier (e.g., UUID or AUTO_INCREMENT).

Why Other Options Are Incorrect:

Option B (Duplicate) (Incorrect): A primary key must be unique , so it cannot be duplicate .

Option C (Numeric) (Incorrect): While primary keys can be numeric , they can also be alphanumeric (VARCHAR).

Option D (Composite) (Incorrect): A composite key consists of multiple fields , whereas a simple key is a single field .

Thus, the correct answer is Simple , since a one-field primary key is a simple primary key.

A valid SELECT statement in SQL follows this basic syntax:

sql

SELECT column1, column2

FROM table_name

WHERE condition;

The correct option D follows this syntax correctly .

Why Other Options Are Incorrect:

Option A (Incorrect): SQL does not use double quotes (") around column/table names unless explicitly required in some databases.

Option B (Incorrect): The WHERE clause must appear after the FROM clause .

Option C (Incorrect): ALL is not a valid keyword in standard SQL queries.

Thus, Option D follows the correct SQL syntax.

To add a primary key constraint after table creation , we use the ALTER TABLE statement.

Example Usage:

sql

ALTER TABLE Employees

ADD CONSTRAINT PK_Employees PRIMARY KEY (EmpID);

This adds a primary key to the EmpID column after the table was created .

Why Other Options Are Incorrect:

Option B (CREATE TABLE) (Incorrect): Used for defining constraints during table creation, not after.

Option C (UPDATE) (Incorrect): Modifies row values , not constraints.

Option D (INSERT INTO) (Incorrect): Used to add data to a table, not modify constraints.

Thus, the correct answer is ALTER TABLE , as it modifies table structure to add a primary key constraint .

An index scan is a database operation that quickly locates table blocks using an index rather than scanning the entire table. It significantly improves query performance.

Example Usage:

sql

SELECT * FROM Employees WHERE EmployeeID = 105;

If EmployeeID is indexed , the database uses an index scan to quickly find the record .

Why Other Options Are Incorrect:

Option A (Binary search) (Incorrect): A searching algorithm, but not a database operation.

Option B (Table scan) (Incorrect): Scans the entire table , which is slower than an index scan.

Option C (Fan-out) (Incorrect): Refers to branching in B-Trees but does not locate table blocks directly .

Thus, the correct answer is Index scan , as it efficiently locates table blocks.

Attributes in a database represent the properties (names, values, or characteristics) of an entity .

Example Usage:

In a Students table, attributes might include:

StudentID (Primary Key), Name, Age, Major

Here, Name is an attribute describing the entity Student .

Why Other Options Are Incorrect:

Option A (Synonyms) (Incorrect): Synonyms in SQL allow different names for the same object but are not attributes .

Option C (Repositories) (Incorrect): A repository stores data but does not define attributes .

Option D (Relationships) (Incorrect): Relationships define connections between entities , not their attributes.

Thus, the correct answer is Names , as attributes define entity properties .

The WHERE clause is used in SQL SELECT statements to limit the number of rows that match a specific condition. It helps filter data based on given criteria before retrieving the results.

Example Usage:

sql

SELECT *

FROM Employees

WHERE Salary > 50000;

This query limits the result set to employees whose salary is greater than 50,000 .

Why Other Options Are Incorrect:

Option A (FROM) (Incorrect): Specifies the table from which data is retrieved but does not limit results .

Option B (DROP) (Incorrect): Used for deleting tables, databases, or views , not filtering rows.

Option C (INTO) (Incorrect): Used in statements like INSERT INTO or SELECT INTO, which do not filter results .

Thus, WHERE is the correct keyword for applying a limiter in a SELECT statement .

A Full Join (FULL OUTER JOIN) selects all records from both tables , filling in NULL values where there is no match. This ensures that no data is lost from either table.

Example Usage:

sql

SELECT Employees.Name, Departments.DepartmentName

FROM Employees

FULL OUTER JOIN Departments ON Employees.DeptID = Departments.ID;

This query retrieves all employees and all departments , even if an employee has no assigned department or a department has no employees .

Types of Joins:

FULL OUTER JOIN (Correct Answer) → Includes all rows from both tables , filling missing values with NULL.

LEFT JOIN (Incorrect) → Includes all rows from the left table and matching rows from the right table .

RIGHT JOIN (Incorrect) → Includes all rows from the right table and matching rows from the left table .

CROSS JOIN (Incorrect) → Produces a Cartesian product (each row from one table is combined with every row from another table).

Thus, the correct answer is FULL JOIN , which ensures that all rows from both tables appear in the result .

A tangible entity is a real-world object that can be measured and stored in a database.

Example Usage:

In an inventory system, tangible entities include:

Products, Orders, Customers

Why Other Options Are Incorrect:

Option A (Logical entity) (Incorrect): Exists logically but may not have a physical presence (e.g., views, categories ).

Option C (Virtual entity) (Incorrect): Exists only in queries or reports , not stored as real data.

Option D (Conceptual entity) (Incorrect): Abstract idea used in design modeling , not a stored entity .

Thus, the correct answer is Tangible entity , as it represents measurable, real-world objects .