Skip to content

All certifications

CAS-005 practice question on Cryptographic use cases, 2026-11-03

Archived question for 2026-11-03. Domain: Security Engineering. Objective 3.8: Cryptographic use cases. Original SecLern question, written for practice.

A retailer's analytics systems need to join records by card number but never need the real number. The company wants to remove them from the scope of card data requirements. Which technique is BEST?

Show the explanation

Tokenization both supports joins and removes real numbers from downstream systems.

Each option

  • A. Systems holding encrypted card data stay in scope along with the keys. It would be right when the real number is needed.
  • B. Card numbers have low entropy and are easily brute-forced. It would be right for none of the stated requirements.
  • C (correct). Correct: Tokens allow joins and, with the vault elsewhere, the systems hold no card data.
  • D. Masked values are not unique, so joins fail. It would be right for display.

What this question tests

It maps to CAS-005 objective 3.8, Cryptographic use cases: Given a scenario, apply the appropriate cryptographic use case and/or technique. Related ideas: tokenization.

The published topics under this objective, so you can check what you have covered:

  • Use cases: Data at rest, Data in transit, Data in use/processing, Secure email
  • Techniques: Tokenization, Code signing, Cryptographic erase/obfuscation, Digital signatures

More from the archive

Start a daily session

Several questions at a time, aimed at your gaps.