Naming a security objective the scenario rules out
The wrong answers pick an objective that the facts of the scenario exclude. Encryption makes confidentiality look relevant, yet an administrator who silently altered stored results with no record caused an integrity failure. A denial of service attack is built to exhaust a service, so it threatens availability rather than the secrecy or accuracy of the data behind it. A copied file of unchanged records that stayed available to staff is a confidentiality breach, because an unauthorised party read it. The objective that failed is the one the facts describe.
See it in a sample questionMixing up recovery point, recovery time and maximum tolerable downtime
The wrong answers swap the recovery objectives. The recovery point objective sets the maximum period of data that may be lost, so backups are checked against it, while the recovery time objective and maximum tolerable downtime both measure outage duration. A nightly full backup cannot meet a fifteen-minute recovery point objective, and moving the tapes closer only shortens restoration. Replication that silently fails for days leaves the secondary site three days behind, which breaches a one-hour recovery point objective in practice rather than the recovery time objective.
See it in a sample questionExpecting the course itself to change behaviour
The wrong answers look to the course itself for behaviour change. Reading logs, quiz scores, and counts of sessions delivered and staff registered record consumption, recall or reach, while a falling click rate and a rising report rate in simulated phishing show what staff actually do. A longer session, a harder end test or an on-demand video still gives one exposure that decays within weeks, so short, regular touchpoints sustain the behaviour. Polished videos, course length and module counts matter less than senior leaders visibly following the same controls.
See it in a sample questionOffering a security control for a privacy principle
The wrong answers reach for a security control where the scenario describes a privacy principle. Encryption and tighter physical access protect tapes that are still kept indefinitely, so a retention schedule with secure disposal is what fixes the disposal stage. Masking leaves unneeded data collected, whereas data minimisation limits collection to the email address required. Encryption in transit does not make a cross-border transfer lawful; a transfer mechanism binding the receiver does. Reusing claims data for marketing breaches purpose limitation, not confidentiality.
See it in a sample questionResponding after the decision instead of before it
The wrong answers place the risk response after the decision it should shape. Recording a tool after deployment locks in the redundancy, so architecture review belongs before approval. A post-build penetration test cannot keep pace with daily releases, and production monitoring finds a weakness only once exploited, so automated checks sit in each pipeline stage. Reviewing a generative AI trial afterwards leaves exposure unmanaged, so the practitioner first identifies the use case, data and exposures. Briefing governance only after an incident denies decision makers the chance to act.
See it in a sample question