easyMultiple Choice
CCSP Practice Question: A cloud security architect is designing a key…
A cloud security architect is designing a key management strategy for a multi-cloud environment. Which of the following is a BEST practice for key management?
⚠ Common exam trap
ISC2 often tests the misconception that using each cloud provider's native KMS separately is a best practice for multi-cloud, but the trap is that this ignores the need for centralized control, auditability, and cross-cloud interoperability, which are critical for enterprise security.
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
✓
Use a centralized key management system that integrates with all clouds
A centralized key management system (KMS) that integrates with all cloud providers enables consistent key lifecycle management, reduces the risk of key sprawl, and ensures uniform access control policies across a multi-cloud environment. This approach aligns with the principle of separation of duties and allows for centralized auditing and rotation without vendor lock-in.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use the same key for all data to simplify rotation
Why it's wrong here
Reusing one key across all data removes cryptographic separation, so compromise of that single key exposes every dataset and rotation becomes a mass re-encryption event. It is tempting because fewer keys appear to simplify rotation, which holds only for a single low-value dataset.
- ✗
Store keys in each cloud provider's native KMS separately
Why it's wrong here
Separate native KMS stores per cloud fragment the key lifecycle, preventing centralised policy, audit and revocation across the multi-cloud estate. It is tempting because native KMS integrates tightly within each provider, which suits a single-cloud deployment where no cross-provider governance is required.
- ✗
Embed keys in application code for simplicity
Why it's wrong here
Embedding keys in code exposes them to anyone with repository or build access, and rotation demands redeployment. The scenario requires a multi-cloud key management strategy, which this cannot deliver. It is tempting because hard-coded keys avoid runtime secret lookups, and would suit a disposable local prototype with no shared repository.
- ✓
Use a centralized key management system that integrates with all clouds
Why this is correct
A centralised key management system provides consistent policy, lifecycle, and auditing across all cloud providers, avoiding fragmented per-cloud key stores. This satisfies the multi-cloud constraint by unifying key governance while integrating with each provider's native encryption services.
Go deeper
Related to this question
About these practice questions
One of 934 original CCSP practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CCSP practice question is part of Courseiva's free ISC2 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 CCSP exam.