nerdexam
Google

PROFESSIONAL-CLOUD-DEVOPS-ENGINEER · Question #20

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…

The correct answer is A. Store the encryption keys in Cloud Key Management Service (KMS) and rotate the keys. To protect sensitive information by encryption and minimize exposure risk, store encryption keys in Cloud Key Management Service (KMS) and regularly rotate them.

Submitted by ravi_2018· Apr 18, 2026Applying site reliability engineering principles to a service

Question

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?

Options

  • AStore the encryption keys in Cloud Key Management Service (KMS) and rotate the keys
  • BInject the secret at the time of instance creation via an encrypted configuration management
  • CIntegrate the application with a Single sign-on (SSO) system and do not expose secrets to the
  • DLeverage a continuous build pipeline that produces multiple versions of the secret for each

How the community answered

(27 responses)
  • A
    74% (20)
  • B
    7% (2)
  • C
    15% (4)
  • D
    4% (1)

Why each option

To protect sensitive information by encryption and minimize exposure risk, store encryption keys in Cloud Key Management Service (KMS) and regularly rotate them.

AStore the encryption keys in Cloud Key Management Service (KMS) and rotate the keysCorrect

Cloud Key Management Service (KMS) is a highly secure and managed service for cryptographic keys. Storing encryption keys in KMS ensures they are protected by Google's infrastructure, are auditable, and allows for automatic or manual rotation. Regular key rotation limits the amount of data encrypted by a single key, reducing the impact if a key is ever compromised, thus minimizing the risk of exposure during a breach.

BInject the secret at the time of instance creation via an encrypted configuration management

While injecting secrets at instance creation via an encrypted configuration management system is a valid pattern, KMS provides a dedicated, managed service for secure key storage and lifecycle management, including rotation, offering a higher level of security specifically for encryption keys.

CIntegrate the application with a Single sign-on (SSO) system and do not expose secrets to the

Integrating with an SSO system manages user authentication and authorization but does not directly address the encryption of sensitive data accessed by the application itself or the secure storage of its encryption keys.

DLeverage a continuous build pipeline that produces multiple versions of the secret for each

A continuous build pipeline producing 'multiple versions of the secret' is not a standard or secure practice for managing sensitive data and doesn't inherently ensure encryption or minimize exposure in the way a KMS does for encryption keys.

Concept tested: Secret management, encryption key management, Cloud KMS

Source: https://cloud.google.com/kms/docs/overview

Topics

#Cloud KMS#Key Management#Secret Management#Security Best Practices

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice