Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
A Cloud Solutions Architect is using natural language prompts in Gemini Cloud Assist to generate Terraform Infrastructure as Code (IaC) and deployment scripts for a secure internal workload on Compute Engine.
The organizational security policy dictates the following technical requirements:
default VPC network.Which infrastructure architecture and configuration generated by Gemini Cloud Assist meets all organizational technical and security requirements while adhering to Google Cloud best practices?
access_config block configured with External NAT to the network interface, and assign the roles/compute.admin role to the default Compute Engine service account.This configuration generates a custom VPC network but includes an access_config block set to ONE_TO_ONE_NAT (External NAT) on the VM network interface and grants high-privilege IAM permissions to the default service account.
access_config block explicitly allocates and assigns a public IPv4 address to the VM instance, directly violating the requirement that VMs must not have public/external IPs.roles/compute.admin, which violates both the custom service account requirement and least-privilege security standards.access_config block exposes the instance directly to inbound internet traffic unless firewalled off.The workload required direct public ingress on individual VMs and permitted the use of default project identities.
When reviewing IaC generated by AI assistants, architects must verify that snippet templates (such as basic quickstarts) do not accidentally retain public access_config parameters or excessive default credentials.
terraform-google-project-factory module to create resources within the default VPC, configure private Google access only, and grant roles/compute.imageUser to allAuthenticatedUsers.This option deploys infrastructure inside the default VPC network using Private Google Access for external communication and opens Compute Engine image permissions to allAuthenticatedUsers.
roles/compute.imageUser to allAuthenticatedUsers makes custom disk images accessible to any authenticated Google Cloud user worldwide, representing a critical security flaw.allAuthenticatedUsers allows any valid Google account outside your organization to read the specified resource.The VMs only needed connectivity to Google Cloud APIs and the images were intentionally published as public marketplace artifacts.
Distinguishing between Private Google Access (Google endpoints only) and Cloud NAT (general outbound internet egress) is essential when architecting private VPC workloads.
access_config block from the VM network interface.This solution uses Gemini Cloud Assist to generate Terraform Infrastructure as Code (IaC) that establishes an enterprise-grade, secure private compute architecture adhering to the Google Cloud Well-Architected Framework.
access_config block inside network_interface ensures that the VM instances are provisioned without an external (public) IP address.This approach directly satisfies every security requirement while adopting standard Google Cloud best practices for network isolation, controlled egress, and identity governance.
default VPC network, attaches Cloud NAT to the default gateway, and configures an instance template with the default service account and cloud-platform access scope.This option provisions the compute instances inside the project's default VPC network using gcloud CLI commands and attaches the default Compute Engine service account with full API access scopes.
default VPC network. The default network contains pre-configured firewall rules that are not tailored for secure production workloads.cloud-platform scopes violates the organizational requirement for a custom least-privilege service account.default-allow-ssh) that open ports globally.cloud-platform access scope on a default service account delegates all permission boundaries solely to IAM without defense-in-depth token isolation.The environment were a temporary sandbox where default networks and rapid prototyping take precedence over governance policies.
Google Cloud best practices strongly advise deleting or disabling the default network in enterprise landing zones and building isolated custom VPCs.
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