Does completing security awareness training prove it worked?
No. Finishing a course does not prove behavior changed, so programs measure results, such as phishing simulation outcomes, and improve continuously.

Exam objectiveGiven a scenario, implement security awareness practices
Objective 5.6 covers how to implement security awareness practices: phishing awareness, recognizing unusual behavior, the topics every user needs, and how an awareness program is built and run.
Phishing. Phishing awareness trains users to spot suspicious messages, rewards them for reporting, and gives security a fast way to respond. It covers campaigns, including authorized simulations that end in training, recognizing a phishing attempt, and responding to reported suspicious messages. The report rate, not only the click rate, is the behavior to encourage.
Anomalous behavior and reporting. Staff who recognize unusual behavior and report it quickly turn every employee into a sensor. The listed categories are risky behavior (carelessness or rule bending), unexpected behavior, and unintentional behavior (an honest slip). Unusual does not always mean hostile, so it is reported and assessed. Reporting and monitoring run as initial and recurring activities.
User guidance and the program. Training topics are policies and handbooks, situational awareness, insider threat, password management, removable media and cables, social engineering, operational security, and hybrid or remote work environments. Awareness raises general attention for everyone, while role-based training builds specific skills for jobs such as developers or administrators. Program development is planning and design around real risks and audiences, and execution is delivery, measurement, and continuous improvement; finishing a course does not prove behavior changed.
Exam scenarios describe a user action, such as clicking a link, plugging in a found USB drive, or working from a cafe, and ask for the best response or training topic; the best answers favor early reporting and a blame-free culture.
This page is the map. Knotch is where you drill it until it sticks.
Risky behavior is carelessness or rule bending, such as sharing a password or using unapproved storage. Unintentional behavior is an honest slip, such as losing a laptop or misaddressing a message.
Awareness raises general attention for everyone. Role-based training builds specific skills for jobs such as developers or administrators.
Situational awareness is noticing threats around you. OPSEC is controlling what information you give out.
The click rate counts users who fell for a phishing message. The report rate counts users who reported it, which is the behavior to encourage.
The full set of look-alike pairs for this objective is inside Knotch.
Everyone at a company watches the same annual security video. Developers continue to introduce injection flaws and administrators reuse privileged passwords.
Which change BEST addresses the gap?
Role-based training targets specific jobs, such as developers or administrators.
Awareness is for everyone. Role-based training is for specific jobs. NIST SP 800-50 Rev. 1 ties training to the real risks people face.
Why not B: General awareness does not teach secure coding or privileged account practices.
Why not C: Policy states the rule but does not build skills.
Why not D: Their role creates risks that general video does not cover.
No. Finishing a course does not prove behavior changed, so programs measure results, such as phishing simulation outcomes, and improve continuously.
A policy states the rule. Training builds the habit.
Initial means training at hire, including how and where to report, and a baseline of knowledge before the person gets access. Recurring means refreshers on a schedule, reminders, and updates when threats change.
