hardmultiple choiceObjective-mapped

Exhibit

Backup vault policy:
- Backup objects are encrypted with per-job data encryption keys (DEKs).
- A key-encryption key (KEK) named vault-kek-v1 wraps the DEKs.
- vault-kek-v1 will be rotated to vault-kek-v2 tonight.
- Existing backup metadata still points to DEKs wrapped by vault-kek-v1.
- Requirement: all backups from the last 18 months must remain restorable after rotation, with no mass re-encryption window.

Based on the exhibit, which action is required to keep the backups restorable after the key-encryption key rotation?

Question 1hardmultiple choice
Full question →

Based on the exhibit, which action is required to keep the backups restorable after the key-encryption key rotation?

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

Delete vault-kek-v1 immediately so only the newest key remains active.

Deleting the old KEK would break access to any DEKs still wrapped by that key. The exhibit states that existing backup metadata still depends on vault-kek-v1. Removing it before migration would make older backups unrecoverable, which directly conflicts with the restore requirement.

B

Best answer

Rewrap or keep access to the old KEK version until existing DEKs are migrated.

This is correct because the backups still depend on the old key-encryption key to unwrap their data-encryption keys. During key rotation, the organization must either keep the old KEK available or rewrap the DEKs with the new KEK before retiring the old one. That preserves restore capability without forcing a full mass re-encryption of the backup data.

C

Distractor review

Re-encrypt the entire backup repository with a single shared password.

A shared password is not an appropriate replacement for managed cryptographic keys, and re-encrypting the entire repository would be disruptive. The exhibit uses a proper DEK/KEK model, so the solution should preserve that structure. This option ignores the existing key hierarchy and the need to keep older backups recoverable during rotation.

D

Distractor review

Export vault-kek-v2 into the backup files so each object stores the new key directly.

Storing the new KEK directly in backup files would expose sensitive key material and undermine the whole purpose of key wrapping. Backups should store encrypted data and metadata, not plaintext keys. This would also make key management and rotation much harder, not easier.

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: Rewrap or keep access to the old KEK version until existing DEKs are migrated. — The correct action is to rewrap the DEKs or keep access to the old KEK version until all existing DEKs are migrated. In a DEK/KEK design, the data is encrypted by DEKs, and the KEK only protects those DEKs. If the backup objects still reference vault-kek-v1, then removing that KEK would prevent restores. Preserving the old key or rewrapping the DEKs allows rotation without breaking recovery. Why others are wrong: Deleting the old KEK would make older backups unreadable, which violates the restore requirement. Re-encrypting everything with a shared password is not a proper enterprise key-management approach and would be operationally weak. Putting the new KEK directly into the backup files would expose key material and defeats the purpose of key wrapping. The workflow must preserve access to the old wrapping key or migrate the wrapped DEKs first.

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.