SCS-C02 CloudHSM Backup Practice Question
A company uses AWS CloudHSM to generate and store encryption keys for a custom application. The security team is concerned about key durability and wants to ensure that keys are not lost if the HSM fails. Which action should be taken?
⚠ Common exam trap
Candidates may mistakenly believe that exporting keys to an EBS volume or using KMS provides adequate durability, but CloudHSM's native backup and restore mechanism is the correct method to protect against HSM failure.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Regularly back up the HSM to an Amazon S3 bucket and restore to a new cluster if needed
AWS CloudHSM supports taking backups of the HSM content to an Amazon S3 bucket. These backups can be used to restore to a new HSM cluster in case of failure, ensuring key durability. Option A is incorrect because CloudHSM clusters are single-region; multi-region clusters are not supported. Option B is incorrect because storing keys on an encrypted EBS volume bypasses the security of the HSM and is not a recommended practice for key durability. Option C is incorrect because AWS KMS cannot directly import keys from CloudHSM; KMS and CloudHSM are separate services with different key management capabilities.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create a multi-region CloudHSM cluster
Why it's wrong here
CloudHSM clusters are confined to a single AWS region and consist of HSMs deployed across Availability Zones within that region; there is no multi-region cluster construct. Attempting to configure a cluster spanning regions is not supported by the CloudHSM service. If cross-region resilience is required, you must back up the cluster and restore the backup to a separate cluster in another region.
- ✗
Store the keys in a file on an encrypted EBS volume
Why it's wrong here
Storing encryption keys in a file on an encrypted EBS volume moves the key material out of the tamper-resistant CloudHSM hardware into software, where it can be accessed by the OS and any privileged process. Even if the volume is encrypted at rest, the key is available in plaintext in memory during runtime and bypasses the HSM's non-exportability guarantees. This approach violates the fundamental requirement that keys never leave the HSM in a usable form.
- ✗
Use AWS KMS to import the keys from CloudHSM
Why it's wrong here
AWS KMS does not provide an operation to import key material directly from a CloudHSM; key material can only be imported into KMS using the import key material feature, which requires wrapping a plaintext key with a public key from a KMS key. CloudHSM keys are designed to be non-exportable—the service does not allow you to extract key material from an HSM—so there is no source plaintext available for import. The only integration between KMS and CloudHSM is a custom key store, which uses CloudHSM as the underlying storage for KMS keys rather than migrating existing CloudHSM keys into KMS.
- ✓
Regularly back up the HSM to an Amazon S3 bucket and restore to a new cluster if needed
Why this is correct
CloudHSM automatically stores encrypted backups of each HSM partition in Amazon S3, and you can schedule backups on a regular basis to protect against hardware failure or cluster loss. These backups capture the HSM's key material and data in an encrypted, point-in-time snapshot that can be restored to a new cluster in the same region. By regularly backing up, you ensure that if the cluster becomes unavailable, you can launch a new cluster and restore the backup, preserving access to the keys. This is the supported disaster-recovery mechanism for CloudHSM.
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
About these practice questions
This SCS-C02 question is part of Courseiva's 1,205-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SCS-C02 practice question is part of Courseiva's free Amazon Web Services 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 SCS-C02 exam.