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.
A financial enterprise is establishing a secure cloud development environment on Google Cloud to support sensitive application engineering workloads under strict regulatory compliance. The architecture must satisfy the following security specifications:
Which configuration steps should the DevOps engineer implement?
This solution implements an enterprise-grade secure development environment by combining Secure Source Manager, Private Service Connect (PSC), Customer-Managed Encryption Keys (CMEK), and VPC Service Controls (VPC SC).
This architecture directly aligns with Google Cloud security best practices by implementing defense-in-depth across the network, storage, and identity layers.
This configuration sets up a traditional Compute Engine jump host (bastion VM) with a public IP address, using OS Login with 2-Step Verification for developer SSH access and granting intrusion detection administrative roles.
roles/ids.admin gives broad permissions to manage Cloud IDS packet mirroring and intrusion detection endpoints, which developers do not need and which fails the principle of least privilege.The primary goal was providing legacy SSH jump-host access to private VMs on a network without IAP support, and the team required direct administrative management over Cloud IDS endpoints.
This approach attempts to secure source repositories by relying on transport layer encryption (TLS), organization-level asymmetric encryption keys, and hierarchical firewall rules to block unauthorized public ingress.
The workload was hosted entirely on standalone Compute Engine instances exposed to the internet, requiring public PKI authentication and traditional IP perimeter filtering rather than managed Google Cloud service perimeters.
This option configures multi-VPC transit connectivity using VPC Network Peering, manages access credentials inside Secret Manager, and defines an Access Context Manager access level that permits traffic from any public IP address range (0.0.0.0/0).
The architecture required an open public API gateway with client-side credential storage in Secret Manager rather than a hardened, private, compliance-enforced development environment.
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