Treating reversible methods as password storage
The wrong options store passwords with symmetric encryption, public-key encryption or Base64, or claim a hash can be reversed. Symmetric and public-key encryption are reversible by whoever holds the key, and Base64 is an encoding that anyone can decode. A salted hash is one-way, so a login system can compare the hash of an entered password without ever recovering the original, and a stolen database yields no plaintext.
See it in a sample questionMatching the wrong control to the data state
Data at rest, in transit and in use get paired with the wrong protection. Full-disk encryption and column encryption protect stored data and do nothing for traffic on the network, while TLS protects the connection but not the copy on a laptop disk. A file opened for editing is data in use, because it is decrypted in memory where disk and transport encryption no longer apply. The state in the scenario decides which control fits.
See it in a sample questionGiving symmetric and asymmetric encryption each other's jobs
Asymmetric encryption is slow on bulk data, so a shared symmetric key suits large files when both sides already hold one. Symmetric encryption needs that key exchanged first, so it fails when the parties have no prior arrangement. Encrypting with a private key is a signing pattern, not a confidentiality control. A published public key lets anyone encrypt, and only the matching private key decrypts.
See it in a sample questionSubstituting adjacent controls for system hardening
Antivirus scanning, disk encryption, a firewall appliance, automatic patching, a subnet move, extra logging and backups each protect something, but the wrong options offer them where hardening is asked for. None of them removes the default accounts, sample databases and unneeded services that make up the attack surface. Hardening disables or removes those, and a hardened configuration baseline gives every new device the same known, secure starting state.
See it in a sample questionSwapping change management, acceptable use, logging and training
The wrong answers offer one of these controls where another is asked for, or give them functions they do not have, such as encryption, backup scheduling or deleting audit trails. Change management governs how modifications are requested, assessed, approved and tracked before they reach production. The acceptable use policy sets how staff may use systems. Logging and monitoring record events for later review, and awareness training changes behaviour toward threats such as phishing.
See it in a sample question