BCT(A) common mistakes
BCT(A) · Understand the traps and how to avoid them.
Treating strategy questions as generic leadership questions, choosing the option that sounds most collaborative or aspirational instead of the one that follows from the scenario's stated objectives, constraints, and stakeholders.
Candidates rely on workplace instinct and buzzwords rather than analysing the scenario; strategy items are written so that the distractors are all defensible-sounding management platitudes.
What to do instead
Before reading the options, restate the scenario's goal, the binding constraint, and who bears the consequence. Eliminate any option that ignores the stated constraint or that would require resources the scenario says are unavailable.
Confusing organisational structures and governance bodies, for example describing a matrix organisation's dual reporting as a project management office function, or mixing up the roles of a steering committee and a project sponsor.
The terms overlap in everyday speech and candidates learn definitions by recognition rather than by distinguishing the specific decision rights each body holds.
What to do instead
Build a comparison table of structures and governance bodies keyed on three attributes: who sets priorities, who owns budget, and who resolves escalated conflicts. Answer from the attribute, not the label.
Selecting a network, storage, or cloud option based on the technology name rather than on the requirement stated in the scenario, such as recommending a public cloud deployment when the scenario requires data to remain on premises for regulatory reasons.
Candidates pattern-match on familiar technologies and skim past the requirement sentence, which is often embedded in a subordinate clause.
What to do instead
Highlight every explicit requirement and prohibition in the stem before looking at options, then test each option against the list; discard any option that violates even one stated requirement.
Mixing up availability, scalability, and resilience, or treating redundancy as equivalent to backup, when evaluating an infrastructure design.
The concepts are related and vendors use them loosely, so candidates accept an option that sounds robust without checking whether it addresses the failure mode described.
What to do instead
For each scenario, name the failure mode first (component failure, demand spike, data corruption, site loss), then select the mechanism that specifically addresses that failure mode.
Choosing a data model or normalisation answer by memorised rule rather than by the scenario's stated access patterns and integrity needs, such as insisting on third normal form when the scenario demands fast denormalised reporting reads.
Candidates learn normal forms as absolute rules and do not connect them to the trade-off between write integrity and read performance.
What to do instead
State the trade-off explicitly for each item: what integrity problem does the option prevent, and what performance or complexity cost does it impose? Pick the option whose cost the scenario can bear.
Reading a metric question and answering with the definition of the metric instead of computing or interpreting it, or confusing correlation with causation when a scenario reports two trends moving together.
Time pressure and unfamiliar numbers push candidates toward the option that defines a term, which is often a well-crafted distractor.
What to do instead
When numbers appear, do the arithmetic on scratch paper and match your result to an option before reading the explanations. When a scenario reports two trends, ask whether a third factor could explain both.
Treating risk treatment as a single choice, for example selecting 'mitigate' when the scenario describes a risk whose likelihood cannot be reduced and whose impact is best handled by a contractual transfer or a documented acceptance.
Candidates equate good security with controls, so they pick the most active-sounding response without checking whether it addresses the residual risk described.
What to do instead
For each risk item, write the risk as likelihood times impact and ask which lever the option actually moves; then confirm the option matches the organisation's stated risk appetite.
Confusing authentication with authorisation, or confidentiality with integrity, when selecting a control for a described threat.
These pairs are taught together and candidates recall the umbrella term rather than the precise property each control protects.
What to do instead
Before choosing, name the property under attack in one word (who you are, what you may do, secrecy, tampering, availability) and select only the control that protects that property.
Choosing a project methodology or lifecycle by preference rather than by the scenario's uncertainty, regulatory, and stakeholder characteristics, such as prescribing predictive waterfall for a project with undefined requirements and frequent change.
Candidates have a favoured methodology and treat the question as asking which is best in general rather than which fits the described conditions.
What to do instead
Extract three signals from the stem: requirement stability, tolerance for incremental delivery, and need for formal documentation. Let those three signals determine the lifecycle, and reject options that conflict with any of them.
Answering communication and collaboration items by picking the richest medium or newest tool, ignoring the scenario's need for a permanent record, geographic distribution, or confidentiality.
Candidates equate more interaction with better communication and overlook that medium choice is a function of message complexity, audience, and evidentiary needs.
What to do instead
Ask two questions: does this message need a durable record, and does it need immediate feedback? The answers narrow the medium to one or two options before you evaluate the rest.
Treating an ethical dilemma as a compliance checkbox, selecting the option that is legal while ignoring the scenario's conflict of interest, disclosure obligation, or duty to the profession.
Candidates conflate 'not prohibited' with 'ethical' and stop analysing once an option appears lawful.
What to do instead
For ethics items, identify the affected parties and ask what a reasonable observer would expect to be disclosed or refused; prefer the option that preserves transparency even when a lawful alternative exists.