PROFESSIONAL-CLOUD-DEVOPS-ENGINEER practice question 5 of 25

You are deploying an application that needs to access sensitive information. You need to ensure that this information is encrypted and the risk of exposure is minimal if a breach occurs. What should you do?

Full set: 205 questions
Answer options
A: Store the encryption keys in Cloud Key Management Service (KMS) and rotate the keys frequently Correct answer
B: Inject the secret at the time of instance creation via an encrypted configuration management system.
C: Integrate the application with a Single sign-on (SSO) system and do not expose secrets to the application
D: Leverage a continuous build pipeline that produces multiple versions of the secret for each instance of the application.
Correct Answer:
A. Store the encryption keys in Cloud Key Management Service (KMS) and rotate the keys frequently
Explanation

To encrypt sensitive information and minimize risk, a robust key management system is essential. Cloud Key Management Service (KMS) provides a secure, centralized service for managing cryptographic keys. Storing the encryption keys in Cloud KMS ensures they are protected by hardware security modules (HSMs). Regularly rotating these keys is a critical security best practice that limits the potential impact if a key is ever compromised, reducing the "blast radius" of a breach.

Why Incorrect

B. Inject the secret at the time of instance creation via an encrypted configuration management system: This is a viable pattern but less secure, as the secret still resides on the instance, increasing its exposure to other processes or potential attackers on that machine.
C. Integrate the application with a Single sign-on (SSO) system and do not expose secrets to the application: SSO is a system for user authentication and authorization, not for providing application-level secrets like database credentials or API keys to a workload.
D. Leverage a continuous build pipeline that produces multiple versions of the secret for each instance of the application: This unnecessarily increases complexity and the number of secrets to manage, which generally increases, rather than minimizes, security risk.

References

1. Google Cloud Documentation, "Cloud Key Management Service documentation". The overview states, "Cloud KMS is a centralized cloud service that allows you to manage cryptographic keys... It provides a root of trust for your data."

2. Google Cloud Documentation, "Secret Manager documentation". Secret Manager is the recommended service for storing secrets, and it integrates directly with Cloud KMS for encryption. The documentation on "Editing secrets" describes how to set a rotation schedule for secrets. Option A describes the underlying cryptographic best practice (key management and rotation) that enables services like Secret Manager.

3. Google Cloud Security Foundations Guide, "Managing secrets". This guide recommends using Secret Manager, which leverages Cloud KMS for encryption, and emphasizes the importance of rotating secrets and keys.

Scroll to Top