Data Management - Foundations (D426) Exam Topics and Questions
These WGU Data Management - Foundations (D426) exam topics are organized according to official exam domains to help candidates quickly verify coverage and focus on assessment rather than theory. Each domain is paired with topic-wise Data Management - Foundations (D426) sample questions that reflect how objectives are tested in the actual exam. This structure enables efficient review, targeted self-assessment, and rapid identification of weak areas when preparing for the WGU Data Management - Foundations Exam certification exam.
Let's Practice Free WGU Data Management - Foundations (D426) Questions Aligned with Official Exam Topics
SQL query writing is the most hands-on section of this exam, and it is where candidates who know the theory but have skipped practice pay the price. The domain tests whether you can read a statement and predict what it does, construct the right clause for a given requirement, and spot the mistake in a statement that almost works. Expect SELECT with filtering and sorting, INSERT, UPDATE, DELETE, and aggregate functions. Knowing syntax alone is not enough; you need to...
SQL query writing is the most hands-on section of this exam, and it is where candidates who know the theory but have skipped practice pay the price. The domain tests whether you can read a statement and predict what it does, construct the right clause for a given requirement, and spot the mistake in a statement that almost works. Expect SELECT with filtering and sorting, INSERT, UPDATE, DELETE, and aggregate functions. Knowing syntax alone is not enough; you need to trace execution order mentally.
How Running SQL queries to create and manipulate data is tested
Items in this area present a scenario, a table structure, and a SQL statement, then ask you to identify the output, diagnose the error, or choose the statement that meets the requirement. The trap is in clauses that look correct but execute in the wrong order, or WHERE conditions that filter more or fewer rows than intended.
Items reward candidates who understand how the database engine processes a query: FROM before WHERE, WHERE before GROUP BY, GROUP BY before HAVING, and SELECT near last. Misreading that sequence is the single most common source of wrong picks. Aggregate functions paired with GROUP BY are especially productive territory for item writers, because the logic is easy to misread under time pressure. Read every statement from the inside out, not top to bottom, and check what the result set actually contains before committing to an answer.
The ITExamsTopics practice test covers SQL query scenarios across the full range of statement types. Working through a large bank lets you spot the clause combinations you consistently misread, which is more efficient than re-reading a textbook chapter on syntax.
The question below puts a SQL statement in front of you and asks you to reason about what it produces.
Which operator defines the field that the index is using in a CREATE TABLE statement?
From writing queries, the exam shifts to the structural decisions that make those queries meaningful. Primary and foreign keys are not just index markers; they are the mechanism that enforces entity integrity and referential integrity across a schema. Where candidates lose marks here is in confusing which constraint does which job, or in failing to recognise when a composite primary key is the right choice over a surrogate key. The consequences of a wrong key design ripple through every query...
From writing queries, the exam shifts to the structural decisions that make those queries meaningful. Primary and foreign keys are not just index markers; they are the mechanism that enforces entity integrity and referential integrity across a schema. Where candidates lose marks here is in confusing which constraint does which job, or in failing to recognise when a composite primary key is the right choice over a surrogate key. The consequences of a wrong key design ripple through every query written against that schema.
How Defining primary and foreign keys for data normalization is tested
Items present a schema or a business rule and ask you to identify the appropriate key structure, or to spot a design that violates integrity constraints. The most common trap is a foreign key scenario where the candidate must determine which table holds the key and which table it references. Getting the direction backwards produces a plausible-looking schema that breaks on insert or delete.
Items reward candidates who can distinguish entity integrity (handled by the primary key, which must be unique and non-null) from referential integrity (handled by the foreign key, which must match an existing primary key value or be null where permitted). Composite keys appear in junction tables for many-to-many relationships, and items frequently test whether you recognise when a natural composite key is preferable to adding a surrogate. Tie your key choice to the business rule in the scenario, not just to what looks tidy.
A timed practice test from ITExamsTopics lets you check whether you can apply key-definition rules under pressure, not just recall them. Seeing the item style before the real exam removes one variable on test day.
The question below asks you to apply key-definition rules to a specific table relationship.
Which function removes only the leading spaces from a string?
Key design and normalization are two sides of the same decision: once you know how keys work, you need to know what structural rules the rest of the table must satisfy. Normalization is examined as a diagnostic skill. You will be given a table and asked to identify which normal form it violates, or to produce the correctly decomposed version. The forms tested are 1NF through 3NF, and the failure mode for most candidates is being able to name the...
Key design and normalization are two sides of the same decision: once you know how keys work, you need to know what structural rules the rest of the table must satisfy. Normalization is examined as a diagnostic skill. You will be given a table and asked to identify which normal form it violates, or to produce the correctly decomposed version. The forms tested are 1NF through 3NF, and the failure mode for most candidates is being able to name the forms without being able to apply them to a concrete table.
How Normalizing relational databases is tested
Items typically show a denormalized or partially normalized table and ask you to identify the violation or to select the schema that resolves it. The distinction between a 2NF violation (partial dependency on part of a composite key) and a 3NF violation (transitive dependency between non-key attributes) is the most productive trap in this area. Candidates who memorise definitions without working through examples consistently confuse the two.
Items reward the candidate who can look at a column, trace its functional dependency back to the key, and state precisely what is wrong. A column that depends on another non-key column is a 3NF issue; a column that depends on only one part of a composite key is a 2NF issue. The fix in each case is decomposition into a separate table, but the decomposition looks different depending on which violation you have diagnosed. Work through the dependency, not through pattern-matching on table shape.
ITExamsTopics includes normalization scenarios across multiple item styles. Running through the full bank gives you enough varied examples to move from recognising the forms by name to diagnosing them reliably in unfamiliar table structures.
The question below presents a table structure and asks you to identify its normalization status.
Normalization tells you what a schema should look like; this area tests whether you can build it. DDL commands (CREATE, ALTER, DROP) are the focus, and the exam is interested in the details that candidates gloss over during practice: constraint syntax, data type selection, and the order in which objects must be created or dropped when foreign key dependencies exist. A candidate who has only written SELECT statements and never set up a schema from scratch will find this area...
Normalization tells you what a schema should look like; this area tests whether you can build it. DDL commands (CREATE, ALTER, DROP) are the focus, and the exam is interested in the details that candidates gloss over during practice: constraint syntax, data type selection, and the order in which objects must be created or dropped when foreign key dependencies exist. A candidate who has only written SELECT statements and never set up a schema from scratch will find this area more demanding than expected.
How Creating databases and tables in SQL enabled database systems is tested
Items present a requirement, such as a table that must enforce a uniqueness constraint or a column that must not accept null values, and ask you to identify the correct DDL statement or to spot the error in one that is given. The trap is in constraint placement: inline column constraints versus table-level constraints behave differently, and getting that distinction wrong produces a statement that runs but does not enforce the intended rule.
Items also reward understanding of dependency order. Dropping a parent table before its child table fails if a foreign key constraint is in place; creating a child table before the parent it references fails for the same reason. The exam tests whether you know the sequence, not just the syntax. Data type choices appear in scenario-based items where the wrong type causes truncation or precision loss. Pick the type that fits the data, not the one that feels familiar.
The ITExamsTopics PDF and practice test both cover DDL scenarios. If creating schemas is a weak area for you, working through targeted questions is faster than re-reading documentation, and you get immediate feedback on which constraint rules you are misapplying.
The question below focuses on DDL syntax and the rules that govern how database objects are created.
After four areas of technical SQL and schema work, this topic shifts register entirely. Leadership and management in a data management context covers the organisational side of running data as a function: governance, data stewardship, team roles, and the decisions that sit above the query level. Candidates with a purely technical background often underestimate this area and arrive unprepared for scenario-based items that ask what a data manager should do, not what a database should contain. How Leadership and management...
After four areas of technical SQL and schema work, this topic shifts register entirely. Leadership and management in a data management context covers the organisational side of running data as a function: governance, data stewardship, team roles, and the decisions that sit above the query level. Candidates with a purely technical background often underestimate this area and arrive unprepared for scenario-based items that ask what a data manager should do, not what a database should contain.
How Leadership and management is tested
Items in this area are scenario-driven. You are placed in the role of a data manager or team lead and asked to choose the most appropriate action, priority, or organisational response. The trap is selecting the technically correct action when the item is actually asking for the managerially correct one. These are not always the same thing, and the item rewards the candidate who reads the role in the scenario before picking an option.
Data governance questions test whether you know which role owns a decision: a data steward handles quality and definitions, while an executive sponsor handles cross-functional authority. Confusing those responsibilities is a reliable way to lose marks. Items also appear around prioritisation: when multiple data problems exist, the managerial response is to triage by business impact, not by technical severity. Approach this area the way you would approach a management case study, not a syntax problem.
Because leadership items are scenario-based, volume matters. The ITExamsTopics practice test exposes you to a range of management scenarios so you can calibrate your instincts on role boundaries and governance priorities before the real exam.
The question below puts you in a management scenario and asks you to identify the appropriate course of action.
The three-model framework sits underneath every design decision covered elsewhere in this exam. A conceptual model captures business entities and relationships without implementation detail. A logical model adds attributes, key definitions, and relationship cardinality. A physical model translates all of that into the specific syntax and structures of a target database system. Candidates most often lose marks by collapsing two adjacent layers together, particularly logical and physical, because in practice they are often built in the same tool. How Introduction...
The three-model framework sits underneath every design decision covered elsewhere in this exam. A conceptual model captures business entities and relationships without implementation detail. A logical model adds attributes, key definitions, and relationship cardinality. A physical model translates all of that into the specific syntax and structures of a target database system. Candidates most often lose marks by collapsing two adjacent layers together, particularly logical and physical, because in practice they are often built in the same tool.
How Introduction to conceptual logical and physical data models is tested
Items present a modelling artefact, a description of a design decision, or a diagram element, and ask you to identify which layer it belongs to or which layer a described activity should produce. The most common trap is assigning a physical-level detail (a specific data type, an index, a storage parameter) to the logical model, or assigning a business-level entity description to the logical model instead of the conceptual one.
Items reward the candidate who can classify a design decision by the question it answers. Conceptual models answer 'what does the business care about?'; logical models answer 'how are those things structured and related?'; physical models answer 'how is this stored and accessed in this specific system?'. Cardinality notation appears at the logical level, not the conceptual. Technology-specific syntax appears only at the physical level. Keep those boundaries clear and the items in this area become straightforward classification exercises.
The free demo on the ITExamsTopics practice test includes items from across all topics, so you can check your footing on data modelling concepts before committing to the full bank.
The question below asks you to place a modelling concept or decision within the correct layer of the three-model framework.
This final area ties together terminology and structural knowledge from across the exam. It covers how database objects are described and classified: table attributes, column properties, database-level settings, and the SQL commands associated with each category. Candidates sometimes treat this as a vocabulary exercise, but the exam uses these terms inside scenarios where misidentifying an attribute type or misclassifying a command leads directly to a wrong pick. Precision with terminology pays off here more than in any other area. How...
This final area ties together terminology and structural knowledge from across the exam. It covers how database objects are described and classified: table attributes, column properties, database-level settings, and the SQL commands associated with each category. Candidates sometimes treat this as a vocabulary exercise, but the exam uses these terms inside scenarios where misidentifying an attribute type or misclassifying a command leads directly to a wrong pick. Precision with terminology pays off here more than in any other area.
How Attributes of databases tables and SQL commands is tested
Items test classification and application, not definition recall. You may be shown a column property and asked which SQL command sets or modifies it, or shown a command and asked what category of operation it belongs to (DDL, DML, DCL, or TCL). The trap is in commands that candidates associate with the wrong category because they use them frequently without thinking about the classification.
Items reward the candidate who connects the command to the type of object or operation it acts on. DDL acts on schema objects; DML acts on data within those objects; DCL controls access; TCL controls transaction boundaries. Attributes of a table (column name, data type, nullability, default value, constraint) are distinct from attributes of the database itself (character set, collation, owner). Items also appear on the relationship between a column attribute and the constraint that enforces it. Review these groupings actively, not as a list to memorise but as a set of distinctions to apply.
ITExamsTopics covers all command categories and table attribute types in the practice test. Because this area rewards precision, working through questions that mix terminology in realistic scenarios is more effective than studying a command reference in isolation.
The question below tests your ability to classify a database object attribute or SQL command within the correct category.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full Data Management - Foundations (D426) Exam Questions 🚀
