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 uses automated CI/CD pipelines that dynamically provision ephemeral Google Cloud projects to run integration tests and validate containerized workloads. These temporary environments create Compute Engine instances, Cloud Storage buckets, and analytical clusters before being destroyed.
Your security team mandates the following governance requirements for all ephemeral environments:
Which combination of Google Cloud security controls and configuration management policies should you implement?
This architecture combines Organization Policies, VPC Service Controls (VPC SC), and Privileged Access Manager (PAM) to establish an automated, zero-trust security baseline for short-lived cloud environments.
iam.disableServiceAccountKeyCreation constraint at the folder level ensures that any dynamically provisioned project inside that folder automatically inherits the restriction, blocking the generation of long-lived service account keys.This approach aligns with Google Cloud security best practices by automating guardrails via the resource hierarchy and enforcing strict perimeter boundaries, ensuring temporary environments maintain the same security rigor as production systems.
This approach attempts to use domain-wide delegation to grant broad administrative power to service accounts, relies on BigQuery log export queries for retrospective compliance checks, and attempts to suppress service account keys via Compute Engine instance metadata.
The organization required offline security analytics and historical telemetry reporting rather than real-time preventive governance and automated guardrails.
This approach uses OS Login 2-step verification for server administration, manages context-aware access using multiple Cloud Identity Access Bindings, and relies on VPC firewall rules for network security.
OR semantics, which can unintentionally weaken context-aware security and fails to provide dedicated just-in-time privilege workflows.The primary goal was strictly to secure interactive developer SSH sessions to compute instances without addressing API data exfiltration, service account lifecycle constraints, or just-in-time IAM role elevations.
This setup assigns permanent Organization Administrator (roles/resourcemanager.organizationAdmin) privileges to developers, configures Cloud NAT for outbound internet routing, and persists generated service account key JSON files inside Secret Manager.
roles/resourcemanager.organizationAdmin provides unrestricted control over the entire Google Cloud resource hierarchy, representing a critical security anti-pattern.The objective was to provide private VMs with outbound internet connectivity to download external packages while centrally rotating application secrets.
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