Google Associate Cloud Engineer Practice Test 61

Question 600

An internal role is being retired and must no longer be assigned for future work. Which method addresses the task?

  1. Create a custom role at organization scope
  2. Add an IAM allow-policy binding for the team group on the target project
  3. Disable or delete the custom role through the supported lifecycle workflow
  4. Update the role definition after reviewing the permission's support level
  5. Create a project-level custom IAM role

Explanation

Correct Answer

C:

Custom role lifecycle changes can restrict future use and may affect existing bindings. Role deprecation should include a migration plan for dependent principals.

Incorrect Answers

A:

This setting would define a reusable organization custom role. That behavior does not establish the requested ability to stop using an obsolete permission bundle; it addresses an adjacent concern instead.

B:

Using this action would bind a role to a principal on a resource, not stop using an obsolete permission bundle. Its function is different from the specific change described in the scenario.

D:

This choice is useful to extend a custom role's permission list. The stated task is to stop using an obsolete permission bundle, which requires a different mechanism or permission scope.

E:

The tool can own a custom role within one project, but it cannot be substituted for the capability needed to stop using an obsolete permission bundle. Its operational effect is not equivalent.

Question 601

Several employees need identical service-level read rights and membership changes happen weekly. Which implementation matches this requirement?

  1. Bind a role to a Cloud Identity group rather than to each employee
  2. Audit all relevant direct and group-based bindings and group membership
  3. Map the external group attribute and bind the filtered workforce principal set
  4. Grant a scoped IAM role to the correct workforce pool principal or principal set

Explanation

Correct Answer

A:

Group-based IAM reduces repeated policy edits when staffing changes. The group principal holds the role and membership controls who benefits.

Incorrect Answers

B:

Its purpose is to find indirect IAM access via groups. That distinction matters: the scenario calls for an action to simplify team authorization management, not this separate configuration task.

C:

Administrators use it to scope IAM grants by federated group attribute, rather than to simplify team authorization management. Applying it would change the wrong component of this deployment.

D:

While this can authorize federated human access, the present task requires an action to simplify team authorization management. This operation does not supply the behavior described in the requirements.

Question 602

A contractor was removed from one IAM binding but remains authorized through another group. What should the administrator do?

  1. Bind a role to a Cloud Identity group rather than to each employee
  2. Audit all relevant direct and group-based bindings and group membership
  3. Grant a scoped IAM role to the correct workforce pool principal or principal set
  4. Map the external group attribute and bind the filtered workforce principal set
  5. Use a Google group as the IAM binding member

Explanation

Correct Answer

B:

A principal can have multiple paths to the same permission. Effective access remains if any applicable allow path survives other restrictions.

Incorrect Answers

A:

It can delegate access through a Google group; however, it does not provide the specific operation to revoke all relevant contractor authorization paths. The two controls serve different purposes.

C:

The tool can authorize federated human access, but it cannot be substituted for the capability needed to revoke all relevant contractor authorization paths. Its operational effect is not equivalent.

D:

Select this when the goal is to scope IAM grants by federated group attribute. Here the decisive requirement is to revoke all relevant contractor authorization paths, and that outcome is not achieved by this action.

E:

An operator would use this action to grant IAM permissions to a group, chiefly when trying to authorize a rotating team; The current requirement is to revoke all relevant contractor authorization paths, which remains unresolved by that operation.

Question 603

A federated workforce member authenticates successfully but has no resource role. Which choice provides the required behavior?

  1. Grant appropriate Project IAM Admin permissions on that project
  2. Grant a scoped IAM role to the correct workforce pool principal or principal set
  3. Audit all relevant direct and group-based bindings and group membership
  4. Bind a role to a Cloud Identity group rather than to each employee
  5. Map the external group attribute and bind the filtered workforce principal set

Explanation

Correct Answer

B:

Workforce federation establishes identity, while IAM bindings grant resource privileges. The federation configuration does not automatically grant project-wide roles.

Incorrect Answers

A:

For the stated need to give a workforce identity resource permissions, this would instead delegate project IAM management; it supports the separate task to authorize project access-policy updates, not the required configuration.

C:

This setting would find indirect IAM access via groups. That behavior does not establish the requested ability to give a workforce identity resource permissions; it addresses an adjacent concern instead.

D:

Its purpose is to delegate access through a Google group. That distinction matters: the scenario calls for an action to give a workforce identity resource permissions, not this separate configuration task.

E:

This approach can scope IAM grants by federated group attribute. The requirement is to give a workforce identity resource permissions, so it controls a different part of the workflow and leaves that result unaddressed.

Question 604

A business must limit federated contractor access to a particular group claim. Which approach should be selected?

  1. Grant a scoped IAM role to the correct workforce pool principal or principal set
  2. Map the external group attribute and bind the filtered workforce principal set
  3. Bind a role to a Cloud Identity group rather than to each employee
  4. Audit all relevant direct and group-based bindings and group membership
  5. Evaluate a Principal Access Boundary policy for the appropriate principal set

Explanation

Correct Answer

B:

Attribute mapping allows policy to refer to particular groups of external identities. A pool-wide binding would authorize a broader population.

Incorrect Answers

A:

This mechanism is intended to authorize federated human access. It does not implement the required action to restrict contractor principal sets, even though both are relevant to the same general service.

C:

Select this when the goal is to delegate access through a Google group. Here the decisive requirement is to restrict contractor principal sets, and that outcome is not achieved by this action.

D:

Administrators use it to find indirect IAM access via groups, rather than to restrict contractor principal sets. Applying it would change the wrong component of this deployment.

E:

In a workflow for principal access boundary concepts, it can limit a principal's eligible resource universe; This question instead asks how to restrict contractor principal sets; substituting the former action would leave that distinct technical requirement unmet.

Question 605

An employee may view IAM policies but must not add or remove role bindings. What is the most direct solution?

  1. Use a properly authorized organization-level IAM administrator
  2. Grant an IAM read-only capability appropriate to the resource scope
  3. Grant appropriate Project IAM Admin permissions on that project
  4. Grant Service Account User on the target service account for attachment

Explanation

Correct Answer

B:

Viewing policies and changing policies are different IAM permissions. Broad administrative roles are unnecessary for inspection.

Incorrect Answers

A:

This choice is useful to manage IAM at organization scope. The stated task is to separate access review from policy editing, which requires a different mechanism or permission scope.

C:

This setting would delegate project IAM management. That behavior does not establish the requested ability to separate access review from policy editing; it addresses an adjacent concern instead.

D:

Using this action would permit attaching a service account to resources, not separate access review from policy editing. Its function is different from the specific change described in the scenario.

Question 606

A project administrator must edit IAM bindings for one project without owning the organization. Which implementation matches this requirement?

  1. Grant appropriate Project IAM Admin permissions on that project
  2. Export or query supported IAM policy asset data at hierarchy scope
  3. Grant an IAM read-only capability appropriate to the resource scope
  4. Use a properly authorized organization-level IAM administrator
  5. Grant Service Account User on the target service account for attachment

Explanation

Correct Answer

A:

Project IAM Admin grants authority for the project's allow-policy management. It is narrower in hierarchy scope than organization-level IAM administration.

Incorrect Answers

B:

For the stated need to authorize project access-policy updates, this would instead generate hierarchy-wide role assignment reports; it supports the separate task to audit project roles centrally, not the required configuration.

C:

While this can permit IAM policy inspection only, the present task requires an action to authorize project access-policy updates. This operation does not supply the behavior described in the requirements.

D:

Administrators use it to manage IAM at organization scope, rather than to authorize project access-policy updates. Applying it would change the wrong component of this deployment.

E:

The result of this choice would be to permit attaching a service account to resources. The requested outcome, to authorize project access-policy updates, is handled at a different layer or through another operation.

Question 607

An IAM engineer wants to change organization-wide security allow policies. What should the administrator do?

  1. Grant appropriate Project IAM Admin permissions on that project
  2. Create a project-level custom IAM role
  3. Use a properly authorized organization-level IAM administrator
  4. Grant Service Account User on the target service account for attachment
  5. Grant an IAM read-only capability appropriate to the resource scope

Explanation

Correct Answer

C:

Organization IAM policy changes affect many descendant resources. Permission to edit a single project policy does not provide organization-wide governance access.

Incorrect Answers

A:

The tool can delegate project IAM management, but it cannot be substituted for the capability needed to update company-wide access controls. Its operational effect is not equivalent.

B:

In a workflow for custom role lifecycle, it can own a custom role within one project; This question instead asks how to update company-wide access controls; substituting the former action would leave that distinct technical requirement unmet.

D:

It can permit attaching a service account to resources; however, it does not provide the specific operation to update company-wide access controls. The two controls serve different purposes.

E:

This choice is useful to permit IAM policy inspection only. The stated task is to update company-wide access controls, which requires a different mechanism or permission scope.

Question 608

A deployment identity should be allowed to use an existing service account on a VM without gaining full ability to mint its access tokens. Which choice provides the required behavior?

  1. Grant an IAM read-only capability appropriate to the resource scope
  2. Grant appropriate Project IAM Admin permissions on that project
  3. Use a properly authorized organization-level IAM administrator
  4. Grant Service Account User on the target service account for attachment
  5. Grant an appropriate Compute Security Admin role where warranted

Explanation

Correct Answer

D:

The Service Account User role authorizes supported attach or run-as operations. Token creation and impersonation require distinct permissions.

Incorrect Answers

A:

While this can permit IAM policy inspection only, the present task requires an action to allow run-as without generic token minting. This operation does not supply the behavior described in the requirements.

B:

This setting would delegate project IAM management. That behavior does not establish the requested ability to allow run-as without generic token minting; it addresses an adjacent concern instead.

C:

Its purpose is to manage IAM at organization scope. That distinction matters: the scenario calls for an action to allow run-as without generic token minting, not this separate configuration task.

E:

The choice is aimed at a different purpose: to allow firewall administration without Owner; Even if it can delegate network security rule management, that would not accomplish the stated requirement to allow run-as without generic token minting.

Question 609

A support tool only needs to read records in one BigQuery dataset. How should the team proceed?

  1. Grant appropriate BigQuery data read permission at dataset scope
  2. Add an IAM allow-policy binding for the team group on the target project
  3. Grant the Cloud Run Invoker role on the target service to the client principal
  4. Grant Pub/Sub Publisher at the target topic
  5. Grant Storage Object Creator on the bucket

Explanation

Correct Answer

A:

Dataset-level data access can restrict which tables are readable. Query job creation is a separate permission when the tool executes queries.

Incorrect Answers

B:

Select this when the goal is to bind a role to a principal on a resource. Here the decisive requirement is to limit warehouse data visibility, and that outcome is not achieved by this action.

C:

The result of this choice would be to authorize runtime invocation of a private Cloud Run endpoint. The requested outcome, to limit warehouse data visibility, is handled at a different layer or through another operation.

D:

This mechanism is intended to permit publishing to a single Pub/Sub topic. It does not implement the required action to limit warehouse data visibility, even though both are relevant to the same general service.

E:

The tool can grant write-new-object access, but it cannot be substituted for the capability needed to limit warehouse data visibility. Its operational effect is not equivalent.

Question 610

An automated monitoring client needs to invoke one private Cloud Run endpoint, but must never deploy or update its service. What is the most direct solution?

  1. Grant Storage Object Creator on the bucket
  2. Grant appropriate BigQuery data read permission at dataset scope
  3. Grant Pub/Sub Publisher at the target topic
  4. Grant the Cloud Run Invoker role on the target service to the client principal

Explanation

Correct Answer

D:

Cloud Run Invoker authorizes service invocation without granting permissions to deploy revisions or change service configuration. The client still needs a valid authentication token for the protected endpoint.

Incorrect Answers

A:

Using this action would grant write-new-object access, not allow calling a service without deployment privileges. Its function is different from the specific change described in the scenario.

B:

This setting would grant access to one analytical dataset. That behavior does not establish the requested ability to allow calling a service without deployment privileges; it addresses an adjacent concern instead.

C:

This approach can permit publishing to a single Pub/Sub topic. The requirement is to allow calling a service without deployment privileges, so it controls a different part of the workflow and leaves that result unaddressed.

Associate Cloud Engineer Practice Tests