Google Associate Cloud Engineer Practice Test 70

Question 690

An infrastructure deployment job must modify Google Cloud project resources with auditable least-privilege authority. Which approach should be selected?

  1. Run the deployment under a dedicated automation service account with scoped roles
  2. Grant the pipeline's effective build service account the necessary Artifact Registry writer access
  3. Distinguish the build/deploy service account from the Cloud Run runtime service account
  4. Create a user-managed service account dedicated to the inventory application
  5. Use Workload Identity Federation to acquire deployment credentials without storing a Google private key

Explanation

Correct Answer

A:

A dedicated automation identity separates pipeline changes from human user privileges. Granting only required resource roles limits the impact of a compromised build or deployment job.

Incorrect Answers

B:

Its purpose is to authorize a CI build identity to push container images. That distinction matters: the scenario calls for an action to deploy infrastructure with a scoped machine principal, not this separate configuration task.

C:

Administrators use it to separate pipeline identity from deployed application's runtime identity, rather than to deploy infrastructure with a scoped machine principal. Applying it would change the wrong component of this deployment.

D:

While this can create a dedicated nonhuman application principal, the present task requires an action to deploy infrastructure with a scoped machine principal. This operation does not supply the behavior described in the requirements.

E:

This mechanism is intended to authenticate Terraform CI through external OIDC federation. It does not implement the required action to deploy infrastructure with a scoped machine principal, even though both are relevant to the same general service.

Question 691

A public CI platform deploys Terraform to Google Cloud and supports OIDC identity tokens. Which method addresses the task?

  1. Grant the pipeline's effective build service account the necessary Artifact Registry writer access
  2. Use Workload Identity Federation to acquire deployment credentials without storing a Google private key
  3. Run the deployment under a dedicated automation service account with scoped roles
  4. Distinguish the build/deploy service account from the Cloud Run runtime service account

Explanation

Correct Answer

B:

Federated CI credentials can be minted from trusted external OIDC assertions. This avoids an enduring service account key in the public CI platform's secret storage.

Incorrect Answers

A:

The tool can authorize a CI build identity to push container images, but it cannot be substituted for the capability needed to run keyless off-cloud infrastructure deployment. Its operational effect is not equivalent.

C:

It can assign least-privilege automation identity for infrastructure changes; however, it does not provide the specific operation to run keyless off-cloud infrastructure deployment. The two controls serve different purposes.

D:

This choice is useful to separate pipeline identity from deployed application's runtime identity. The stated task is to run keyless off-cloud infrastructure deployment, which requires a different mechanism or permission scope.

Question 692

A team sees successful Cloud Run deployment logs but permission errors in its running service and wants to fix the correct identity. What is the best next step?

  1. Run the deployment under a dedicated automation service account with scoped roles
  2. Distinguish the build/deploy service account from the Cloud Run runtime service account
  3. Use Workload Identity Federation to acquire deployment credentials without storing a Google private key
  4. Grant the pipeline's effective build service account the necessary Artifact Registry writer access
  5. Use Workload Identity Federation for the nonhuman scheduled application

Explanation

Correct Answer

B:

CI and deployment identities manage infrastructure, whereas the Cloud Run runtime identity makes application API calls. Their IAM grants should be inspected independently when investigating failures.

Incorrect Answers

A:

This approach can assign least-privilege automation identity for infrastructure changes. The requirement is to troubleshoot deployment versus runtime IAM, so it controls a different part of the workflow and leaves that result unaddressed.

C:

Its purpose is to authenticate Terraform CI through external OIDC federation. That distinction matters: the scenario calls for an action to troubleshoot deployment versus runtime IAM, not this separate configuration task.

D:

This setting would authorize a CI build identity to push container images. That behavior does not establish the requested ability to troubleshoot deployment versus runtime IAM; it addresses an adjacent concern instead.

E:

An operator would use this action to choose external workload federation rather than workforce federation, chiefly when trying to authenticate a scheduled nonhuman process; The current requirement is to troubleshoot deployment versus runtime IAM, which remains unresolved by that operation.

Question 693

A security team needs to investigate who created or deleted a user-managed service account key. What should the administrator do?

  1. Inspect relevant IAM Credentials API audit log records and configure required log visibility
  2. Use Policy Troubleshooter with the actual principal, permission, and target resource
  3. Inspect the service account's policy bindings, account state, and remaining attached or federated access paths
  4. Review the relevant Cloud Audit Logs Admin Activity entries for IAM service account key operations

Explanation

Correct Answer

D:

Admin Activity audit logs record supported administrative changes including key management operations. They provide an audit trail that is more suitable than searching application stdout for identity creation events.

Incorrect Answers

A:

This mechanism is intended to inspect token-generation activity associated with impersonation. It does not implement the required action to identify who created or deleted a workload key, even though both are relevant to the same general service.

B:

The result of this choice would be to diagnose effective service account IAM access. The requested outcome, to identify who created or deleted a workload key, is handled at a different layer or through another operation.

C:

The tool can audit residual service account grants and use paths, but it cannot be substituted for the capability needed to identify who created or deleted a workload key. Its operational effect is not equivalent.

Question 694

A production team wants to trace impersonation calls that minted service account access tokens. Which choice provides the required behavior?

  1. Use Policy Troubleshooter with the actual principal, permission, and target resource
  2. Review the relevant Cloud Audit Logs Admin Activity entries for IAM service account key operations
  3. Use attached or federated short-lived credentials instead of creating a user-managed key
  4. Inspect relevant IAM Credentials API audit log records and configure required log visibility
  5. Inspect the service account's policy bindings, account state, and remaining attached or federated access paths

Explanation

Correct Answer

D:

IAM Credentials API operations can produce audit records relevant to impersonation investigations. Log availability depends on the audit-log category and associated configuration.

Incorrect Answers

A:

This approach can diagnose effective service account IAM access. The requirement is to investigate who issued short-lived credentials, so it controls a different part of the workflow and leaves that result unaddressed.

B:

Using this action would audit administrative service account key changes, not investigate who issued short-lived credentials. Its function is different from the specific change described in the scenario.

C:

This proposal can avoid distributing long-lived service account private keys, but the failure or goal described here calls for a way to investigate who issued short-lived credentials; It changes the wrong control or scope for the requested outcome.

E:

This setting would audit residual service account grants and use paths. That behavior does not establish the requested ability to investigate who issued short-lived credentials; it addresses an adjacent concern instead.

Question 695

A service account appears to have a role but a workload request is denied and security needs the complete effective-permission reasoning. Which approach should be selected?

  1. Inspect the service account's policy bindings, account state, and remaining attached or federated access paths
  2. Enforce the applicable organization policy constraint disabling service account key creation
  3. Inspect relevant IAM Credentials API audit log records and configure required log visibility
  4. Review the relevant Cloud Audit Logs Admin Activity entries for IAM service account key operations
  5. Use Policy Troubleshooter with the actual principal, permission, and target resource

Explanation

Correct Answer

E:

Policy Troubleshooter evaluates authorization context, including applicable allow, deny, and conditional constraints. Reviewing one visible project binding may overlook inherited or other policies.

Incorrect Answers

A:

The result of this choice would be to audit residual service account grants and use paths. The requested outcome, to explain a workload's resource access denial, is handled at a different layer or through another operation.

B:

An operator would use this action to block new user-managed service account key creation, chiefly when trying to enforce an organization-wide key issuance restriction; The current requirement is to explain a workload's resource access denial, which remains unresolved by that operation.

C:

Administrators use it to inspect token-generation activity associated with impersonation, rather than to explain a workload's resource access denial. Applying it would change the wrong component of this deployment.

D:

While this can audit administrative service account key changes, the present task requires an action to explain a workload's resource access denial. This operation does not supply the behavior described in the requirements.

Question 696

A retired service account still appears in access review results after its key files were removed. Which method addresses the task?

  1. Use Policy Troubleshooter with the actual principal, permission, and target resource
  2. Inspect the service account's policy bindings, account state, and remaining attached or federated access paths
  3. Inspect relevant IAM Credentials API audit log records and configure required log visibility
  4. Review the relevant Cloud Audit Logs Admin Activity entries for IAM service account key operations
  5. Call IAM Credentials generateAccessToken under a principal with appropriate delegation rights

Explanation

Correct Answer

B:

Deleting private keys does not remove a service account's IAM grants or every possible identity-use pathway. Review the principal's authorization and lifecycle separately from its keys.

Incorrect Answers

A:

It can diagnose effective service account IAM access; however, it does not provide the specific operation to review retired identity access beyond key removal. The two controls serve different purposes.

C:

This choice is useful to inspect token-generation activity associated with impersonation. The stated task is to review retired identity access beyond key removal, which requires a different mechanism or permission scope.

D:

Using this action would audit administrative service account key changes, not review retired identity access beyond key removal. Its function is different from the specific change described in the scenario.

E:

For the stated need to review retired identity access beyond key removal, this would instead mint access tokens using the IAM Credentials API; it supports the separate task to obtain short-lived credentials for delegated service account access, not the required configuration.

Question 697

An on-premises workload uses an enterprise OIDC issuer and must call Google Cloud without exporting a service account private key. Which implementation matches this requirement?

  1. Update the relevant provider issuer configuration and validate the external token trust requirements
  2. Configure a compatible Workload Identity Federation provider with trusted issuer, audience, mappings, and IAM grants
  3. Use Workload Identity Federation for the nonhuman scheduled application
  4. Use a supported external-account credential configuration with automatic token exchange and refresh

Explanation

Correct Answer

B:

A properly configured federation trust exchanges external identity evidence for short-lived Google credentials. Issuer and audience verification prevent arbitrary external tokens from being accepted.

Incorrect Answers

A:

While this can repair external OIDC issuer trust configuration, the present task requires an action to connect on-premises software to Google APIs without long-lived keys. This operation does not supply the behavior described in the requirements.

C:

Administrators use it to choose external workload federation rather than workforce federation, rather than to connect on-premises software to Google APIs without long-lived keys. Applying it would change the wrong component of this deployment.

D:

This approach can refresh federated credentials through a supported library flow. The requirement is to connect on-premises software to Google APIs without long-lived keys, so it controls a different part of the workflow and leaves that result unaddressed.

Question 698

A security engineer must choose between Workforce Identity Federation for human enterprise users and Workload Identity Federation for a scheduled external application. What should the administrator do?

  1. Use Workload Identity Federation for the nonhuman scheduled application
  2. Use a supported external-account credential configuration with automatic token exchange and refresh
  3. Register the external scheduled job as an interactive user in a workforce pool
  4. Update the relevant provider issuer configuration and validate the external token trust requirements
  5. Configure a compatible Workload Identity Federation provider with trusted issuer, audience, mappings, and IAM grants

Explanation

Correct Answer

A:

Workload Identity Federation targets external workloads, while Workforce Identity Federation is designed for workforce users and their access. Selecting the right principal type supports clearer authentication and authorization controls.

Incorrect Answers

B:

It can refresh federated credentials through a supported library flow; however, it does not provide the specific operation to authenticate a scheduled nonhuman process. The two controls serve different purposes.

C:

A scheduled nonhuman application should use a workload federation trust rather than a human workforce identity. Treating automation as an interactive workforce user selects the wrong identity model.

D:

Select this when the goal is to repair external OIDC issuer trust configuration. Here the decisive requirement is to authenticate a scheduled nonhuman process, and that outcome is not achieved by this action.

E:

The tool can federate an on-premises OIDC workload identity, but it cannot be substituted for the capability needed to authenticate a scheduled nonhuman process. Its operational effect is not equivalent.

Question 699

A federated identity configuration stops working because the external issuer changed its OIDC issuer URL. Which choice provides the required behavior?

  1. Configure a compatible Workload Identity Federation provider with trusted issuer, audience, mappings, and IAM grants
  2. Create a user-managed service account dedicated to the inventory application
  3. Use Workload Identity Federation for the nonhuman scheduled application
  4. Update the relevant provider issuer configuration and validate the external token trust requirements
  5. Use a supported external-account credential configuration with automatic token exchange and refresh

Explanation

Correct Answer

D:

Federation providers validate token origin and related claims. A mismatch between actual issued tokens and configured provider metadata can prevent token exchange.

Incorrect Answers

A:

Its purpose is to federate an on-premises OIDC workload identity. That distinction matters: the scenario calls for an action to restore federation after issuer metadata changes, not this separate configuration task.

B:

While this can create a dedicated nonhuman application principal, the present task requires an action to restore federation after issuer metadata changes. This operation does not supply the behavior described in the requirements.

C:

Using this action would choose external workload federation rather than workforce federation, not restore federation after issuer metadata changes. Its function is different from the specific change described in the scenario.

E:

This setting would refresh federated credentials through a supported library flow. That behavior does not establish the requested ability to restore federation after issuer metadata changes; it addresses an adjacent concern instead.

Question 700

A deployment job refreshes its external OIDC token periodically and must continue calling Google APIs without hardcoded access tokens. Which approach should be selected?

  1. Use Workload Identity Federation for the nonhuman scheduled application
  2. Configure a Workload Identity Pool, an OIDC provider, and suitable Google IAM trust or impersonation bindings
  3. Use a supported external-account credential configuration with automatic token exchange and refresh
  4. Update the relevant provider issuer configuration and validate the external token trust requirements
  5. Configure a compatible Workload Identity Federation provider with trusted issuer, audience, mappings, and IAM grants

Explanation

Correct Answer

C:

Google credential libraries can use external-account configuration to obtain and refresh temporary Google access credentials. Manually embedding a single issued access token would fail when that token expires.

Incorrect Answers

A:

The result of this choice would be to choose external workload federation rather than workforce federation. The requested outcome, to maintain authenticated external workload API calls over time, is handled at a different layer or through another operation.

B:

In a workflow for workload identity federation with oidc ci, it can federate a CI OIDC identity into Google Cloud; This question instead asks how to maintain authenticated external workload API calls over time; substituting the former action would leave that distinct technical requirement unmet.

D:

Select this when the goal is to repair external OIDC issuer trust configuration. Here the decisive requirement is to maintain authenticated external workload API calls over time, and that outcome is not achieved by this action.

E:

Administrators use it to federate an on-premises OIDC workload identity, rather than to maintain authenticated external workload API calls over time. Applying it would change the wrong component of this deployment.

Associate Cloud Engineer Practice Tests