Question 20

A platform group has joined employees who should receive the same project privileges as existing engineers. What is the best next step?

  1. Assign a service-specific predefined IAM role with the required permissions
  2. Grant a suitable predefined viewer role on that project
  3. Create separate managed groups in Cloud Identity for each team
  4. Examine the project's IAM allow policy, including inherited grants
  5. Grant the relevant IAM role to a Google group and manage group membership

Explanation

Correct Answer

E:

Group principals centralize access for a team. Adding or removing users from the group changes membership-driven access without rewriting each resource policy.

Incorrect Answers

A:

This setting would grant service-specific permissions with least privilege. That behavior does not establish the requested ability to onboard multiple engineers with a managed group principal; it addresses an adjacent concern instead.

B:

Its purpose is to grant read access within a selected project. That distinction matters: the scenario calls for an action to onboard multiple engineers with a managed group principal, not this separate configuration task.

C:

An operator would use this action to organize users into reusable group principals, chiefly when trying to maintain team membership independently of project IAM; The current requirement is to onboard multiple engineers with a managed group principal, which remains unresolved by that operation.

D:

While this can inspect project access bindings and inherited access, the present task requires an action to onboard multiple engineers with a managed group principal. This operation does not supply the behavior described in the requirements.

Question 21

An IT administrator must add a new employee's managed identity to the organization. What should the administrator do?

  1. Create separate managed groups in Cloud Identity for each team
  2. Inspect the group membership using Cloud Identity administration or API
  3. Remove the employee from the relevant Cloud Identity or Google group
  4. Provision the employee in Cloud Identity or the connected identity-management workflow

Explanation

Correct Answer

D:

Cloud Identity manages organization users and groups. Cloud resources can then authorize the resulting principal through IAM bindings.

Incorrect Answers

A:

Select this when the goal is to organize users into reusable group principals. Here the decisive requirement is to create a managed employee account, and that outcome is not achieved by this action.

B:

The tool can inspect users belonging to a group, but it cannot be substituted for the capability needed to create a managed employee account. Its operational effect is not equivalent.

C:

This mechanism is intended to update group membership for permission removal. It does not implement the required action to create a managed employee account, even though both are relevant to the same general service.

Question 22

A project access group is used for IAM grants and an employee must stop inheriting its permissions. Which choice provides the required behavior?

  1. Remove the employee from the relevant Cloud Identity or Google group
  2. Provision the employee in Cloud Identity or the connected identity-management workflow
  3. Suspend or deactivate the employee's workforce identity in the identity management system
  4. Create separate managed groups in Cloud Identity for each team
  5. Inspect the group membership using Cloud Identity administration or API

Explanation

Correct Answer

A:

Group-based access is governed by membership. Removing the person from the group stops future authorization through that group after changes propagate.

Incorrect Answers

B:

This approach can manage enterprise user identities. The requirement is to revoke permissions obtained through group membership, so it controls a different part of the workflow and leaves that result unaddressed.

C:

This proposal can disable a departing person's managed sign-in, but the failure or goal described here calls for a way to revoke permissions obtained through group membership; It changes the wrong control or scope for the requested outcome.

D:

Using this action would organize users into reusable group principals, not revoke permissions obtained through group membership. Its function is different from the specific change described in the scenario.

E:

This setting would inspect users belonging to a group. That behavior does not establish the requested ability to revoke permissions obtained through group membership; it addresses an adjacent concern instead.

Question 23

Several engineering teams need reusable membership management without creating IAM bindings for every user. Which approach should be selected?

  1. Inspect the group membership using Cloud Identity administration or API
  2. Use an appropriate Cloud Identity or Google Workspace directory synchronization approach
  3. Provision the employee in Cloud Identity or the connected identity-management workflow
  4. Create separate managed groups in Cloud Identity for each team
  5. Remove the employee from the relevant Cloud Identity or Google group

Explanation

Correct Answer

D:

Managed groups provide stable group principals for IAM policies. They keep team membership administration distinct from resource-level permission bindings.

Incorrect Answers

A:

Administrators use it to inspect users belonging to a group, rather than to maintain team membership independently of project IAM. Applying it would change the wrong component of this deployment.

B:

An operator would use this action to synchronize managed users and groups from a directory, chiefly when trying to automate employee identity lifecycle from a source directory; The current requirement is to maintain team membership independently of project IAM, which remains unresolved by that operation.

C:

The result of this choice would be to manage enterprise user identities. The requested outcome, to maintain team membership independently of project IAM, is handled at a different layer or through another operation.

E:

While this can update group membership for permission removal, the present task requires an action to maintain team membership independently of project IAM. This operation does not supply the behavior described in the requirements.

Question 24

A cloud administrator needs to find who is in the group that was granted project access. Which method addresses the task?

  1. Remove the employee from the relevant Cloud Identity or Google group
  2. Create separate managed groups in Cloud Identity for each team
  3. Inspect the group membership using Cloud Identity administration or API
  4. Create a folder under the organization and place the division's projects inside it
  5. Provision the employee in Cloud Identity or the connected identity-management workflow

Explanation

Correct Answer

C:

Group directories maintain members and nested membership where applicable. A project's IAM policy lists the group principal, not necessarily every individual member.

Incorrect Answers

A:

This setting would update group membership for permission removal. That behavior does not establish the requested ability to resolve group membership behind an IAM grant; it addresses an adjacent concern instead.

B:

The tool can organize users into reusable group principals, but it cannot be substituted for the capability needed to resolve group membership behind an IAM grant. Its operational effect is not equivalent.

D:

This choice is useful to group child projects under a common policy boundary. The stated task is to resolve group membership behind an IAM grant, which requires a different mechanism or permission scope.

E:

It can manage enterprise user identities; however, it does not provide the specific operation to resolve group membership behind an IAM grant. The two controls serve different purposes.

Question 25

Human identities must continue to be provisioned from an existing enterprise directory. Which implementation matches this requirement?

  1. Configure organizational SSO with the corporate identity provider
  2. Use an appropriate Cloud Identity or Google Workspace directory synchronization approach
  3. Suspend or deactivate the employee's workforce identity in the identity management system
  4. Configure Workforce Identity Federation for the supported identity provider

Explanation

Correct Answer

B:

Directory synchronization integrates enterprise identity lifecycle with managed Google identities. It reduces the need to create and disable accounts manually in several places.

Incorrect Answers

A:

This approach can integrate enterprise authentication for workforce users. The requirement is to automate employee identity lifecycle from a source directory, so it controls a different part of the workflow and leaves that result unaddressed.

C:

Administrators use it to disable a departing person's managed sign-in, rather than to automate employee identity lifecycle from a source directory. Applying it would change the wrong component of this deployment.

D:

Its purpose is to federate external human identities to cloud authorization. That distinction matters: the scenario calls for an action to automate employee identity lifecycle from a source directory, not this separate configuration task.

Question 26

A business needs workforce users to authenticate with its external identity provider without long-lived Google user credentials. What should the administrator do?

  1. Use an appropriate Cloud Identity or Google Workspace directory synchronization approach
  2. Configure organizational SSO with the corporate identity provider
  3. Create separate managed groups in Cloud Identity for each team
  4. Configure Workforce Identity Federation for the supported identity provider
  5. Suspend or deactivate the employee's workforce identity in the identity management system

Explanation

Correct Answer

D:

Workforce federation connects external human identities to Google Cloud access through configured pools and providers. Authorization still requires suitable IAM grants to those federated principals.

Incorrect Answers

A:

Select this when the goal is to synchronize managed users and groups from a directory. Here the decisive requirement is to allow workforce sign-in through an external identity provider, and that outcome is not achieved by this action.

B:

This mechanism is intended to integrate enterprise authentication for workforce users. It does not implement the required action to allow workforce sign-in through an external identity provider, even though both are relevant to the same general service.

C:

An operator would use this action to organize users into reusable group principals, chiefly when trying to maintain team membership independently of project IAM; The current requirement is to allow workforce sign-in through an external identity provider, which remains unresolved by that operation.

E:

The tool can disable a departing person's managed sign-in, but it cannot be substituted for the capability needed to allow workforce sign-in through an external identity provider. Its operational effect is not equivalent.

Question 27

A company plans a single sign-on flow for its managed workforce accounts. Which choice provides the required behavior?

  1. Suspend or deactivate the employee's workforce identity in the identity management system
  2. Use an appropriate Cloud Identity or Google Workspace directory synchronization approach
  3. Use a workload identity federation pool intended for nonhuman CI jobs as the workforce SSO configuration
  4. Configure organizational SSO with the corporate identity provider
  5. Configure Workforce Identity Federation for the supported identity provider

Explanation

Correct Answer

D:

SSO redirects user authentication to the enterprise identity system while preserving managed account and access administration. It is distinct from granting permissions to service-account workloads.

Incorrect Answers

A:

This approach can disable a departing person's managed sign-in. The requirement is to establish company-managed single sign-on, so it controls a different part of the workflow and leaves that result unaddressed.

B:

Its purpose is to synchronize managed users and groups from a directory. That distinction matters: the scenario calls for an action to establish company-managed single sign-on, not this separate configuration task.

C:

Workload Identity Federation exchanges credentials for external applications; it is not a replacement for the chosen organizational workforce SSO integration for employee interactive sign-in.

E:

Using this action would federate external human identities to cloud authorization, not establish company-managed single sign-on. Its function is different from the specific change described in the scenario.

Question 28

Security operations must disable a departed employee's interactive cloud access at the identity source. Which approach should be selected?

  1. Configure Workforce Identity Federation for the supported identity provider
  2. Suspend or deactivate the employee's workforce identity in the identity management system
  3. Use an appropriate Cloud Identity or Google Workspace directory synchronization approach
  4. Configure organizational SSO with the corporate identity provider
  5. Remove the employee from the relevant Cloud Identity or Google group

Explanation

Correct Answer

B:

Identity lifecycle controls prevent the former employee from continuing to sign in. Merely changing a billing role does not revoke all possible authentication paths.

Incorrect Answers

A:

The result of this choice would be to federate external human identities to cloud authorization. The requested outcome, to terminate access at the identity lifecycle layer, is handled at a different layer or through another operation.

C:

Select this when the goal is to synchronize managed users and groups from a directory. Here the decisive requirement is to terminate access at the identity lifecycle layer, and that outcome is not achieved by this action.

D:

Administrators use it to integrate enterprise authentication for workforce users, rather than to terminate access at the identity lifecycle layer. Applying it would change the wrong component of this deployment.

E:

In a workflow for cloud identity user and group management, it can update group membership for permission removal; This question instead asks how to terminate access at the identity lifecycle layer; substituting the former action would leave that distinct technical requirement unmet.

Question 29

A deployment pipeline reports PERMISSION_DENIED after a developer successfully enables a Google Cloud API. Which TWO checks can establish whether the failure is now an authorization problem rather than an API activation problem? (Choose TWO.)

  1. Verify the effective IAM permissions of the calling principal for the target resource
  2. Verify the API is enabled in the project that owns the request's consumer context
  3. Create a second billing account and leave resource IAM unchanged
  4. Increase the service's API quota without inspecting the response status

Explanation

Correct Answers

A:

An enabled API does not grant data or management access. The principal still needs the permission required by the particular operation on its resource.

B:

Service Usage enablement is scoped to a project. The API must be enabled where the request is charged or evaluated, rather than assumed enabled because another project works.

Incorrect Answers

C:

Billing account configuration may affect service use but does not itself grant the caller a missing IAM permission. It would not resolve a confirmed authorization denial.

D:

A quota change addresses an exhausted service quota, not an IAM PERMISSION_DENIED response. The reported failure calls for checking authorization and the exact request context first.

Question 30

An administrator must confirm which Google Cloud services are currently enabled in a project. Which implementation matches this requirement?

  1. Check API enablement and IAM independently in the failing project
  2. Enable that Google Cloud API in the target project
  3. List the project's enabled services through Service Usage or gcloud services list
  4. Obtain the appropriate Service Usage administrative permission before enabling the service

Explanation

Correct Answer

C:

The enabled-service inventory shows which APIs are available for project use. It is separate from listing resources already created with those APIs.

Incorrect Answers

A:

While this can compare service configuration per project, the present task requires an action to enumerate the APIs enabled for a project. This operation does not supply the behavior described in the requirements.

B:

Administrators use it to enable a service API for a project, rather than to enumerate the APIs enabled for a project. Applying it would change the wrong component of this deployment.

D:

The result of this choice would be to authorize API enablement operations. The requested outcome, to enumerate the APIs enabled for a project, is handled at a different layer or through another operation.

Associate Cloud Engineer Practice Tests