Question 80

A script operates inside Google Cloud and should avoid downloading a long-lived service account JSON key. Which choice provides the required behavior?

  1. Supply the command's --project flag or supported project argument
  2. Attach an appropriate service identity and use its metadata-provided credentials
  3. Run gcloud auth login through the supported interactive flow
  4. Set the active gcloud account or use an explicit --account flag
  5. Run gcloud auth application-default login for local development

Explanation

Correct Answer

B:

Google-managed runtime credentials let a workload obtain short-lived tokens. The workload still requires IAM roles on the destination resources.

Incorrect Answers

A:

This proposal can override the CLI default project per command, but the failure or goal described here calls for a way to avoid static keys for in-cloud API calls; It changes the wrong control or scope for the requested outcome.

C:

Its purpose is to authenticate gcloud as a user. That distinction matters: the scenario calls for an action to avoid static keys for in-cloud API calls, not this separate configuration task.

D:

This setting would select the active CLI credential identity. That behavior does not establish the requested ability to avoid static keys for in-cloud API calls; it addresses an adjacent concern instead.

E:

While this can initialize local application default credentials, the present task requires an action to avoid static keys for in-cloud API calls. This operation does not supply the behavior described in the requirements.

Question 81

A contractor signs in through an external OIDC provider and needs limited console access. How should the team proceed?

  1. Grant the necessary IAM role to the correct federated principal at the appropriate scope
  2. Create a Workforce Identity Federation pool and provider with appropriate attribute mapping
  3. Use Workforce Identity Federation for employees and Workload Identity Federation for nonhuman workloads
  4. Use a principal set mapping and scoped IAM binding appropriate to the workforce pool

Explanation

Correct Answer

B:

Workforce pools represent external human users and groups as federated principals. IAM bindings then authorize only the intended resources.

Incorrect Answers

A:

This mechanism is intended to authorize a federated principal after authentication. It does not implement the required action to authorize OIDC-based contractor access, even though both are relevant to the same general service.

C:

The tool can distinguish human and workload federation, but it cannot be substituted for the capability needed to authorize OIDC-based contractor access. Its operational effect is not equivalent.

D:

The result of this choice would be to scope federated human access to an external group. The requested outcome, to authorize OIDC-based contractor access, is handled at a different layer or through another operation.

Question 82

Administrators need to restrict federated workforce access to a specific external identity group. What is the most direct solution?

  1. Use a principal set mapping and scoped IAM binding appropriate to the workforce pool
  2. Create a Workforce Identity Federation pool and provider with appropriate attribute mapping
  3. Grant the necessary IAM role to the correct federated principal at the appropriate scope
  4. Review Google's standalone organization setup path and required identity administration
  5. Use Workforce Identity Federation for employees and Workload Identity Federation for nonhuman workloads

Explanation

Correct Answer

A:

Mapped attributes can represent a filtered group of external workforce identities. Granting that set the narrow role avoids granting all identities in the pool.

Incorrect Answers

B:

This choice is useful to configure external workforce identity mapping. The stated task is to limit a federated workforce principal set, which requires a different mechanism or permission scope.

C:

This approach can authorize a federated principal after authentication. The requirement is to limit a federated workforce principal set, so it controls a different part of the workflow and leaves that result unaddressed.

D:

Choosing this would bootstrap a supported standalone organization, an appropriate action for organization setup and ownership operations; It cannot take the place of the separate step needed to limit a federated workforce principal set in this specific situation.

E:

This setting would distinguish human and workload federation. That behavior does not establish the requested ability to limit a federated workforce principal set; it addresses an adjacent concern instead.

Question 83

A security architect needs to separate external employee logins from external CI pipeline credentials. Which implementation matches this requirement?

  1. Use Workforce Identity Federation for employees and Workload Identity Federation for nonhuman workloads
  2. Create a Workforce Identity Federation pool and provider with appropriate attribute mapping
  3. Use a principal set mapping and scoped IAM binding appropriate to the workforce pool
  4. Use Resource Manager organization listing or the appropriate console organization view
  5. Grant the necessary IAM role to the correct federated principal at the appropriate scope

Explanation

Correct Answer

A:

Workforce federation addresses user identity access, while workload federation addresses external applications and jobs. Both avoid unnecessary permanent service-account keys but target different identity categories.

Incorrect Answers

B:

The result of this choice would be to configure external workforce identity mapping. The requested outcome, to select the proper federation type for the principal, is handled at a different layer or through another operation.

C:

This mechanism is intended to scope federated human access to an external group. It does not implement the required action to select the proper federation type for the principal, even though both are relevant to the same general service.

D:

This proposal can locate the organization resource identifier, but the failure or goal described here calls for a way to select the proper federation type for the principal; It changes the wrong control or scope for the requested outcome.

E:

While this can authorize a federated principal after authentication, the present task requires an action to select the proper federation type for the principal. This operation does not supply the behavior described in the requirements.

Question 84

An administrator sees an authenticated federated worker still receive permission denied on an API call. What should the administrator do?

  1. Use Workforce Identity Federation for employees and Workload Identity Federation for nonhuman workloads
  2. Grant the necessary IAM role to the correct federated principal at the appropriate scope
  3. Use a principal set mapping and scoped IAM binding appropriate to the workforce pool
  4. Attach an appropriate service identity and use its metadata-provided credentials
  5. Create a Workforce Identity Federation pool and provider with appropriate attribute mapping

Explanation

Correct Answer

B:

Successful external authentication does not by itself authorize cloud API operations. IAM bindings must match the mapped principal or principal set.

Incorrect Answers

A:

This choice is useful to distinguish human and workload federation. The stated task is to fix federated sign-in with missing resource permissions, which requires a different mechanism or permission scope.

C:

The tool can scope federated human access to an external group, but it cannot be substituted for the capability needed to fix federated sign-in with missing resource permissions. Its operational effect is not equivalent.

D:

An operator would use this action to use attached workload credentials, chiefly when trying to avoid static keys for in-cloud API calls; The current requirement is to fix federated sign-in with missing resource permissions, which remains unresolved by that operation.

E:

Using this action would configure external workforce identity mapping, not fix federated sign-in with missing resource permissions. Its function is different from the specific change described in the scenario.

Question 85

A company adopts an organization resource and plans to bring existing projects under a centralized hierarchy. Which TWO controls are particularly important for governance after the projects have been placed under it? (Choose TWO.)

  1. Convert every project into a Cloud Billing account before assigning a parent
  2. Review effective organization policy constraints for each destination folder
  3. Define appropriate organization or folder IAM policies that descendants will inherit
  4. Delete and recreate every existing Compute Engine instance to make organization inheritance work

Explanation

Correct Answers

B:

Folder placement can change inherited resource-configuration restrictions. Governance should check the effective policies that projects must satisfy after reorganization.

C:

Hierarchy-level IAM bindings provide consistent centralized authorization to descendant resources. The organization must still follow least privilege and understand inherited access.

Incorrect Answers

A:

Projects and billing accounts are different resource types. Project hierarchy placement does not require turning each project into a payer or abandoning its existing billing association.

D:

IAM and organization policies can apply through a project's ancestors without recreating all VMs. Resource compliance may need remediation, but blanket deletion is unnecessary.

Question 86

A small organization is evaluating a standalone Google Cloud organization arrangement. How should the team proceed?

  1. Enumerate folder resources using Resource Manager at the organization scope
  2. Review Google's standalone organization setup path and required identity administration
  3. Adopt an organization-backed resource hierarchy for managed projects
  4. Use Resource Manager organization listing or the appropriate console organization view

Explanation

Correct Answer

B:

Standalone organization options provide an organization-level resource boundary where supported. They still require a managed governance model rather than assuming every project is a root.

Incorrect Answers

A:

It can list the organization's folder structure; however, it does not provide the specific operation to create a managed root without an established Workspace rollout. The two controls serve different purposes.

C:

This mechanism is intended to place projects under organizational governance. It does not implement the required action to create a managed root without an established Workspace rollout, even though both are relevant to the same general service.

D:

Select this when the goal is to locate the organization resource identifier. Here the decisive requirement is to create a managed root without an established Workspace rollout, and that outcome is not achieved by this action.

Question 87

An administrator must find the numeric organization identifier for a policy automation. What is the most direct solution?

  1. Create a folder under the organization and place the division's projects inside it
  2. Adopt an organization-backed resource hierarchy for managed projects
  3. Enumerate folder resources using Resource Manager at the organization scope
  4. Use Resource Manager organization listing or the appropriate console organization view
  5. Review Google's standalone organization setup path and required identity administration

Explanation

Correct Answer

D:

Organization IDs identify the resource-hierarchy root in APIs and commands. Project IDs and billing account IDs name different resources.

Incorrect Answers

A:

This setting would group child projects under a common policy boundary. That behavior does not establish the requested ability to identify the parent root for organization-scope commands; it addresses an adjacent concern instead.

B:

While this can place projects under organizational governance, the present task requires an action to identify the parent root for organization-scope commands. This operation does not supply the behavior described in the requirements.

C:

Using this action would list the organization's folder structure, not identify the parent root for organization-scope commands. Its function is different from the specific change described in the scenario.

E:

Its purpose is to bootstrap a supported standalone organization. That distinction matters: the scenario calls for an action to identify the parent root for organization-scope commands, not this separate configuration task.

Question 88

The infrastructure team needs to locate all folders beneath the company's organization. Which implementation matches this requirement?

  1. Review Google's standalone organization setup path and required identity administration
  2. Enumerate folder resources using Resource Manager at the organization scope
  3. Use Resource Manager organization listing or the appropriate console organization view
  4. Adopt an organization-backed resource hierarchy for managed projects
  5. Describe the project with Resource Manager and inspect the parent reference

Explanation

Correct Answer

B:

Folders are first-class hierarchy objects. Resource Manager listing exposes their parent relationships and supports inventory of the folder tree.

Incorrect Answers

A:

Administrators use it to bootstrap a supported standalone organization, rather than to discover administrative child folders. Applying it would change the wrong component of this deployment.

C:

The result of this choice would be to locate the organization resource identifier. The requested outcome, to discover administrative child folders, is handled at a different layer or through another operation.

D:

Select this when the goal is to place projects under organizational governance. Here the decisive requirement is to discover administrative child folders, and that outcome is not achieved by this action.

E:

For the stated need to discover administrative child folders, this would instead read a project's parent relationship; it supports the separate task to determine the resource hierarchy parent of a project, not the required configuration.

Question 89

A new project needs a globally unique text identifier for API calls and deployment automation. Which action is most appropriate?

  1. Keep using the immutable project ID in scripts
  2. Choose a valid unique project ID during project creation
  3. Use the project shutdown process with its documented recovery window
  4. Restore or undelete the project using Resource Manager where eligible

Explanation

Correct Answer

B:

Project IDs are used widely in resource names and APIs and cannot simply be renamed after creation. The mutable project display name serves a different purpose.

Incorrect Answers

A:

Using this action would identify a project by its stable ID, not choose a durable project identifier. Its function is different from the specific change described in the scenario.

C:

This setting would start a project deletion lifecycle. That behavior does not establish the requested ability to choose a durable project identifier; it addresses an adjacent concern instead.

D:

This choice is useful to recover a recently deleted project. The stated task is to choose a durable project identifier, which requires a different mechanism or permission scope.

Question 90

An engineer sees a project display name change while scripts must continue addressing the same project. Which solution should be used?

  1. Use the project shutdown process with its documented recovery window
  2. Restore or undelete the project using Resource Manager where eligible
  3. Grant the needed project-creation permissions on the appropriate hierarchy resource
  4. Choose a valid unique project ID during project creation
  5. Keep using the immutable project ID in scripts

Explanation

Correct Answer

E:

A project's human-readable display name is editable, whereas its ID remains the stable identifier for many commands and resource paths.

Incorrect Answers

A:

Administrators use it to start a project deletion lifecycle, rather than to preserve scripts across display-name changes. Applying it would change the wrong component of this deployment.

B:

While this can recover a recently deleted project, the present task requires an action to preserve scripts across display-name changes. This operation does not supply the behavior described in the requirements.

C:

An operator would use this action to delegate project creation at a parent scope, chiefly when trying to allow creation of projects in one folder; The current requirement is to preserve scripts across display-name changes, which remains unresolved by that operation.

D:

The result of this choice would be to assign the project ID used by APIs. The requested outcome, to preserve scripts across display-name changes, is handled at a different layer or through another operation.

Associate Cloud Engineer Practice Tests