Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise organization stores database credentials in Google Cloud Secret Manager. The security team must implement continuous credential hygiene for these database secrets according to the following requirements:
Which workflow and architectural configuration should the security engineer implement?
Secret Manager automated rotation is a native lifecycle management capability that automatically schedules credential updates and invokes custom automation routines via Cloud Pub/Sub and serverless compute like Cloud Functions or Cloud Run.
next-rotation-time and rotation-period=2592000s (30 days) on the Secret Manager resource instructs Google Cloud to automatically trigger rotation events at the specified interval.ROTATION) to the configured Pub/Sub topic whenever the rotation timer elapses.service-@gcp-sa-secretmanager.iam.gserviceaccount.com) is granted the roles/pubsub.publisher role strictly on the designated topic, adhering to least-privilege principles.secrets.addVersion), verifies application access, and sets the state of the older version to Disabled (secrets.versions.disable).roles/secretmanager.secretVersionManager.This architecture leverages the purpose-built Secret Manager rotation framework, ensuring dependable event dispatching, decoupled execution, and continuous credential hygiene without service interruption.
This setup applies an expiration timestamp (expire-time or ttl) directly to the secret resource in Secret Manager, while attempting to manage rotated credentials through Cloud Storage object lifecycle notifications.
expire-time or ttl causes the secret and all of its versions to become permanently inaccessible or destroyed once the timestamp passes, causing complete application outage.The organization needed to enforce strict data retention limits to guarantee that temporary staging secrets were permanently deleted after 30 days.
This approach uses Cloud Scheduler as an external timer to call an HTTP-triggered Cloud Function, which attempts to overwrite secret payloads in place and relies on default service accounts.
rotation-period and Pub/Sub notification mechanisms, leading to fragmented governance across scheduling tools.secrets.addVersion) rather than modifying existing versions in place.Editor permissions across project resources, violating the requirement for least privilege.The organization had to trigger custom batch operations against a legacy third-party key vault that lacked native rotation scheduling and Pub/Sub webhook integrations.
This configuration listens for audit log entries emitted during Secret Manager changes via Eventarc and uses Cloud Build to bake updated secret values into container environment variables during redeployment.
SecretUpdate are generated after a change has occurred, making it unsuitable for initiating scheduled, proactive 30-day credential rotations.The goal was to trigger an audit pipeline whenever an administrator manually modifies metadata or permissions on a Secret Manager secret.
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