Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your enterprise DevOps team is architecting a continuous integration and continuous deployment (CI/CD) pipeline on Google Cloud. The architecture spans a dedicated security project for key management (proj-kms-sec) and a pipeline project (proj-cicd-prod).
The pipeline requires Customer-Managed Encryption Keys (CMEK) to protect the following components:
us-central1 and us-east1us-central1us-central1How should you configure the Cloud KMS keys and IAM permissions to support envelope encryption across these CI/CD pipeline resources?
A global Cloud KMS key resides across multi-region infrastructure without geographical pin-pointing. The Cloud Build service account (@cloudbuild.gserviceaccount.com or custom service account) is the runtime identity executing CI/CD build steps.
us-central1). They do not support global KMS keys.us-central1 and us-east1). Global keys are only permitted for automatic replication.service-@gs-project-accounts.iam.gserviceaccount.com), not by the pipeline's Cloud Build execution service account.The requirement used Secret Manager with automatic replication exclusively, and the build steps performed manual client-side envelope decryption using KMS APIs directly inside pipeline scripts instead of relying on native CMEK service integrations.
Creating keys directly inside proj-cicd-prod keeps all resources in the same operational project. The roles/cloudkms.admin role grants administrative control over key rings and keys (such as setting IAM policies, updating rotation periods, and managing key versions), but does not grant cryptographic data plane permissions.
proj-cicd-prod) rather than the central security project (proj-kms-sec) violates enterprise governance principles.roles/cloudkms.admin does not contain permissions (cloudkms.cryptoKeyVersions.useToEncrypt or cloudkms.cryptoKeyVersions.useToDecrypt) required for cryptographic operations.roles/cloudkms.cryptoKeyEncrypterDecrypter to the Google-managed service identities (Secret Manager, Cloud Storage, and Artifact Registry service agents), which will cause resource creation and decryption to fail.The requirement was specifically to allow pipeline automation to administer and create new key rings dynamically via Terraform without enabling service-level CMEK at-rest encryption.
Customer-Managed Encryption Keys (CMEK) allow organizations to use Cloud Key Management Service (Cloud KMS) to control the Key Encryption Keys (KEKs) that protect data at rest. Under Google Cloud's envelope encryption model, services generate a local, unique Data Encryption Key (DEK) to encrypt the actual resource payload (such as a secret version, storage object, or container layer), and the DEK is subsequently encrypted using the KEK residing in Cloud KMS.
us-central1 and us-east1 satisfies the location constraints for all target services.us-central1 and us-east1, separate CMEK keys matching each replica region must be provisioned. The Secret Manager service identity (service-@gcp-sa-secretmanager.iam.gserviceaccount.com) must have roles/cloudkms.cryptoKeyEncrypterDecrypter on both regional keys to encrypt and decrypt the DEKs for secret versions in those regions.service-@gs-project-accounts.iam.gserviceaccount.com) and the Artifact Registry service agent (service-@gcp-sa-artifactregistry.iam.gserviceaccount.com) must be granted roles/cloudkms.cryptoKeyEncrypterDecrypter on the us-central1 KMS key.proj-kms-sec) isolates key lifecycle management from application workloads.Asymmetric signing keys use public/private key pairs (such as RSA or ECDSA) specifically designed for digital signatures and integrity verification. The roles/cloudkms.signerVerifier role allows principals to sign payloads with the private key or verify signatures with the public key.
GOOGLE_SYMMETRIC_ENCRYPTION purpose with AES-256).roles/cloudkms.signerVerifier role cannot perform cryptoKey.encrypt or cryptoKey.decrypt operations. Service agents attempting to wrap or unwrap Data Encryption Keys (DEKs) will receive permission denied errors.roles/cloudkms.cryptoKeyEncrypterDecrypter to perform symmetric key encryption.The team was implementing supply-chain security attestations (such as Binary Authorization) using Cloud KMS to sign container image digests rather than encrypting storage payloads at rest.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated