The answer is to keep the private key in an HSM or secure escrow with tested recovery procedures. This is correct because separating the encryption key from the backup data eliminates a single point of failure; if the primary backup server is lost, the key remains accessible from a tamper-resistant HSM or a securely escrowed copy, ensuring you can still decrypt and restore the data. On the Security+ SY0-701 exam, this tests your understanding of key management and fault tolerance—a common trap is assuming that simply backing up the key alongside the data is sufficient, which actually creates a cascading failure. Remember the memory tip: "Key apart, backup smart"—always keep the key in a separate, hardened location like an HSM to guarantee recoverability.
SY0-701 General Security Concepts Practice Question
This SY0-701 practice question tests your understanding of general security concepts. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Clue: "primary"
Why it matters: Asks for the main purpose or function, not a secondary benefit. Eliminate answers that describe side-effects or partial functions.
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
A
Store the private key on the same backup server so recovery is faster.
Why wrong: 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
Replace AES with hashing so the archive no longer needs a key.
Why wrong: 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
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
Send the private key to backup operators by email so they can restore data quickly.
Why wrong: 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.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Keep the private key in an HSM or secure escrow with tested recovery procedures.
Option C is correct because storing the private key in a Hardware Security Module (HSM) or secure escrow ensures it remains available even if the primary backup server is lost. HSMs provide tamper-resistant key storage and support tested recovery procedures, which is critical for decrypting backups and maintaining recoverability. This approach separates the key from the backup data, preventing a single point of failure.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Store the private key on the same backup server so recovery is faster.
Why it's wrong here
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.
✗
Replace AES with hashing so the archive no longer needs a key.
Why it's wrong here
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.
✓
Keep the private key in an HSM or secure escrow with tested recovery procedures.
Why this is correct
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.
Clue confirmation
The clue words "best", "primary" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Send the private key to backup operators by email so they can restore data quickly.
Why it's wrong here
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 traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may assume storing the key with the backup data (Option A) is efficient, but they overlook that it destroys recoverability when the server is lost, which is the exact failure scenario the question describes.
Detailed technical explanation
How to think about this question
A Hardware Security Module (HSM) is a dedicated cryptographic device that generates, stores, and manages keys in a hardened, tamper-resistant environment, often with FIPS 140-2/140-3 validation. In backup scenarios, the private key used for decryption should be escrowed in an HSM or a secure key management system with documented recovery workflows, such as key ceremony procedures or split-key schemes. This ensures that even if the backup server is destroyed, the key can be retrieved from a separate, trusted location to restore encrypted archives.
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.
TExam Day Tips
→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.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A developer is choosing between AES-256 (symmetric) and RSA-2048 (asymmetric) for encrypting a large file that will be sent to a partner. Symmetric encryption is fast but requires key exchange; asymmetric is slower but solves the key distribution problem. A hybrid approach — encrypt the file with AES, encrypt the AES key with RSA — is standard. Questions like this test whether you understand when each approach applies.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this SY0-701 question in full detail.
General Security Concepts — This question tests General Security Concepts — 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. — Option C is correct because storing the private key in a Hardware Security Module (HSM) or secure escrow ensures it remains available even if the primary backup server is lost. HSMs provide tamper-resistant key storage and support tested recovery procedures, which is critical for decrypting backups and maintaining recoverability. This approach separates the key from the backup data, preventing a single point of failure.
What should I do if I get this SY0-701 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "best", "primary". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Based on the exhibit, what should be implemented to reduce the blast radius if a backup server is compromised later?
Backup job configuration:
algorithm=AES-256-GCM
key_file=/opt/backup/key.bin
rotation=disabled
same_key_for_all_sites=true
backup_media copied to an offsite vault each night
hard
✓ A.Use envelope encryption with unique data encryption keys protected by a KMS-managed key encryption key.
B.Store the same key in a password-protected ZIP archive on the backup server.
C.Replace AES with SHA-256 so the files cannot be opened directly.
D.Keep one key forever and increase the backup frequency.
Why A: Envelope encryption with unique data encryption keys (DEKs) protected by a KMS-managed key encryption key (KEK) ensures that even if the backup server is compromised, the attacker cannot decrypt all backups because each backup uses a different DEK, and the KEK is stored externally in a KMS. This limits the blast radius to only the data encrypted with the compromised DEK, rather than exposing all historical backups encrypted with a single static key.
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This SY0-701 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SY0-701 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.