Courseiva
Google Cloud SecuritymediumMultiple ChoiceObjective-mapped

Cloud Digital Leader Google Cloud Security Practice Question

A data engineering team needs to store and manage database passwords and API keys used by their applications. Which Google Cloud service should they use?

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

Secret Manager

Secret Manager is designed to store secrets like passwords and API keys. Cloud KMS is for encryption keys. Cloud Key Management Service is for creating and managing cryptographic keys, not storing secrets. Cloud Storage is for objects.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Cloud KMS

    Why it's wrong here

    Cloud KMS is a cryptographic key management service that generates, rotates, and uses encryption keys to protect data, but it does not store secrets like database passwords; it stores key material. Access to Cloud KMS controls who can use a key for cryptographic operations, not who can retrieve a plaintext secret, and it does not provide secret versioning or application-level secret retrieval APIs. Treating keys as secrets misses the distinction between protecting data and storing credentials.

  • Secret Manager

    Why this is correct

    Secret Manager is the correct choice for storing and managing database passwords because it is a dedicated secrets-management service that provides versioning, fine-grained IAM permissions, and audit logging for each secret access. It encrypts secret values in transit and at rest, and integrates seamlessly with Compute Engine, GKE, Cloud Run, and Cloud Functions so applications can retrieve secrets at runtime via a simple API. This avoids hardcoding credentials and supports easy rotation.

  • Cloud Key Management Service

    Why it's wrong here

    Cloud Key Management Service is the full name for Cloud KMS, and while it is a centralized key vault for managing cryptographic keys, it is not a general-purpose secret store for passwords and API keys. A common misconception is that since keys are themselves secrets, the service can serve as a secret manager, but it lacks features like automatic secret rotation policies, secret versioning tied to application releases, and per-secret IAM roles for non-key material. Using it for database credentials would be an architectural anti-pattern.

  • Cloud Storage

    Why it's wrong here

    Cloud Storage is object storage for unstructured blobs, with bucket-level IAM and lifecycle policies, but it lacks native secret-versioning, rotation, and per-secret audit capabilities. Storing database passwords there would require bolting on client-side encryption and manually managing access control, which is error-prone and not a secure pattern. It is not designed for secret management.

About these practice questions

Courseiva writes every GCDL question from scratch — 829 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This GCDL practice question is part of Courseiva's free Google Cloud 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 GCDL exam.