Organization policies in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the effect of Organization Policy constraints

You have set the constraint constraints/compute.disableSerialPortAccess to ENFORCED at the organization level in Google Cloud. What is the expected behavior for all VM instances in projects under this organization?

A All VM instances will have serial port access disabled, regardless of project or instance-level settings.

B VM instances can override this setting at the project level to enable serial port access.

C Only new VM instances created after the policy is set will have serial port access disabled.

D The policy only applies to VM instances in projects with billing enabled.

💡 Hint

Think about how organization policies enforce constraints across all projects and resources.

Organization policies with constraints set to ENFORCED apply to all resources under the organization and cannot be overridden at lower levels. Therefore, serial port access is disabled for all VM instances regardless of project or instance settings.

❓ Architecture

intermediate

Applying Organization Policies to restrict resource locations

You want to restrict all projects in your organization to create resources only in the us-central1 and us-east1 regions. Which organization policy constraint should you apply, and where should it be set?

A Set the <code>constraints/compute.allowedRegions</code> constraint with allowed values <code>us-central1</code> and <code>us-east1</code> at the folder level.

B Set the <code>constraints/gcp.resourceLocations</code> constraint with allowed values <code>us-central1</code> and <code>us-east1</code> at the project level.

C Set the <code>constraints/gcp.resourceLocations</code> constraint with allowed values <code>us-central1</code> and <code>us-east1</code> at the organization level.

D Set the <code>constraints/compute.allowedRegions</code> constraint with allowed values <code>us-central1</code> and <code>us-east1</code> at the organization level.

💡 Hint

Consider which constraint controls resource location restrictions and the scope of enforcement.

The constraints/gcp.resourceLocations constraint controls where resources can be created. Setting it at the organization level restricts all projects under it. The constraints/compute.allowedRegions constraint does not exist.

❓ security

advanced

Impact of Organization Policy on Service Account Key creation

An organization policy is set to constraints/iam.disableServiceAccountKeyCreation with ENFORCED at the folder level. What will happen if a user tries to create a new service account key in a project under that folder?

A Service account key creation is allowed but keys will be automatically rotated.

B Users can create service account keys if they have the <code>iam.serviceAccountKeyAdmin</code> role.

C The policy only blocks key creation if set at the project level, not folder level.

D The creation of new service account keys will be blocked for all projects under the folder.

💡 Hint

Think about how organization policies propagate and enforce security constraints.

The constraints/iam.disableServiceAccountKeyCreation constraint set to ENFORCED at the folder level blocks all service account key creation in projects under that folder, regardless of user roles.

❓ service_behavior

advanced

Behavior of conflicting Organization Policies at different levels

An organization policy constraints/compute.vmExternalIpAccess is set to ENFORCED at the organization level to deny external IPs on VMs. However, at a specific project, the same constraint is set to NOT_ENFORCED. What is the effective behavior for VM instances in that project?

A Both policies are merged, causing an error and blocking VM creation.

B The organization-level policy overrides the project-level setting, so external IPs are denied on VMs.

C The VM instances will have external IPs allowed only if explicitly set during creation.

D The project-level policy overrides the organization-level, allowing external IPs on VMs.

💡 Hint

Consider the hierarchy and precedence of organization policies.

Organization policies set at higher levels (organization) override conflicting policies at lower levels (project). Therefore, the ENFORCED deny on external IPs at the organization level takes precedence.

✅ Best Practice

expert

Designing Organization Policies for multi-team environment

Your company has multiple teams managing projects under a single organization. You want to enforce a policy that restricts VM instance machine types to a predefined list but allow teams to add more machine types if needed. What is the best way to implement this using organization policies?

A Set <code>constraints/compute.allowedMachineTypes</code> at the organization level with the predefined list, and require teams to request changes through a central admin to update the policy.

B Set <code>constraints/compute.allowedMachineTypes</code> at the organization level with the predefined list, and allow projects to add exceptions using policy inheritance and overrides.

C Do not set any organization policy and rely on IAM roles to restrict machine types per team.

D Set the constraint only at the project level for each team with their allowed machine types.

💡 Hint

Think about how organization policies enforce constraints and how exceptions can be managed.

Organization policies do not support additive overrides for allowed values. To maintain control and security, set the allowed machine types at the organization level and require teams to request changes through a central admin who updates the policy. This ensures consistent enforcement and auditability.