Google Associate Cloud Engineer Practice Test 3
Question 20
A deployment uses the standard project-level Service Usage workflow. The Pub/Sub API is enabled in sandbox, but the production project has neither its own enablement nor an inherited hierarchical service activation policy. What is needed before using Pub/Sub in production?
- Assume the API is enabled in production because sandbox and production share a billing account.
- Enable the required API for the production project using an authorized Service Usage operation, or establish an approved inherited policy.
- Grant production project Editor to the deployer because IAM automatically enables every Google service.
- Configure a new production VPC subnet because API enablement is controlled by subnet routing.
Explanation
Correct Answer
B:Enable the required API for the production project using an authorized Service Usage operation, or establish an approved inherited policy. Normal Service Usage operations enable services for the selected project. Google also documents a Preview hierarchical activation model; this stem explicitly states that production has no inherited enablement, so it must be enabled through an authorized supported path.
Incorrect Answers
A:Assume the API is enabled in production because sandbox and production share a billing account. A common billing account does not convey a service enablement state to unrelated projects. The production effective service policy must permit the API.
C:Grant production project Editor to the deployer because IAM automatically enables every Google service. A role grant controls authorization; it does not by itself activate Pub/Sub. Enabling services requires the appropriate Service Usage permissions and policy state.
D:Configure a new production VPC subnet because API enablement is controlled by subnet routing. VPC configuration affects packet routing, not whether the Pub/Sub API is enabled for the consuming project. Creating a subnet cannot resolve service-disabled responses.
Question 21
A project operator can administer Compute Engine VMs but a deployment fails specifically because the Cloud Run API is disabled in the project. What is the missing prerequisite?
- Add another instanceAdmin role to the operator, without inspecting service enablement.
- Change an existing Compute Engine firewall rule so Cloud Run can receive API requests.
- Verify Cloud Run API enablement in the project's effective Service Usage policy and have an authorized principal enable it if absent.
- Grant billing report access to the operator; that role automatically enables all project APIs.
Explanation
Correct Answer
C:Verify Cloud Run API enablement in the project's effective Service Usage policy and have an authorized principal enable it if absent. The error identifies the service enablement prerequisite. Effective enablement may be project-level or inherited under the supported hierarchical Preview, so inspect the effective state before enabling it.
Incorrect Answers
A:Add another instanceAdmin role to the operator, without inspecting service enablement. Instance administration and API enablement are distinct permissions. Another VM role cannot cause a disabled Cloud Run API to become enabled.
B:Change an existing Compute Engine firewall rule so Cloud Run can receive API requests. Firewall rules control network traffic for workloads. They do not determine whether a project is an enabled consumer of the Cloud Run API.
D:Grant billing report access to the operator; that role automatically enables all project APIs. Billing report permissions govern financial visibility. They do not grant Service Usage enablement or alter Cloud Run service activation.
Question 22
A project has an active Cloud Billing account but calls to the Cloud Run API return a disabled-service error. Which assumption is incorrect?
- Linking a project to an active billing account automatically enables every Google Cloud API required by the workload.
- The operator should check whether Cloud Run is enabled locally or by an applicable inherited service policy.
- Enabling a currently disabled service requires a principal with appropriate Service Usage authorization.
- A project may be billed successfully yet have a particular product API disabled.
Explanation
Correct Answer
A:Linking a project to an active billing account automatically enables every Google Cloud API required by the workload. Billing permits charges to be paid, but service activation is governed separately by Service Usage. A project can have active billing and still lack Cloud Run enablement.
Incorrect Answers
B:The operator should check whether Cloud Run is enabled locally or by an applicable inherited service policy. This is a correct diagnostic step, not the false assumption: effective service enablement can come from the project or from a hierarchical activation policy where supported.
C:Enabling a currently disabled service requires a principal with appropriate Service Usage authorization. Service Usage permissions determine who may enable an API. This is a genuine prerequisite, not an incorrect assumption about the failure.
D:A project may be billed successfully yet have a particular product API disabled. A valid billing link does not imply all APIs are enabled. This statement accurately separates the two controls.
Question 23
A sandbox project is moved to a new billing account while a weekly forecast still uses the old account's export. What must finance do to avoid a false conclusion?
- Use only the previous account’s export because the project’s ID has not changed.
- Review exports from the paying accounts for the appropriate periods and account for the billing-link change date.
- Count charges in both account exports as duplicates without reviewing usage timestamps.
- Move the project back to its original folder so all historic charges switch accounts.
Explanation
Correct Answer
B:Exports are organized by the account that paid for consumption. For a project transfer, compare the relevant account datasets and effective billing dates before combining costs in a forecast; otherwise usage may be omitted or wrongly attributed.
Incorrect Answers
A:A stable project ID does not mean every billing period is attributed to the original account.
C:A change in paying account does not automatically mean all rows in both exports are duplicates.
D:Folder placement controls resource ancestry, not historic billing ledger ownership.
Question 24
An operations team can create VMs but cannot manage its project's billing link. Which distinction explains the behavior?
- Assume Compute Instance Admin grants every Cloud Billing account management permission.
- Check billing-account and project billing association permissions separately from VM operation rights.
- Raise the project CPU quota because quota controls authorization to switch billing accounts.
- Create a new service account and grant it only Logging Viewer.
Explanation
Correct Answer
B:Compute Engine operations and billing linkage use different permission sets. Verify the required project-level billing assignment permission and billing-account access before allowing an approved user to change the project’s paying account.
Incorrect Answers
A:Resource administration roles do not automatically include the financial permissions for changing payment associations.
C:CPU quota limits resource allocation, not account-link authorization.
D:Logging Viewer allows reading logs and does not grant the requested billing management action.
Question 25
A researcher has Viewer on project alpha but is denied access to private objects in a bucket in project beta. Which authorization should be evaluated for the attempted read?
- Check only the roles attached to the researcher on project alpha; they authorize the same operation in all sibling projects.
- Grant the organization Viewer role so the researcher can list every bucket object in all projects without a bucket-level policy review.
- Change project beta's billing account because billing association, not IAM, controls object-read permission.
- Evaluate the researcher's effective storage-object permissions on the beta bucket, including valid bindings inherited from beta's ancestors.
Explanation
Correct Answer
D:Evaluate the researcher's effective storage-object permissions on the beta bucket, including valid bindings inherited from beta's ancestors. Cloud Storage checks permissions at the resource with relevant inherited IAM grants. Whether the principal can read private beta objects depends on effective permissions applicable to that bucket, not project alpha membership.
Incorrect Answers
A:Check only the roles attached to the researcher on project alpha; they authorize the same operation in all sibling projects. A grant on alpha does not automatically cover beta. A sibling project has its own effective IAM policy and may not authorize this principal.
B:Grant the organization Viewer role so the researcher can list every bucket object in all projects without a bucket-level policy review. A broad Viewer grant violates least privilege and may not include the specific Cloud Storage object-data read permission required. Object access must be checked against effective roles on beta.
C:Change project beta's billing account because billing association, not IAM, controls object-read permission. Billing account linkage determines payment responsibility, not whether this principal has storage.objects.get or related access for the target bucket.
Question 26
A team wants all new projects in a regulated folder to inherit baseline read-only audit access while sibling folders stay unaffected. Where should the role be attached?
- Grant the audit role separately on each existing project and require manual repetition for new projects.
- Grant the audit role at the organization root for every folder.
- Bind the audited principals to the role at the regulated folder.
- Grant the audit role on the folder's oldest project and rely on new projects inheriting from that sibling.
Explanation
Correct Answer
C:A binding at the regulated folder is inherited by projects within that folder, including future descendants. It leaves unrelated sibling folders outside this specific audit grant while preserving one managed policy location.
Incorrect Answers
A:Manual project grants would not automatically cover newly created projects; they add avoidable administration.
B:An organization-level binding would affect sibling folders that are explicitly outside the requirement.
D:Project role bindings do not propagate sideways into newer sibling projects; only an appropriate ancestor binding would cover both.
Question 27
After creating a custom IAM role, an operator expects it to grant access automatically to every service account. What is missing?
- Enable every API in the project so the role is assigned to all service accounts.
- Assign the custom role to the organization owner; Google Cloud will spread it automatically.
- Add an IAM binding granting the custom role to the specific service account at the required scope.
- Rename the role to a predefined role without creating any bindings.
Explanation
Correct Answer
C:A custom role defines a collection of permissions. It takes effect for an identity only when an allow-policy binding connects the role to that principal on the appropriate project, folder, or other supported resource.
Incorrect Answers
A:Service enablement determines available APIs, not which principals receive a custom IAM role.
B:Granting a role to an owner is not the same as assigning that role to the target service account.
D:The name of a role does not grant access. An explicit role binding remains necessary.
Question 28
A service administrator discovers that a user with no explicit local bucket binding can still administer a bucket. Which source may explain the privilege?
- Check only the bucket's explicit allow-policy bindings and exclude roles from its parent project.
- Cloud Storage automatically makes all buckets writable to project viewers.
- Check whether a storage ACL is in use, but ignore the project's effective IAM roles.
- A project or ancestor IAM binding, possibly through a group, may authorize the bucket action.
Explanation
Correct Answer
D:Bucket permissions can come from roles attached higher in the hierarchy or to a group containing the user. Inspect the effective policy and the relevant project, folder, and organization bindings rather than relying only on the local bucket policy.
Incorrect Answers
A:Effective authorization can include inherited roles, so checking the local policy alone can miss the source of access.
B:Project Viewer is not blanket object-administration access; the required effective role must authorize the action.
C:Bucket ACLs may be relevant in eligible configurations, but inherited IAM permissions still need review to explain administration.
Question 29
A project is owned by the right engineering team but anyone in a broad corporate group can read its objects. What should be reviewed?
- Remove the approved engineering group from the project while leaving the broad corporate group binding active.
- Identify and narrow the binding that grants the broad group access to those storage objects.
- Move the objects into another folder within the same bucket without reviewing IAM.
- Add a second Viewer grant for the correct engineering team, leaving the broad one intact.
Explanation
Correct Answer
B:A Google Group can receive an IAM role at a bucket, project, or inherited ancestor scope. Locate the binding that permits object access, then restrict its principal or scope to the approved audience. Also confirm the group membership before changing production permissions.
Incorrect Answers
A:Revoking the narrow group's grant does not eliminate the existing broad role that exposes the objects.
C:An object prefix does not automatically cancel a project- or bucket-level role binding.
D:Another valid grant does not neutralize the existing overly broad group binding.
Question 30
An incident responder needs to read one Cloud Storage bucket for exactly one hour. They currently have indefinite project Editor. Security requires least privilege and an enforced expiration. Which remediation is most appropriate?
- Leave Editor in place and ask the responder to sign out when the incident closes.
- Remove the Editor grant and use a supported bucket-scoped read role with a one-hour conditional expiry.
- Keep Editor indefinitely but schedule an access review for the following month.
- Replace project Editor with an unconditional organization-level Viewer role so the grant has a simpler name.
Explanation
Correct Answer
B:Remove the Editor grant and use a supported bucket-scoped read role with a one-hour conditional expiry. The task needs only bucket reading for a bounded window. A supported narrow role binding with request-time expiry enforces the cutoff, and removing Editor eliminates the standing broader privilege.
Incorrect Answers
A:Leave Editor in place and ask the responder to sign out when the incident closes. Signing out does not revoke an IAM role, and Editor is broader than the bucket-read requirement. The indefinite authorization remains effective.
C:Keep Editor indefinitely but schedule an access review for the following month. An access review is not a time-enforced stop. The principal retains Editor during the rest of the month, contrary to the one-hour requirement.
D:Replace project Editor with an unconditional organization-level Viewer role so the grant has a simpler name. An organization-level role affects more resources than required and does not expire automatically. Moving the access to a wider scope cannot satisfy least privilege.