12.2 Flag and Review Workflow
Key Takeaways
- Flagging should mark questions that need a second look, not questions a candidate plans to avoid.
- A useful review pass checks the prompt's domain, task, constraint, and official fact claims before changing an answer.
- Candidates should be especially careful with answers that sound sustainable but contradict source-brief logistics or transition facts.
- A changed answer should have a specific reason, such as finding a wrong vendor, wrong date, wrong version, or unsupported promise.
Flag for Evidence, Not Worry
A flag is a promise to revisit a question with better focus, not an excuse to postpone thinking. During the first pass, give every item a serious attempt. If you are uncertain, choose the best answer available, flag the item, and move on. This protects the clock while avoiding blank decisions. Because scored and unscored questions are mixed randomly, the right strategy is not to guess what counts. The right strategy is to answer all questions and use review time where it can improve confidence.
The review pass should be structured. Before changing an answer, ask four questions. What is the domain anchor? What task does the question ask? What constraint limits the answer? What official fact claim appears in the options? This turns review from emotional second-guessing into evidence checking. If you cannot name a concrete reason to change an answer, leaving the original choice may be better than switching because the wording feels unfamiliar.
| Review check | Ask this | Change only if you find... |
|---|---|---|
| Domain | Which topic controls the decision? | Your first answer belongs to a different domain. |
| Task | Is it asking first, best, incorrect, or current? | Your first answer solves a different task. |
| Constraint | Is there a date, beta/final distinction, or policy rule? | Your first answer ignores the constraint. |
| Official fact | Does an option make a logistics or scoring claim? | The option conflicts with the source brief. |
| Overreach | Does the answer promise too much? | The answer invents a overclaim or pass-rate claim. |
Many review gains come from catching fact errors. If an answer names a delivery vendor other than Prometric, it conflicts with the source brief because delivery is through a Prometric test center or Prometric ProProctor remote exam. If an answer converts the v4 scaled score into a raw percentage of questions correct, it conflicts with the scoring guardrail. If an answer says the current Green Associate pass rate is a specific percentage, it invents a fact not published in the source brief. If an answer says v5 beta results are immediate, it ignores the beta result rule.
Other review gains come from sequencing. First-action questions often reward earlier planning, assessment, rating-system, or documentation steps. If your first answer jumps to a final tactic, ask whether the prompt asked for a final tactic or an initial move. Best-explanation questions often reward a precise connection between a project choice and the controlling domain. If your first answer is a broad statement about sustainability, ask whether it is specific enough.
Timed practice should include a review log. After a set, record how many items you flagged, how many you changed, how many changes were correct, and why. If most changes are wrong, your review may be anxiety-driven. If most changes are correct and tied to specific evidence, your flagging system is working. The goal is not to flag as few questions as possible. The goal is to make flags useful.
During the final week, reduce careless flagging by training the first pass. Read the final sentence of each prompt twice. Underline or mentally mark version words such as v4, v5 beta, final v5, data-collection phase, or retake. Notice whether the question asks about the exam itself or a project scenario. The cleaner your first pass becomes, the more time your review pass can spend on genuinely hard decisions.
When should a candidate change an answer during review?
Which flagged item most clearly needs a source-brief fact check?
What is the main purpose of flagging an uncertain item?