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 organization is bootstrapping its landing zone across multiple Google Cloud folders and projects. As a DevOps engineer, you are tasked with defining baseline preventative controls at the organization node to establish security guardrails across the entire resource hierarchy while still allowing folder- or project-level exceptions where strictly necessary.
Your implementation must satisfy the following requirements:
Which set of organization policy constraints should you configure and enforce at the organization node?
compute.disableVpcExternalIpv6 boolean constraint, set the iam.automaticIamGrantsForDefaultServiceAccounts constraint to true, and configure storage.publicAccessPrevention at the organization node.This option enforces three valid Google Cloud organization policy constraints: disabling external IPv6 subnets (compute.disableVpcExternalIpv6), stopping automatic IAM grants to default service accounts (iam.automaticIamGrantsForDefaultServiceAccounts), and blocking public access to Cloud Storage buckets (storage.publicAccessPrevention).
compute.disableVpcExternalIpv6 only restricts external IPv6 addresses on subnets, leaving default external IPv4 addresses completely unrestricted on Compute Engine instances.compute.skipDefaultNetworkCreation).storage.publicAccessPrevention applies solely to Cloud Storage buckets and has zero impact on Cloud SQL networking.The organizational requirements focused on Cloud Storage bucket permissions, external IPv6 subnet provisioning, and default service account IAM role curtailment.
0.0.0.0/0 at the organization root and implement IAM Deny policies targeting compute.instances.create and sql.instances.create across all folders.This approach uses hierarchical firewall policies to block outbound network traffic globally at the network layer and attempts to use IAM Deny policies to block developers from invoking instance creation permissions.
compute.instances.create completely disables VM provisioning rather than allowing compliant internal-only VM creations.The requirement was to enforce traffic microsegmentation across VPC networks and restrict broad API permissions rather than establishing preventative resource configuration guardrails.
compute.googleapis.com/Instance and sqladmin.googleapis.com/Instance and enforce them individually on each project without configuring policies at the organization root.This option builds custom organization policy constraints written with Common Expression Language (CEL) and attempts to enforce them individually at the project level instead of utilizing built-in managed constraints at the root of the hierarchy.
compute.vmExternalIpAccess, compute.skipDefaultNetworkCreation, sql.restrictPublicIp) designed specifically for these exact controls. Writing custom constraints introduces unnecessary maintenance overhead.You needed to restrict specialized resource parameters or attributes that are not covered by any existing Google-managed organization policy constraints.
compute.vmExternalIpAccess constraint with a policy denying all external IP addresses, enforce the compute.skipDefaultNetworkCreation boolean constraint set to true, and enforce the sql.restrictPublicIp boolean constraint set to true at the organization node.The Organization Policy Service provides centralized, programmatic guardrails that govern resource configurations across an entire Google Cloud resource hierarchy. Applying managed constraints at the organization node ensures that preventative security baselines automatically cascade down to all child folders, projects, and resources via inheritance, even restricting users with privileged project-level IAM roles.
compute.vmExternalIpAccess with a list policy configured to deny all external IP values (or an empty allowlist) blocks Compute Engine instances from being assigned public IPv4 addresses upon creation or network interface update.compute.skipDefaultNetworkCreation ensures that when the Compute Engine API is activated in newly created projects, Google Cloud skips the generation of the default VPC network and its default firewall rules.sql.restrictPublicIp blocks the assignment of public IP addresses on Cloud SQL database instances, requiring workloads to leverage private IP networking or authorized proxy configurations.Leveraging Google-managed organization policy constraints (compute.vmExternalIpAccess, compute.skipDefaultNetworkCreation, and sql.restrictPublicIp) is the native, platform-recommended mechanism to establish strict infrastructure configuration guardrails across the organization resource hierarchy.
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