TEST ARCHED
More study resources
Cheat sheet
Keep the key ideas within reach.
ExploreKey terms
Get comfortable with the vocabulary.
ExploreStudy plan
Give each week a clear focus.
ExploreCommon mistakes
Understand the traps and how to avoid them.
ExploreCase studies
Put your knowledge to work in context.
ExploreExam-day guide
Prepare for the day ahead.
ExploreAbout this exam
TEST ARCHED is a multiple-choice examination built around seven domains that together describe the full lifecycle of a technology project: project and program fundamentals, requirements and scope definition, architecture and solution design, delivery and implementation management, quality assurance and verification, risk change and issue management, and stakeholder communication and governance. It suits practitioners who sit between business intent and technical delivery - project or program leads, solution architects, business analysts moving into design roles, and delivery managers who must defend design decisions to sponsors. The exam tests judgement rather than memorisation. Expect scenario questions that describe a project situation and ask which action, artefact, or control is most appropriate, with plausible distractors drawn from common but weak practice. Domain weighting is published in the profile: fundamentals and architecture and solution design carry the most weight, followed by requirements and delivery, with quality, risk, and stakeholder governance sharing the remainder. Preparation should be built around the domains rather than a single textbook. Work through each domain, write short summaries in your own words, and practise justifying why one option beats another. Because the official body publishes current administrative details - question count, duration, fees, passing score, retake rules, and result validity - check its website directly rather than relying on secondhand summaries. This page is independent study material and is not affiliated with or endorsed by the exam owner.
What you'll study
About TEST ARCHED preparation
What is the exam format?
It is delivered as multiple-choice questions covering the seven published domains. The official body publishes the current question count, time limit, and whether any questions are unscored pretest items, so confirm those specifics on its website before you book.
How difficult is it?
The difficulty comes from judgement, not recall. Most items describe a project situation and ask for the best next action. Candidates who have only memorised definitions struggle; those who can explain why a plausible option is wrong usually cope well. Architecture and fundamentals carry the most weight.
How long should I study?
There is no official recommended hours figure. A practical approach is to allocate study time in proportion to domain weighting, spending roughly half your effort on fundamentals and architecture and solution design. Spread sessions over several weeks so you revisit earlier domains rather than cramming them once.
Can I retake it, and how soon?
Retake eligibility, waiting periods, and any fee for a second attempt are set by the exam owner and change over time. Rather than relying on forum posts, check the official website or your candidate handbook for the current policy before scheduling a retake.
In what order should I study the domains?
Start with project and program fundamentals, because later domains assume its vocabulary. Then take requirements and scope, followed by architecture and solution design. Delivery, quality, and risk build on those. Finish with stakeholder communication and governance, which ties the other domains together in scenario questions.
What are the most common failure modes?
Three recur: choosing the technically elegant answer when the question asks for the governed or approved one; confusing scope change control with design change control; and answering from personal workplace habit rather than from the principle the question tests. Read the stem carefully and eliminate options that skip approval steps.
How should I handle scenario questions?
Identify who the decision-maker is, what stage the project is in, and whether the question tests prevention, detection, or correction. Eliminate options that escalate prematurely or bypass governance. If two options remain, prefer the one that produces a documented, reviewable artefact over a verbal agreement.
Does this page make me officially prepared?
No. This is independent study material and is not affiliated with, endorsed by, or sponsored by the exam owner. Use it alongside the official syllabus and any reference material the body publishes. Always treat the official site as authoritative for scope, administration, and scoring.