Scenario-based questions: filtering the noise
Most ExAC questions are scenario-based. A short brief sets up a project, a code situation, a coordination problem, or an office decision, and the multiple-choice question asks you to choose the best response. The scenarios are written to feel like real projects, which means they carry the kind of incidental detail real projects carry: client preferences, contract values, schedule pressure, a junior staff comment, a square-metre figure. Some of that detail bears on the answer. Most of it does not.
The most useful habit on a scenario-based question is to read the question stem before the scenario. Once you know what the question asks (the next step in a process, the applicable code clause, the architect's appropriate response, the cost implication), the scenario reads differently. You stop scanning everything for relevance and start scanning only for the few facts that actually answer the question.
Two quick filters land most scenario questions. First, what discipline is being tested? Cost, code, contract, coordination, or design judgment? The discipline tells you which Canadian reference frames the answer: NBC 2020 for code, Yardsticks for Costing or RSMeans for cost, CCDC 2 for contracts, CHOP for coordination and office decisions, design fundamentals for schematic and analysis items. Second, what does the question literally ask? "What is the architect's next step" is a different question than "what is the most appropriate response", and both are different from "which option best satisfies the code".
Treat the scenario like a project brief and the question like a project meeting agenda. The brief has detail; the agenda has one decision. Answer the decision, then move on.