SaveMyCert
Log in
5 of 5 free questions left today·for 10 a day
ACE · Domain 1

Setting up a cloud solution environment practice questions

Setting up a cloud solution environment is worth 20% of the ACE exam — the 3rd-heaviest of the 4 domains. Setting up cloud projects, accounts, and billing on Google Cloud. Official (approximate) weighting ~20%. 6 fully worked examples are further down this page, answers included.

Exam weight
20%
the 3rd-heaviest of the 4 domains
Questions
92
across 2 topics
Free, no account
5/day
a free account allows 10 a day
Explanations
Every option
right and wrong

Build a practice session

5 free questions left today.

Domains

How many?

5 free questions left today.

Mode

Ready when you are

10 fresh questions drawn across 1 of 4 domains, in Learn mode.

Review what you missed

Every question you answer incorrectly, and every question you flag while practising, is saved here automatically. Finish a session and you can come back to re-drill just those.

6 sample Setting up a cloud solution environment questions, fully explained

Questions from the ACE bank mapped to domain 1, with the answer key and the reasoning behind every option. None of them repeat the examples on the main ACE practice page.

Question 1Setting up a cloud solution environment

A security auditor holds the Viewer role on the organization node and must keep it for every project except one sensitive project, which the auditor must no longer be able to read. The organization grant is managed by a central team and must not be changed. What should you do?

Choose one.

  • a
    Remove the auditor's Viewer binding from the sensitive project's allow policy

    The Viewer binding is not on the project's allow policy; it is inherited from the organization node, so there is nothing on the project to remove and the inherited access continues.

  • b
    Set an organization policy constraint on the project that restricts the auditor

    Organization policy constraints restrict resource configurations such as locations or external IPs. They do not take permissions away from a specific principal.

  • c
    Attach an IAM deny policy to the project denying the auditor's read permissions Correct

    Deny policies can be attached to a project and are evaluated before allow policies, so denying the auditor's read permissions there blocks the inherited Viewer access on that project only.

  • d
    Add a deny binding for the auditor to the sensitive project's allow policy

    Allow policies only contain role bindings that grant access. Denials are expressed in a separate IAM deny policy, not as an entry in the allow policy.

The concept

IAM allow policies are additive: the effective allow policy on a project is the union of its own bindings and every inherited binding, so nothing in a child allow policy can subtract an ancestor's grant. IAM deny policies are a separate policy type that can be attached to an organization, folder or project; IAM checks deny policies before allow policies.

Why that’s the answer

With the organization grant off-limits, the only way to remove access on one project is a deny policy attached to that project that names the auditor and the read permissions to block (permission groups such as all get or list permissions of a service are supported). Removing a project binding fails because the grant is inherited, an allow policy has no deny entries, and organization policy constraints govern configurations rather than principals.

How to reason it out
  1. Locate the grant: it is inherited from the organization node, not set on the project.
  2. Recall that allow policies only add access, so a child allow policy cannot revoke it.
  3. Recall that deny policies are a separate policy type attachable at the project and checked first.
  4. Discard organization policy constraints, which do not target principals.

Exam tip: Allow policies only add; to carve an exception out of an inherited grant, attach an IAM deny policy lower down.

Setting Up Google Cloud Projects, Resource Hierarchy, and IAM — the lesson that teaches this.

Question 2Setting up a cloud solution environment

Your compliance team requires that no Compute Engine VM in the company can be given an external IP address, including VMs in projects created next year, and including VMs created by project Owners. You want a single control with the least ongoing effort. What should you do?

Choose one.

  • a
    Set the compute.vmExternalIpAccess constraint to deny all on each existing project

    This is the right constraint at the wrong scope. Projects created next year would not have it, so someone must remember to repeat it on every new project.

  • b
    Create a hierarchical firewall policy on the organization that denies ingress from 0.0.0.0/0

    Firewall rules filter traffic. A VM could still be created with an external IP address, which is what the requirement forbids.

  • c
    Set the compute.vmExternalIpAccess constraint to deny all on the organization node Correct

    The list constraint governs which VMs may have external IPs, applies regardless of the creator's IAM roles, and is inherited by every current and future project under the organization.

  • d
    Set the compute.restrictVpcPeering constraint to deny all on the organization node

    This is a real constraint at the right scope, but it controls VPC Network Peering, not whether VMs can have external IP addresses.

The concept

Organization policy constraints restrict what configurations are allowed, no matter which IAM roles the actor holds, and they are inherited down the hierarchy from where they are set. The compute.vmExternalIpAccess list constraint defines which VM instances (if any) may use external IP addresses.

Why that’s the answer

Setting compute.vmExternalIpAccess to deny all on the organization node meets every requirement at once: it blocks external IPs even for Owners, and new projects inherit it automatically. Applying it per project gives the right behaviour only until the next project appears; a hierarchical firewall policy blocks traffic but still lets the IP be assigned; compute.restrictVpcPeering is a real organization-level constraint that governs a different feature.

How to reason it out
  1. Recognise a configuration guardrail that must hold regardless of IAM roles: an organization policy.
  2. Pick the constraint that governs external IPs on VMs: compute.vmExternalIpAccess.
  3. Pick the scope that covers future projects: the organization node.
  4. Reject controls that act on traffic rather than on the configuration.

Exam tip: Guardrails for every project, now and later, go on the organization node as an organization policy constraint.

Setting Up Google Cloud Projects, Resource Hierarchy, and IAM — the lesson that teaches this.

Question 3Setting up a cloud solution environment

Three analysts join next week and need exactly the access of the existing analytics team, whose IAM roles are all granted to the group data-analysts@example.com on the analytics folder. Following Google-recommended practices, what should you do?

Choose one.

  • a
    Grant the three analysts the same roles as data-analysts@example.com on the folder

    Individual bindings duplicate the group grant and drift as the team's roles change, and every leaver needs IAM edits on top of a Cloud Identity change.

  • b
    Grant the three analysts the same roles as data-analysts@example.com on each project

    Per-user, per-project bindings duplicate the group grant at a lower level, multiply the IAM changes and miss any project added to the folder later.

  • c
    Add the three analysts as members of data-analysts@example.com in Cloud Identity Correct

    The roles are already bound to the group on the folder, so group membership gives the new analysts the full, current access with no IAM policy changes.

  • d
    Create a second group for the analysts and grant it the roles of data-analysts@example.com

    A parallel group with copied bindings creates two sources of truth that drift apart as the team's access changes over time.

The concept

When roles are bound to a group, a person's access is managed by group membership in Cloud Identity (or Google Workspace), not by IAM policy edits. Onboarding and offboarding become one membership change.

Why that’s the answer

Adding the analysts to the existing group is the only choice that gives them exactly the team's access today and keeps them in step with future changes. Every other choice copies the bindings somewhere else, to users or to a second group, which works on day one but drifts and multiplies IAM changes.

How to reason it out
  1. Notice that the team's roles are bound to a group, not to users.
  2. Ask what must change for a new member: membership, not IAM policy.
  3. Reject any choice that duplicates bindings, because duplicates drift.

Exam tip: If access is bound to a group, onboard people by changing group membership, never by copying bindings.

Setting Up Google Cloud Projects, Resource Hierarchy, and IAM — the lesson that teaches this.

Question 4Setting up a cloud solution environment

You created a project, linked it to billing and set it as your gcloud default. Your first gcloud compute instances create command fails with HTTP 403 and the error reason SERVICE_DISABLED for compute.googleapis.com. Which command resolves the error so that the create command can succeed?

Choose one.

  • a
    gcloud services list --enabled --filter=compute

    This lists enabled services matching compute. It confirms that Compute Engine is missing from the list but changes nothing, so the create command still fails.

  • b
    gcloud services enable compute.googleapis.com Correct

    SERVICE_DISABLED means the API is turned off in this project. Enabling compute.googleapis.com in the current project lets the create command reach a working Compute Engine API.

  • c
    gcloud services list --available --filter=compute

    This lists services that can be enabled, so it finds compute.googleapis.com, but it only reports; it does not enable the API.

  • d
    gcloud config set compute/region us-central1

    This sets a default region for compute commands. The request already reached Google, which rejected it because the API is disabled in the project, not because of a location.

The concept

Every Google Cloud service is exposed through an API that must be enabled in each project before use. A 403 with reason SERVICE_DISABLED means the API is off for that project; enabling it needs the serviceusage.services.enable permission.

Why that’s the answer

gcloud services enable compute.googleapis.com turns the Compute Engine API on for the current project, which is what SERVICE_DISABLED asks for. The two gcloud services list variants are the tempting near-twins: --enabled confirms the API is missing and --available finds it, but neither changes the project's state. Setting a default region fixes location problems, which this error is not.

How to reason it out
  1. Read the error reason: SERVICE_DISABLED is about the API's state in the project, not your credentials or location.
  2. Recall that API state is managed with gcloud services.
  3. Choose the subcommand that changes state (enable), not one that only reports it (list).

Exam tip: SERVICE_DISABLED means run gcloud services enable for that API in that project; gcloud services list only reports.

Setting Up Google Cloud Projects, Resource Hierarchy, and IAM — the lesson that teaches this.

Question 5Setting up a cloud solution environment

A deployment in us-central1 fails with a QUOTA_EXCEEDED error that names the CPUs quota for region us-central1. Next month's launch will need about three times the current vCPU count, and for data-residency reasons the workload must stay in us-central1. What should you do to prepare for the launch?

Choose one.

  • a
    Request a CPUs quota increase for us-central1 now, ahead of the launch Correct

    Allocation quotas such as CPUs are enforced per project and region and raised by a quota increase request that Google reviews, so requesting well ahead of the launch is the supported path.

  • b
    Raise the project's Cloud Billing budget for the expected launch spending

    Budgets only track spending and send alerts. They do not change how many vCPUs the project is allowed to run.

  • c
    Create a Compute Engine reservation for the extra vCPUs in us-central1

    Reservations hold capacity for VMs you are allowed to run, and they consume CPU quota themselves, so the reservation would fail on the same quota.

  • d
    Request a CPUS_ALL_REGIONS quota increase now, ahead of the launch

    CPUS_ALL_REGIONS is a separate project-wide cap across all regions. Raising it does not lift the regional CPUs quota in us-central1, which is the limit that failed.

The concept

Quotas cap how much of a resource a project can use. CPUs are an allocation quota enforced per project and per region. Raising one means submitting a quota increase request (Cloud Quotas page or gcloud), which Google reviews and may take time to approve.

Why that’s the answer

The launch needs more vCPUs in one specific region, and the error names that region's CPUs quota, so the fix is a CPUs quota increase for us-central1, requested ahead of the launch because approval is not instant. CPUS_ALL_REGIONS is the tempting near-twin, but it is a separate global cap; raising it leaves the regional limit in place. Raising a budget changes alerting, not limits, and a reservation consumes the same quota it would need.

How to reason it out
  1. Identify the limit in the error: the regional CPUs quota in us-central1.
  2. Recall that the regional CPUs quota and the global CPUS_ALL_REGIONS quota are separate limits.
  3. Quotas are raised only through a reviewed increase request, so request it early.
  4. Reject controls that do not change limits (budgets) or that depend on quota (reservations).

Exam tip: Budgets alert, reservations consume quota, and only a quota increase request raises the regional CPU limit.

Setting Up Google Cloud Projects, Resource Hierarchy, and IAM — the lesson that teaches this.

Question 6Setting up a cloud solution environment

A team lead must be able to create new projects under the engineering folder as services are spun up. The lead must not be able to change the folder's IAM policy or create projects elsewhere in the organization. Applying least privilege, which grant should you make?

Choose one.

  • a
    Folder Admin (roles/resourcemanager.folderAdmin) on the engineering folder

    Folder Admin manages the folder itself, including its IAM policy and subfolders, which the stem forbids, and it still does not include resourcemanager.projects.create, so it is both over-privileged and insufficient.

  • b
    Project Creator (roles/resourcemanager.projectCreator) on the organization node

    This is the right role at the wrong scope: on the organization node the lead could create projects anywhere in the company.

  • c
    Project Creator (roles/resourcemanager.projectCreator) on the engineering folder Correct

    Project Creator granted on the folder lets the lead create projects only inside that folder, without any rights over the folder's own policy.

  • d
    Folder Editor (roles/resourcemanager.folderEditor) on the engineering folder

    Folder Editor lets the lead modify, delete and restore folders but does not include the resourcemanager.projects.create permission needed to create projects.

The concept

Resource Manager roles are scoped by where they are granted. Project Creator (roles/resourcemanager.projectCreator) contains the permission to create projects, and when granted on a folder, the holder can create projects in that folder only.

Why that’s the answer

Project Creator on the engineering folder is the narrowest grant that lets the lead create projects there. Folder Admin adds control of the folder's IAM policy, which the stem forbids, and neither Folder Admin nor Folder Editor contains resourcemanager.projects.create; Project Creator on the organization grants the right ability at too broad a scope.

How to reason it out
  1. Find the one permission needed: creating projects.
  2. Pick the predefined role that contains it: Project Creator.
  3. Pick the narrowest scope that covers the need: the engineering folder.
  4. Reject roles that add folder management rights the stem rules out.

Exam tip: Least privilege is two choices: the narrowest role and the narrowest node in the hierarchy.

Setting Up Google Cloud Projects, Resource Hierarchy, and IAM — the lesson that teaches this.

What ACE domain 1 tests, topic by topic

The official exam guide breaks Setting up a cloud solution environment into 2 topics. The question bank follows the same split, so a weak topic shows up as a cluster of misses you can go back and read.

Published ACE practice questions per topic in Setting up a cloud solution environment
TopicWhat it coversQuestions
Setting up cloud projects and accountsOfficial ACE exam-guide sub-section. Creating a resource hierarchy; applying organizational policies; granting IAM roles within a project; managing users and groups in Cloud Identity (manual and automated); enabling APIs; provisioning Google Cloud Observability; assessing quotas and requesting increases; setting up standalone organizations; setting up cloud networking; verifying product availability across regions and zones; configuring Cloud Asset Inventory and using Gemini Cloud Assist to analyze resources; configuring Workforce Identity Federation.44
Managing billing configurationOfficial ACE exam-guide sub-section. Creating one or more billing accounts; linking projects to a billing account; establishing billing budgets and alerts; setting up billing exports.48
Total92

Revise Setting up a cloud solution environment before you drill it

Other ACE domains

Setting up a cloud solution environment: your questions

Setting up a cloud solution environment is domain 1 of the ACE exam guide and carries 20% of the scored content — the 3rd-heaviest of the 4 domains. On a 55-question paper that works out to roughly 11 questions, though Google Cloud does not publish an exact per-domain count and individual exam forms vary.

Source

The domain weight and topic list on this page come from the official ACE exam guide.