mediummultiple choiceObjective-mapped

Exhibit

Data export sample:
CustomerName, CardNumber, OrderTotal, Region
A. Lee, 4532 1100 8822 7744, 158.22, West
B. Patel, 6011 9009 1044 2219, 41.88, East
C. Jones, 6011 9010 3321 1197, 92.10, South

Business requirement:
- Analytics team needs repeated values for reporting and joins
- Full card numbers must not appear in reports or test data

Based on the exhibit, which data protection control best allows analysts to work with the records without exposing full card numbers?

Question 1mediummultiple choice
Full question →

Based on the exhibit, which data protection control best allows analysts to work with the records without exposing full card numbers?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Encrypt the entire analytics database and give the team the decryption key.

Encryption protects stored data, but anyone with the decryption key could still see full card numbers in reports. The requirement is to prevent exposure while preserving usefulness.

B

Best answer

Tokenize the card numbers and keep the token mapping in a secured vault.

Tokenization replaces sensitive card numbers with non-sensitive substitutes that can still support joins and repeated reporting without revealing the original values. Keeping the mapping in a secured vault protects the real numbers while allowing the analytics team to work with consistent placeholders. This fits the business need much better than simple encryption or masking alone.

C

Distractor review

Hash the card numbers with SHA-256 so the analytics team can reverse them later if needed.

Hashes are one-way and are not appropriate when the team needs stable, usable values for repeated records and reporting workflows. They also do not allow recovery of the original number.

D

Distractor review

Delete all but the last four digits from the production database immediately.

Truncation can reduce exposure, but it may remove useful data needed for reconciliation, analytics, or customer support. It is more destructive than the requirement calls for.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Related practice questions

Related SY0-701 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SY0-701 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Tokenize the card numbers and keep the token mapping in a secured vault. — Tokenization is the best control because it preserves referential consistency while preventing the full card number from appearing in ordinary reports or test data. The analytics team can still work with repeated values, perform joins, and analyze trends. The actual card numbers remain protected in a separate vault or token service, which is exactly the balance of usability and confidentiality the scenario requires. Why others are wrong: Database encryption protects data at rest but does not hide values from authorized report users. Hashing is not reversible and is poor for repeatable business records. Truncation reduces exposure, but it may remove too much detail and does not support the same reporting workflows as tokenization.

What should I do if I get this SY0-701 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.