mediummultiple choiceObjective-mapped

A help desk manager wants sample customer tickets copied into a test environment so developers can reproduce support issues. The tickets include names, phone numbers, and account details. Which action best reduces privacy exposure while still supporting testing?

Question 1mediummultiple choice
Full question →

A help desk manager wants sample customer tickets copied into a test environment so developers can reproduce support issues. The tickets include names, phone numbers, and account details. Which action best reduces privacy exposure while still supporting testing?

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

Export the full tickets because the developers need realistic records.

Copying full records exposes unnecessary personal information and increases privacy risk. Realistic data can often be preserved without full identifiers.

B

Best answer

Mask or tokenize the personal data and restrict access to approved testers only.

Masking or tokenizing personal data follows privacy-by-design principles by reducing exposure while preserving enough structure for testing. Limiting access further reduces the chance of improper handling. This approach allows developers to reproduce issues without using unnecessary real customer information, which supports data minimization and secure sharing requirements.

C

Distractor review

Copy the tickets to a shared cloud drive and protect it with a simple password.

A shared drive with a simple password is not sufficient protection for sensitive customer data. It does not minimize the data collected and often creates weak access control.

D

Distractor review

Remove the account numbers only and leave the rest of the ticket untouched.

Partial redaction helps, but names and phone numbers are still personal data. The scenario asks for the best way to reduce privacy exposure while supporting testing, which requires broader masking or tokenization.

Common exam trap

Common exam trap: usable hosts are not the same as total addresses

Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.

Technical deep dive

How to think about this question

Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.

KKey Concepts to Remember

  • CIDR notation defines the prefix length.
  • Block size helps identify subnet boundaries.
  • Network and broadcast addresses are not usable hosts in normal IPv4 subnets.
  • The required host count determines the smallest suitable subnet.

TExam Day Tips

  • Write the block size before choosing the subnet.
  • Check whether the question asks for hosts, subnets or a specific address range.
  • Do not confuse /24, /25, /26 and /27 host counts.

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?

CIDR notation defines the prefix length.

What is the correct answer to this question?

The correct answer is: Mask or tokenize the personal data and restrict access to approved testers only. — Masking or tokenizing the personal data is the best option because it reduces the amount of sensitive information exposed to the test environment while still allowing developers to work with realistic records. Restricting access to approved testers supports privacy-by-design and need-to-know principles. This approach is more secure than a full export and more effective than removing only one identifier, because it lowers the overall privacy risk across the dataset. Why others are wrong: Exporting the full tickets gives developers unnecessary access to customer data. A shared cloud drive with a simple password is weak access control and does not address data minimization. Removing only account numbers still leaves names and phone numbers exposed, so the privacy risk remains significant. The best answer must both support testing and reduce exposure, which masking or tokenization does.

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.