Google Associate Cloud Engineer Practice Test 64

Question 630

The same access must apply to all members of an operations team through a managed principal. Which configuration best meets the requirement?

  1. Use an IAM service account as the workload principal
  2. Identify the intended binding and condition rather than editing every matching role entry
  3. Use Workforce Identity Federation principal identifiers
  4. Use the appropriate user principal in the binding
  5. Use a Google group as the IAM binding member

Explanation

Correct Answer

E:

Group principals represent memberships maintained by an identity system. They reduce the need for individual per-person bindings.

Incorrect Answers

A:

Administrators use it to identify an application as a service account, rather than to authorize a rotating team. Applying it would change the wrong component of this deployment.

B:

This proposal can edit a particular conditional IAM binding, but the failure or goal described here calls for a way to authorize a rotating team; It changes the wrong control or scope for the requested outcome.

C:

While this can represent external human identities in IAM, the present task requires an action to authorize a rotating team. This operation does not supply the behavior described in the requirements.

D:

Its purpose is to bind an IAM role to a human user. That distinction matters: the scenario calls for an action to authorize a rotating team, not this separate configuration task.

Question 631

A deployed application needs a nonhuman identity to call cloud APIs. What should be configured?

  1. Use Workforce Identity Federation principal identifiers
  2. Use an IAM service account as the workload principal
  3. Bind a role to a Cloud Identity group rather than to each employee
  4. Use a Google group as the IAM binding member
  5. Use the appropriate user principal in the binding

Explanation

Correct Answer

B:

Service accounts represent application identities with independent IAM bindings. Using a human user's credentials for a production service complicates lifecycle and auditability.

Incorrect Answers

A:

Select this when the goal is to represent external human identities in IAM. Here the decisive requirement is to separate workload from human identity, and that outcome is not achieved by this action.

C:

An operator would use this action to delegate access through a Google group, chiefly when trying to simplify team authorization management; The current requirement is to separate workload from human identity, which remains unresolved by that operation.

D:

It can grant IAM permissions to a group; however, it does not provide the specific operation to separate workload from human identity. The two controls serve different purposes.

E:

The tool can bind an IAM role to a human user, but it cannot be substituted for the capability needed to separate workload from human identity. Its operational effect is not equivalent.

Question 632

An external OIDC employee population needs access without provisioning each as a conventional Google user. Which action is most appropriate?

  1. Use Workforce Identity Federation principal identifiers
  2. Use the appropriate user principal in the binding
  3. Review the resource path and inherited descendants affected by the binding
  4. Use an IAM service account as the workload principal
  5. Use a Google group as the IAM binding member

Explanation

Correct Answer

A:

Workforce federation maps external human attributes into Google Cloud principals. Authorization still happens through resource IAM policies.

Incorrect Answers

B:

While this can bind an IAM role to a human user, the present task requires an action to authorize non-Google workforce users. This operation does not supply the behavior described in the requirements.

C:

For the stated need to authorize non-Google workforce users, this would instead inspect role grant blast radius; it supports the separate task to avoid an overly broad inherited assignment, not the required configuration.

D:

This approach can identify an application as a service account. The requirement is to authorize non-Google workforce users, so it controls a different part of the workflow and leaves that result unaddressed.

E:

Its purpose is to grant IAM permissions to a group. That distinction matters: the scenario calls for an action to authorize non-Google workforce users, not this separate configuration task.

Question 633

A team needs a distinct nonhuman identity for a new scheduled inventory application, separate from users and other workloads. Which method addresses the task?

  1. Create a user-managed service account dedicated to the inventory application
  2. Disable the retired service account
  3. Undelete the service account using its unique identifier if restoration remains supported
  4. List service accounts for the project using IAM console or gcloud iam service-accounts list

Explanation

Correct Answer

A:

User-managed service accounts represent workloads rather than people. A dedicated identity enables targeted role grants, clearer auditing, and independent lifecycle management.

Incorrect Answers

B:

This mechanism is intended to temporarily block a workload identity from authenticating. It does not implement the required action to give one application a distinct workload identity, even though both are relevant to the same general service.

C:

The tool can recover a recently deleted account identity, but it cannot be substituted for the capability needed to give one application a distinct workload identity. Its operational effect is not equivalent.

D:

Select this when the goal is to inventory service account identities in a project. Here the decisive requirement is to give one application a distinct workload identity, and that outcome is not achieved by this action.

Question 634

A security auditor must enumerate the user-managed service accounts belonging to a particular project. What is the best next step?

  1. Undelete the service account using its unique identifier if restoration remains supported
  2. List service accounts for the project using IAM console or gcloud iam service-accounts list
  3. Configure its service identity to a dedicated user-managed service account
  4. Create a user-managed service account dedicated to the inventory application
  5. Disable the retired service account

Explanation

Correct Answer

B:

Listing service accounts exposes their names and identities for inventory review. It does not reveal a plaintext secret key or automatically list every credential on all workloads.

Incorrect Answers

A:

Using this action would recover a recently deleted account identity, not enumerate existing project service accounts. Its function is different from the specific change described in the scenario.

C:

An operator would use this action to set a dedicated Cloud Run runtime principal, chiefly when trying to select the identity for Cloud Run API calls; The current requirement is to enumerate existing project service accounts, which remains unresolved by that operation.

D:

This approach can create a dedicated nonhuman application principal. The requirement is to enumerate existing project service accounts, so it controls a different part of the workflow and leaves that result unaddressed.

E:

This choice is useful to temporarily block a workload identity from authenticating. The stated task is to enumerate existing project service accounts, which requires a different mechanism or permission scope.

Question 635

A service account is no longer supposed to run new jobs, but the security team needs a reversible retirement process and an audit trail. Which THREE actions belong in a controlled decommission plan? (Choose THREE.)

  1. Copy its user-managed private keys into the logs to preserve troubleshooting access
  2. Disable the service account while monitoring for legitimate workloads that unexpectedly depended on it
  3. Review remaining permissions, key state and audit records before a final deletion decision
  4. Inventory the service account's current resource bindings, attached workloads and federated use paths
  5. Automatically grant Project Owner to every replacement workload to prevent authorization errors

Explanation

Correct Answers

B:

Disabling the identity is reversible and stops it from being used as an active credential in supported flows. Monitoring reveals remaining dependencies before a final deletion decision.

C:

Role bindings and key-related audit records help verify both exposure and cleanup scope. Deleting an account without those checks can leave unresolved dependencies or investigations.

D:

A decommission should identify which resources and principals still depend on the identity. Attached workloads or federation configurations may otherwise fail unexpectedly.

Incorrect Answers

A:

Private keys should not be published into log storage. Their disclosure would create additional credential risk instead of preserving a controlled audit trail.

E:

Broad replacement access violates least privilege and hides missing dependency analysis. Replacement identities should receive only their required scoped permissions.

Question 636

The team mistakenly deleted a service account and wants to restore it within the supported recovery window. What should be configured?

  1. List service accounts for the project using IAM console or gcloud iam service-accounts list
  2. Inspect the Compute Engine default service account attached to the VM
  3. Create a user-managed service account dedicated to the inventory application
  4. Disable the retired service account
  5. Undelete the service account using its unique identifier if restoration remains supported

Explanation

Correct Answer

E:

Google Cloud supports undeleting a recently deleted service account during a limited recovery period. Recreating an account with a similar display name does not necessarily restore its original identity.

Incorrect Answers

A:

It can inventory service account identities in a project; however, it does not provide the specific operation to restore a deleted service account within its recovery window. The two controls serve different purposes.

B:

The tool can identify the default runtime identity used by a VM, but it cannot be substituted for the capability needed to restore a deleted service account within its recovery window. Its operational effect is not equivalent.

C:

This setting would create a dedicated nonhuman application principal. That behavior does not establish the requested ability to restore a deleted service account within its recovery window; it addresses an adjacent concern instead.

D:

This choice is useful to temporarily block a workload identity from authenticating. The stated task is to restore a deleted service account within its recovery window, which requires a different mechanism or permission scope.

Question 637

An engineer creates a Compute Engine VM and wants to know which identity it might use if no dedicated identity is selected. Which approach should be selected?

  1. Attach a service account to the VM instead of relying on a human user's credentials
  2. Create and attach separate user-managed service accounts with only the permissions each job needs
  3. Inspect the Compute Engine default service account attached to the VM
  4. Retain required Google-managed service agents and review their assigned service-agent roles

Explanation

Correct Answer

C:

Compute Engine has a default service account that can be attached to VMs, with permissions dependent on organization configuration. Its presence alone does not guarantee any particular broad project role.

Incorrect Answers

A:

Its purpose is to use a workload principal instead of an employee identity. That distinction matters: the scenario calls for an action to determine a VM's attached default identity, not this separate configuration task.

B:

Administrators use it to isolate workload privileges with dedicated identities, rather than to determine a VM's attached default identity. Applying it would change the wrong component of this deployment.

D:

While this can preserve a Google-managed service agent used by infrastructure, the present task requires an action to determine a VM's attached default identity. This operation does not supply the behavior described in the requirements.

Question 638

An administrator sees a service agent for a managed Google service and considers deleting it to clean up unused accounts. Which method addresses the task?

  1. Use Application Default Credentials with the VM's attached service account
  2. Inspect the Compute Engine default service account attached to the VM
  3. Attach a service account to the VM instead of relying on a human user's credentials
  4. Create and attach separate user-managed service accounts with only the permissions each job needs
  5. Retain required Google-managed service agents and review their assigned service-agent roles

Explanation

Correct Answer

E:

Service agents are Google-managed service identities used to operate service features. Deleting them or stripping required permissions can interrupt dependent managed-service operations.

Incorrect Answers

A:

For the stated need to avoid breaking service-agent permissions, this would instead let client libraries obtain attached VM credentials; it supports the separate task to authenticate VM application code through ADC, not the required configuration.

B:

This mechanism is intended to identify the default runtime identity used by a VM. It does not implement the required action to avoid breaking service-agent permissions, even though both are relevant to the same general service.

C:

It can use a workload principal instead of an employee identity; however, it does not provide the specific operation to avoid breaking service-agent permissions. The two controls serve different purposes.

D:

The tool can isolate workload privileges with dedicated identities, but it cannot be substituted for the capability needed to avoid breaking service-agent permissions. Its operational effect is not equivalent.

Question 639

Several unrelated batch jobs are using one highly privileged default service account and security wants workload isolation. What is the best next step?

  1. Inspect the Compute Engine default service account attached to the VM
  2. Attach a service account to the VM and grant it the required bucket permission
  3. Attach a service account to the VM instead of relying on a human user's credentials
  4. Create and attach separate user-managed service accounts with only the permissions each job needs
  5. Retain required Google-managed service agents and review their assigned service-agent roles

Explanation

Correct Answer

D:

Separate per-workload identities reduce privilege sharing and attribution ambiguity. A common default account with many roles makes a compromise affect multiple jobs.

Incorrect Answers

A:

Using this action would identify the default runtime identity used by a VM, not remove a shared overly privileged service account. Its function is different from the specific change described in the scenario.

B:

In a workflow for compute engine service account attachment and adc, it can use an attached VM identity for keyless Cloud Storage access; This question instead asks how to remove a shared overly privileged service account; substituting the former action would leave that distinct technical requirement unmet.

C:

This approach can use a workload principal instead of an employee identity. The requirement is to remove a shared overly privileged service account, so it controls a different part of the workflow and leaves that result unaddressed.

E:

This setting would preserve a Google-managed service agent used by infrastructure. That behavior does not establish the requested ability to remove a shared overly privileged service account; it addresses an adjacent concern instead.

Question 640

A developer proposes assigning their personal Google user account to a VM to call APIs while unattended. Which configuration best meets the requirement?

  1. Apply least-privilege IAM roles to its attached service account and account for VM access scopes
  2. Create and attach separate user-managed service accounts with only the permissions each job needs
  3. Inspect the Compute Engine default service account attached to the VM
  4. Attach a service account to the VM instead of relying on a human user's credentials
  5. Retain required Google-managed service agents and review their assigned service-agent roles

Explanation

Correct Answer

D:

Service accounts provide a nonhuman principal suitable for deployed workloads. Embedding personal credentials creates lifecycle, revocation, and accountability problems.

Incorrect Answers

A:

The choice is aimed at a different purpose: to reduce API authority of a VM workload; Even if it can manage both service account IAM and applicable VM scopes, that would not accomplish the stated requirement to authenticate unattended VM API calls without a user credential.

B:

Select this when the goal is to isolate workload privileges with dedicated identities. Here the decisive requirement is to authenticate unattended VM API calls without a user credential, and that outcome is not achieved by this action.

C:

This mechanism is intended to identify the default runtime identity used by a VM. It does not implement the required action to authenticate unattended VM API calls without a user credential, even though both are relevant to the same general service.

E:

Administrators use it to preserve a Google-managed service agent used by infrastructure, rather than to authenticate unattended VM API calls without a user credential. Applying it would change the wrong component of this deployment.

Associate Cloud Engineer Practice Tests