ARC common mistakes
ARC · Understand the traps and how to avoid them.
Choosing the 'textbook-perfect' answer (e.g., 'escalate to the sponsor immediately') instead of the answer that reflects what a competent practitioner would actually do first in the described situation.
Candidates memorize process outputs and idealised control loops but never practise applying them to messy, realistic scenarios, so they pick the most dramatic or formal-sounding option rather than the proportionate first action.
What to do instead
For every practice scenario, force yourself to rank the options by 'what happens next in the real world' before checking the answer key, and write one sentence justifying why the runner-up option is premature or excessive.
Treating a stated requirement as complete when it describes a solution ('the system shall use a dropdown') rather than a need, and failing to probe for missing acceptance criteria.
Candidates read requirements for plausibility rather than for testability, and they conflate solution language with requirement language because both sound technical and specific.
What to do instead
Practise rewriting every requirement you encounter into 'given/when/then' form; if you cannot state how you would verify it, flag it as incomplete and look for the option that adds acceptance criteria or asks a clarifying question.
Compressing the schedule by shortening task durations or removing float when the critical path is constrained, instead of selecting the option that changes logic (fast-tracking, crashing with cost trade-off analysis).
Duration arithmetic feels concrete and safe, while logic changes feel risky; candidates also confuse 'critical path' with 'longest list of tasks' and mis-identify which activities actually drive the finish date.
What to do instead
Before answering any schedule question, redraw the network on scratch paper, compute total float for each path, and eliminate any option that shortens a non-critical activity or that adds risk without stating the cost/benefit trade-off.
Reading a cost variance or CPI figure and concluding the project is 'over budget' without separating the cause (rate vs. usage vs. scope) or checking whether the variance is within the control threshold.
Candidates latch onto the sign of the variance and skip the diagnostic step, and they often invert the CPI/SPI interpretation under time pressure.
What to do instead
For every earned-value item, compute CV, SV, CPI and SPI explicitly, state in words what each means, then ask 'is this beyond the tolerance defined in the plan?' before selecting a corrective-action option.
Selecting 'accept the risk' or 'add a contingency' for a threat that is already occurring, rather than recognising it as an issue requiring an issue-management response.
Risk and issue vocabulary overlaps heavily, and candidates default to the risk register because it is the more familiar artefact, missing the tense shift ('has occurred', 'is currently') that signals an issue.
What to do instead
Scan each scenario for tense and status words first; if the event has happened, eliminate every option that mentions risk response strategies and choose from escalate/assign/resolve actions instead.
Escalating to the sponsor or steering committee as a first response to a difficult stakeholder, instead of first attempting direct engagement, expectation management, or use of the communication plan.
Escalation feels decisive and is easy to justify, and candidates under-weight the professional-responsibility expectation that the practitioner handles it at the lowest effective level first.
What to do instead
Memorize the escalation ladder explicitly (direct conversation → agreed channel → manager → governance body) and reject any 'escalate' option that does not show prior engagement attempts or a defined threshold being breached.
Interpreting a quality metric that is within control limits as a defect requiring corrective action, or ignoring a metric that is within limits but trending steadily toward a limit.
Candidates conflate specification limits with control limits and react to individual data points rather than to patterns, because the question wording often emphasises a single alarming-looking number.
What to do instead
Before answering, label the limits in the scenario as specification or control, then apply the rule: out-of-spec = defect; in-spec but out-of-control pattern = investigate the process; in-control variation = no action.
Choosing the option that satisfies the client or sponsor fastest when it conflicts with a policy, regulation, or safety obligation, on the reasoning that stakeholder satisfaction is the priority.
Stakeholder-management material is heavily weighted in study time, so candidates over-apply 'keep the customer happy' and under-apply the non-negotiable primacy of compliance and professional standards.
What to do instead
Build a reflex hierarchy: legal/regulatory/safety > organisational policy > contractual obligation > stakeholder preference. Any option that trades the top of that hierarchy for speed or satisfaction is wrong regardless of how reasonable it sounds.
Answering the question that was asked about the wrong lifecycle phase - applying planning-phase artefacts (WBS, schedule baseline) to an executing or closing scenario, or vice versa.
Candidates recognize a familiar keyword and retrieve the associated tool without first anchoring on where in the lifecycle the scenario sits and what artefacts would actually exist at that point.
What to do instead
Before reading the options, write the lifecycle phase and the two or three artefacts that legitimately exist at that moment; eliminate any option that depends on an artefact not yet created or already closed.
Leaving scenario questions unanswered or changing correct first-instinct answers on review because the option 'sounds more sophisticated'.
Candidates run short on time from over-deliberation on a few items, then second-guess answers without new evidence, and sophisticated-sounding distractors exploit that doubt.
What to do instead
Adopt a fixed time budget per item, answer every question on first pass, and on review only change an answer when you can name the specific word in the stem that invalidates your original reasoning.