GBDS study plan

Draw a fully attributed entity-relationship diagram from a written scenario, assigning primary and foreign keys and resolving one many-to-many relationship into an associative entity.

Convert that ER diagram into third normal form tables and write the CREATE TABLE statements with appropriate data types and NOT NULL constraints.

Normalize a supplied unnormalized table through 1NF, 2NF, and 3NF, documenting the anomaly each step removes.

Write single-table SELECT queries using WHERE, ORDER BY, DISTINCT, and aggregate functions with GROUP BY and HAVING.

Model a star schema for a sales reporting scenario, separating fact and dimension tables and declaring grain in one sentence.

Compare star and snowflake schemas and justify the chosen design in a short written rationale.

Write multi-table joins including INNER, LEFT, and self joins, and explain when each is appropriate.

Implement primary key, foreign key, CHECK, and UNIQUE constraints and demonstrate a referential integrity violation being rejected.

Write subqueries, correlated subqueries, and a CTE that solve three reporting questions against your practice schema.

Use window functions such as ROW_NUMBER, RANK, and running SUM partitioned by a dimension.

Create a view and a stored procedure or parameterized query, and state one security benefit of each.

Convert three stakeholder statements into testable functional requirements with acceptance criteria.

Elicit and document requirements for a small case scenario using interviews, observation, and document analysis, and note which technique surfaced which requirement.

Classify each requirement as functional or non-functional and trace it to a design element.

Define data quality dimensions (completeness, accuracy, consistency, timeliness, uniqueness) and write a measurable rule for each.

Draft a data dictionary for your practice schema covering name, type, nullability, allowed values, and owner.

Design a role-based access model with least privilege, granting SELECT, INSERT, and UPDATE separately to distinct roles.

Explain encryption at rest and in transit, masking, and auditing, and place each control at the correct layer.

Map a source-to-target ETL specification including transformations, data type conversions, and rejection handling.

Identify slowly changing dimension types and implement a Type 2 dimension with effective and expiry dates.

Build an incremental load that handles inserts, updates, and deletes, and explain idempotency and restartability.

Add validation and reconciliation checks that compare source and target row counts and key aggregates.

Design three KPIs with explicit calculation logic, grain, and refresh cadence.

Choose an appropriate chart type for each KPI and justify the choice against the audience and the question asked.

Produce a delivery plan for a data project with work breakdown, dependencies, and a critical path.

Identify five project risks with likelihood, impact, and a mitigation for each.

Write a stakeholder communication plan naming audience, message, channel, and frequency.

Interpret a dashboard requirement and translate it into a semantic layer or view definition.

Complete two timed full-length practice exams and record the score by domain.

Re-study the two weakest domains using targeted drills rather than rereading notes.

Recite from memory the normal forms, SCD types, quality dimensions, and ETL failure-handling options.

Review every missed practice question and write the underlying rule it tested.