mediummultiple choiceObjective-mapped

A development manager wants to copy a production customer database into a test environment so testers can reproduce a bug. The database contains names, addresses, and payment tokens. What is the best security practice before the copy is made?

Question 1mediummultiple choice
Full question →

A development manager wants to copy a production customer database into a test environment so testers can reproduce a bug. The database contains names, addresses, and payment tokens. What is the best security practice before the copy is made?

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

Copy the production database unchanged and limit access to the QA team.

Limiting access helps, but the test environment would still contain unnecessary real customer data. That increases privacy risk and could expose sensitive information outside production controls. A safer process is to reduce or replace the sensitive data before it reaches the test system.

B

Best answer

Mask, tokenize, or replace sensitive fields with approved test data before moving it.

Masking or tokenizing sensitive fields is the best practice because it preserves the data structure needed for testing while reducing privacy risk. The test environment should not contain raw customer information unless there is a strong approved need. Using approved test data limits exposure if the environment is compromised or shared more broadly than intended.

C

Distractor review

Compress the database export to reduce storage and transfer time.

Compression can make the file smaller, but it does nothing to protect sensitive content. The same real customer data would still be present in the test copy. This option improves logistics, not privacy, and does not address the actual security concern in the scenario.

D

Distractor review

Encrypt the database backup and give developers the decryption key.

Encryption is useful for protecting data at rest, but handing developers the decryption key means the sensitive data is still available to anyone with access. The issue is whether production data should be copied in raw form at all. Masking or tokenization is a better privacy control before the copy occurs.

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, tokenize, or replace sensitive fields with approved test data before moving it. — The best practice is to mask, tokenize, or replace sensitive fields before copying the database into test. That keeps the test environment useful for troubleshooting while avoiding unnecessary exposure of real customer information. Because names, addresses, and payment tokens are sensitive, the goal is to preserve functionality without retaining full production data where it is not needed. Why others are wrong: Copying the database unchanged leaves real customer data exposed in a less controlled environment. Compression reduces file size only and offers no privacy benefit. Encryption helps protect the file, but if developers have the key, the sensitive data is still accessible. The safer choice is to reduce the sensitivity of the data before the copy is made.

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.