hardmultiple choiceObjective-mapped

Exhibit

Backup job design
- Generate a random AES key to encrypt 8 TB of archive data
- Encrypt the AES key with the backup server’s public key
- Store the encrypted AES key alongside the archive
- Secondary site must restore the data if the primary backup server is unavailable
- Current design stores the corresponding private key only on the primary server

Based on the exhibit, which key management improvement best preserves recoverability if the primary backup server is lost?

Question 1hardmultiple choice
Full question →

Based on the exhibit, which key management improvement best preserves recoverability if the primary backup server is lost?

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

Store the private key on the same backup server so recovery is faster.

Putting the private key on the same server creates a single point of failure and weakens key protection. If the server is lost, compromised, or destroyed, the organization may also lose the ability to decrypt the backup key material.

B

Distractor review

Replace AES with hashing so the archive no longer needs a key.

Hashing is one-way and cannot be used to restore encrypted backup data. It is useful for integrity checks, not for decrypting archives. This suggestion would eliminate recoverability rather than improve it.

C

Best answer

Keep the private key in an HSM or secure escrow with tested recovery procedures.

The private key must be protected separately from the primary backup server so the encrypted AES key can still be recovered if the server is lost. An HSM or secure escrow improves key protection while preserving recoverability, especially when paired with tested restoration procedures and restricted access controls.

D

Distractor review

Send the private key to backup operators by email so they can restore data quickly.

Emailing the private key exposes it to interception, forwarding, and unauthorized access. That undermines key confidentiality and creates unnecessary risk. Recovery should be possible without distributing the private key broadly or insecurely.

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: Keep the private key in an HSM or secure escrow with tested recovery procedures. — The best improvement is to keep the private key in an HSM or secure escrow with tested recovery procedures. The exhibit shows the AES data key is wrapped with the backup server’s public key, so recovery depends on the matching private key. If the private key exists only on the primary server, a loss event could make the backups unusable. Secure escrow preserves both protection and recoverability. Why others are wrong: Storing the private key on the same server creates a dangerous single point of failure. Hashing cannot replace encryption because it is not reversible. Emailing the key would expose sensitive material to unauthorized parties and is not an acceptable recovery practice. The correct answer balances confidentiality of the key with the organization’s need to restore encrypted backups later.

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.