dbt Architect exam-day guide
dbt Architect · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the original physical ID (passport or government photo ID) in the exact name used on your registration. Confirm with the provider which ID types are accepted and whether a digital ID is allowed before test day; treat digital-only ID as needs_review.
Exam appointment confirmation and login details
Have your confirmation email, candidate/registration ID, and the username or email tied to your testing account accessible. If the exam is proctored online, verify the delivery platform and browser requirements in advance.
Confirm exam delivery format and technical requirements
Check whether your sitting is at a test center or online-proctored, and note the platform, browser, webcam/microphone, and bandwidth requirements. Details vary by provider, so confirm with the provider rather than assuming.
Allowed reference materials
Most certification exams are closed-book. Confirm with the provider whether any notes, documentation, or scratch materials are permitted; assume none unless explicitly stated. needs_review.
Scratch paper and writing tool policy
Determine in advance whether a whiteboard, laminated sheet, or on-screen notepad is provided and whether you may bring your own pen or paper. Confirm with the provider; needs_review.
Quiet, private testing space (online sittings)
For remote proctoring, clear the desk, remove monitors and secondary devices, ensure a closed door, good lighting, and a stable connection. Run the platform's system check at least a day ahead.
Review dbt fundamentals you will be tested on
Be ready to reason about models, sources, tests, seeds, snapshots, macros, Jinja, ref/source, materializations (view, table, incremental, ephemeral), the DAG, and project configuration. The exam emphasizes practical architecture judgment, not memorized syntax.
Practice reading dbt project structures and YAML
Be comfortable interpreting dbt_project.yml, schema YAML, model configs, and profiles without an IDE. You will likely need to reason about configuration precedence and environment behavior.
Plan timing and question strategy
Know the number of questions and time limit from your appointment details. Decide a per-question pace, a flag-and-return strategy, and how much time to reserve for review.
Arrange travel or connection buffer
For test centers, arrive early and account for security check-in. For online sittings, log in before the start time and allow time for identity verification and room scan.
Rest, hydration, and break expectations
Plan sleep and meals so you are sharp. Confirm with the provider whether scheduled or unscheduled breaks are allowed and how they affect the clock; needs_review.
Backup plan for technical failure
Save the provider's support contact and know the procedure if the connection drops or the platform fails. Confirm the policy for rescheduling or incident reporting with the provider.
Plan the day
Do a focused review pass over the dbt concepts most likely to be tested: the DAG and ref/source resolution, materialization trade-offs, incremental model strategies (append, merge, delete+insert, unique_key, incremental predicates), testing (generic vs singular, severity, store_failures), snapshots (timestamp vs check strategy), and environment/promotion patterns (dev vs prod targets, CI jobs, Slim CI with state comparison). Re-read your own project's dbt_project.yml and a couple of model files to keep configuration precedence fresh. Stop learning brand-new topics; consolidate what you know.
Do a timed practice run using any sample questions or practice exam available to you, then review every miss for the underlying concept rather than the specific wording. Note recurring weak areas and target them in your remaining study blocks.
Confirm logistics: verify appointment date, time, and time zone; check the delivery format; run the system test if online-proctored; confirm ID validity and name match; and locate the test center or set up your testing room.
Do a light review only: skim a one-page summary of key concepts, materialization choices, and testing strategy. Avoid cramming new material. Prepare your ID, confirmation details, and any permitted items. Get a full night's sleep and set two alarms.
Re-run the platform system check if online-proctored, charge devices, and confirm your internet connection. Clear and set up your desk so morning-of is frictionless. Confirm with the provider any last-minute rules on breaks, materials, and check-in time.
Eat a normal meal, hydrate moderately, and avoid last-minute cramming that raises anxiety. Log in or arrive with a comfortable buffer. Have your ID and confirmation ready before check-in begins.
Read each question fully and identify what is actually being asked (configuration behavior, architecture trade-off, debugging, or best practice). Answer confident questions first, flag uncertain ones, and return to them. Eliminate clearly wrong options, then choose the best remaining answer. Watch the clock and keep a steady pace; do not let one hard question consume disproportionate time.
Use any provided scratch notepad to sketch a DAG or configuration hierarchy when a question is complex. If a question depends on a policy or feature detail you are unsure of, reason from dbt principles rather than guessing wildly, and reserve time for a final review of flagged items.
Note any concepts that felt weak while they are fresh, in case a retake is needed. Follow the provider's process for score reporting and, if applicable, any retake waiting period.
Rules to check
Bring original government-issued photo ID whose name matches your registration exactly. Confirm with the provider which ID forms are accepted and whether expired or digital IDs are permitted.
Arrive or log in early enough to complete identity verification and check-in. Late arrival may forfeit your seat or appointment; confirm the provider's late-arrival and rescheduling policy in advance.
Assume the exam is closed-book and individual. Do not use notes, external documentation, AI tools, or communicate with others during the sitting unless the provider explicitly permits it.
Follow all proctoring instructions, including room scans, desk clearance, and camera/microphone requirements for online sittings. Non-compliance can lead to score invalidation.
Confirm with the provider whether breaks are allowed, whether they are timed, and how they affect the clock. Do not leave the testing environment without following the proctor's procedure.
Understand the scoring model before test day: confirm whether the exam is pass/fail with a scaled score, the passing threshold, and whether question review or comments are offered. Do not assume a specific threshold.
If a technical failure occurs, stop and follow the provider's incident-reporting process rather than improvising. Confirm the support contact and escalation path beforehand.
Keep all exam content confidential. Do not reproduce, share, or discuss specific questions afterward; doing so may violate the provider's candidate agreement.