Question 680
A legacy process still requires a downloaded service account key and the current key is nearing its retirement date. Which action is most appropriate?
- Use attached or federated short-lived credentials instead of creating a user-managed key
- Create a replacement key, migrate the client, then remove the old key under a controlled rotation plan
- Disable or delete the exposed key promptly and replace the affected authentication path
- Enforce the applicable organization policy constraint disabling service account key creation
- Replace the downloaded key workflow with supported short-lived service account impersonation
Explanation
Correct Answer
B:Key rotation limits exposure time for any one long-lived credential but does not eliminate key risks. Verify the workload uses the replacement before deleting the previous key.
Incorrect Answers
A:While this can avoid distributing long-lived service account private keys, the present task requires an action to replace an aging private key without interrupting the client. This operation does not supply the behavior described in the requirements.
C:Its purpose is to revoke a potentially exposed service account private key. That distinction matters: the scenario calls for an action to replace an aging private key without interrupting the client, not this separate configuration task.
D:This approach can block new user-managed service account key creation. The requirement is to replace an aging private key without interrupting the client, so it controls a different part of the workflow and leaves that result unaddressed.
E:The technical effect is to avoid static keys for command-line administrative automation, not to replace an aging private key without interrupting the client; That distinction matters here because the first operation serves replace a CLI key file with ephemeral credentials, rather than the scenario's required result.
Question 681
A service account can obtain tokens but its calls to BigQuery fail with insufficient permission. Which method addresses the task?
- Grant the needed BigQuery resource permissions to the service account principal
- Grant the required Cloud Storage object role on the specific bucket to the service account
- Grant the developer only the required impersonation permission on the service account, not dataset permissions on the developer identity
- Create a user-managed service account dedicated to the inventory application
- Inspect that service account's IAM policy bindings for impersonation-capable roles
Explanation
Correct Answer
A:Authorization to mint or use a service account token is separate from what that identity can do in BigQuery. The target resource needs applicable IAM permissions for the requested operation.
Incorrect Answers
B:The tool can assign bucket-scoped rights to a service account, but it cannot be substituted for the capability needed to fix BigQuery API authorization after successful token issuance. Its operational effect is not equivalent.
C:The result of this choice would be to grant impersonation without direct resource read rights. The requested outcome, to fix BigQuery API authorization after successful token issuance, is handled at a different layer or through another operation.
D:It can create a dedicated nonhuman application principal; however, it does not provide the specific operation to fix BigQuery API authorization after successful token issuance. The two controls serve different purposes.
E:This mechanism is intended to inspect impersonation grants on a service account. It does not implement the required action to fix BigQuery API authorization after successful token issuance, even though both are relevant to the same general service.
Question 682
A developer needs to run as a specific service account, but should not receive any rights to read its application datasets directly. What is the best next step?
- Inspect that service account's IAM policy bindings for impersonation-capable roles
- Grant the needed BigQuery resource permissions to the service account principal
- Grant the developer only the required impersonation permission on the service account, not dataset permissions on the developer identity
- Grant the required Cloud Storage object role on the specific bucket to the service account
Explanation
Correct Answer
C:An impersonation grant controls use of the service account, whereas data access can remain assigned to that workload principal. This allows auditing the delegated execution path separately from the developer's direct data access.
Incorrect Answers
A:Using this action would inspect impersonation grants on a service account, not separate developer and runtime data permissions. Its function is different from the specific change described in the scenario.
B:This choice is useful to authorize the service account as a BigQuery resource principal. The stated task is to separate developer and runtime data permissions, which requires a different mechanism or permission scope.
D:This setting would assign bucket-scoped rights to a service account. That behavior does not establish the requested ability to separate developer and runtime data permissions; it addresses an adjacent concern instead.
Question 683
An auditor wants to know who may impersonate a sensitive deployment service account. Which configuration best meets the requirement?
- Grant the required Cloud Storage object role on the specific bucket to the service account
- Grant the needed BigQuery resource permissions to the service account principal
- Configure the supported Kubernetes service account annotation and grant the workload permission to impersonate the IAM service account
- Inspect that service account's IAM policy bindings for impersonation-capable roles
- Grant the developer only the required impersonation permission on the service account, not dataset permissions on the developer identity
Explanation
Correct Answer
D:The service account resource has its own IAM policy governing principals able to act as or mint credentials for it. Resource IAM policies elsewhere show where the identity has access, not necessarily who can impersonate it.
Incorrect Answers
A:The result of this choice would be to assign bucket-scoped rights to a service account. The requested outcome, to identify principals allowed to use a sensitive identity, is handled at a different layer or through another operation.
B:While this can authorize the service account as a BigQuery resource principal, the present task requires an action to identify principals allowed to use a sensitive identity. This operation does not supply the behavior described in the requirements.
C:The technical effect is to map Kubernetes identity to an IAM service account, not to identify principals allowed to use a sensitive identity; That distinction matters here because the first operation serves enable GKE workload service-account impersonation, rather than the scenario's required result.
E:This mechanism is intended to grant impersonation without direct resource read rights. It does not implement the required action to identify principals allowed to use a sensitive identity, even though both are relevant to the same general service.
Question 684
A workload identity must write to a bucket but should not receive project-level object administration over unrelated buckets. What should be configured?
- Grant the developer only the required impersonation permission on the service account, not dataset permissions on the developer identity
- Grant the needed BigQuery resource permissions to the service account principal
- Use Policy Troubleshooter with the actual principal, permission, and target resource
- Inspect that service account's IAM policy bindings for impersonation-capable roles
- Grant the required Cloud Storage object role on the specific bucket to the service account
Explanation
Correct Answer
E:Resource-level IAM roles can scope service account permissions to a single bucket. Assigning equivalent roles at project level would authorize a broader set of storage resources.
Incorrect Answers
A:This choice is useful to grant impersonation without direct resource read rights. The stated task is to limit a service account's object write permissions, which requires a different mechanism or permission scope.
B:It can authorize the service account as a BigQuery resource principal; however, it does not provide the specific operation to limit a service account's object write permissions. The two controls serve different purposes.
C:Choosing this would diagnose effective service account IAM access, an appropriate action for service account audit and investigation operations; It cannot take the place of the separate step needed to limit a service account's object write permissions in this specific situation.
D:Using this action would inspect impersonation grants on a service account, not limit a service account's object write permissions. Its function is different from the specific change described in the scenario.
Question 685
A VM in a workload project needs to run with a service account belonging to a centralized identity project. Which approach should be selected?
- Retain a centralized account where suitable and explicitly configure supported cross-project usage and resource grants
- Grant the needed bucket IAM permissions to the centralized service account
- Set up supported cross-project service account attachment, including required policies and actAs permissions
- Enforce the relevant organization policy restriction on cross-project service account usage
Explanation
Correct Answer
C:Compute Engine can use a service account from another project when supported cross-project constraints and IAM permissions are satisfied. Project membership alone does not permit arbitrary cross-project identity attachment.
Incorrect Answers
A:Administrators use it to reuse a centrally governed identity across authorized projects, rather than to attach a centralized identity to a different project's VM. Applying it would change the wrong component of this deployment.
B:This approach can grant centralized identity access to another project's bucket. The requirement is to attach a centralized identity to a different project's VM, so it controls a different part of the workflow and leaves that result unaddressed.
D:Its purpose is to restrict cross-project service account usage centrally. That distinction matters: the scenario calls for an action to attach a centralized identity to a different project's VM, not this separate configuration task.
Question 686
A centrally managed service account is attached to an authorized VM but cannot access a bucket hosted in a third project. Which method addresses the task?
- Set up supported cross-project service account attachment, including required policies and actAs permissions
- Grant the needed bucket IAM permissions to the centralized service account
- Enforce the relevant organization policy restriction on cross-project service account usage
- Retain a centralized account where suitable and explicitly configure supported cross-project usage and resource grants
- Grant the administrator the required Service Account User permission on that service account
Explanation
Correct Answer
B:The service account's project of origin does not automatically grant access to resources in other projects. Each target resource must allow the identity's intended operations.
Incorrect Answers
A:Select this when the goal is to enable a VM to use a cross-project service account. Here the decisive requirement is to fix cross-project resource permissions for an attached service account, and that outcome is not achieved by this action.
C:It can restrict cross-project service account usage centrally; however, it does not provide the specific operation to fix cross-project resource permissions for an attached service account. The two controls serve different purposes.
D:This mechanism is intended to reuse a centrally governed identity across authorized projects. It does not implement the required action to fix cross-project resource permissions for an attached service account, even though both are relevant to the same general service.
E:The technical effect is to authorize an operator to attach a service account, not to fix cross-project resource permissions for an attached service account; That distinction matters here because the first operation serves fix service account attachment permissions, rather than the scenario's required result.
Question 687
A security officer must stop project owners from attaching service accounts owned by unrelated projects unless a central policy allows it. What is the best next step?
- Retain a centralized account where suitable and explicitly configure supported cross-project usage and resource grants
- Grant the required Cloud Storage object role on the specific bucket to the service account
- Enforce the relevant organization policy restriction on cross-project service account usage
- Grant the needed bucket IAM permissions to the centralized service account
- Set up supported cross-project service account attachment, including required policies and actAs permissions
Explanation
Correct Answer
C:An organization policy constraint can restrict cross-project service account attachment where supported. The security boundary is a policy restriction, not merely a grant or removal of an IAM role.
Incorrect Answers
A:This setting would reuse a centrally governed identity across authorized projects. That behavior does not establish the requested ability to block unauthorized attachment of identities from other projects; it addresses an adjacent concern instead.
B:Choosing this would assign bucket-scoped rights to a service account, an appropriate action for service account iam policy versus resource iam operations; It cannot take the place of the separate step needed to block unauthorized attachment of identities from other projects in this specific situation.
D:This approach can grant centralized identity access to another project's bucket. The requirement is to block unauthorized attachment of identities from other projects, so it controls a different part of the workflow and leaves that result unaddressed.
E:Its purpose is to enable a VM to use a cross-project service account. That distinction matters: the scenario calls for an action to block unauthorized attachment of identities from other projects, not this separate configuration task.
Question 688
A platform engineer assumes moving a service account to a different project is required whenever applications in multiple projects use it. Which configuration best meets the requirement?
- Retain a centralized account where suitable and explicitly configure supported cross-project usage and resource grants
- Set up supported cross-project service account attachment, including required policies and actAs permissions
- Grant the developer only the required impersonation permission on the service account, not dataset permissions on the developer identity
- Enforce the relevant organization policy restriction on cross-project service account usage
- Grant the needed bucket IAM permissions to the centralized service account
Explanation
Correct Answer
A:Service accounts are associated with owning projects, but access to resources can be granted across project boundaries. Whether attachment is supported also depends on relevant organization policies and permissions.
Incorrect Answers
B:Administrators use it to enable a VM to use a cross-project service account, rather than to avoid recreating identical service accounts in every project. Applying it would change the wrong component of this deployment.
C:This proposal can grant impersonation without direct resource read rights, but the failure or goal described here calls for a way to avoid recreating identical service accounts in every project; It changes the wrong control or scope for the requested outcome.
D:This mechanism is intended to restrict cross-project service account usage centrally. It does not implement the required action to avoid recreating identical service accounts in every project, even though both are relevant to the same general service.
E:Select this when the goal is to grant centralized identity access to another project's bucket. Here the decisive requirement is to avoid recreating identical service accounts in every project, and that outcome is not achieved by this action.
Question 689
An organization migrated a Cloud Build trigger from the legacy build service account to a dedicated user-managed build service account. The same build YAML now fails when trying to access protected resources. What should the operator establish before changing project-level roles?
- Identify the effective service account configured for the trigger and grant that specific identity only the permissions required by the build
- Grant Project Owner to all human developers so the nonhuman build identity can access resources
- Assume the previous legacy build service account's permissions automatically transfer to every custom service account
- Make the Artifact Registry repository public even when the failed operation accesses a private KMS key
Explanation
Correct Answer
A:Cloud Build authorization is evaluated against the identity actually executing the build. Changing the trigger to a custom build service account can change available IAM permissions; reviewing that identity first prevents unrelated broad grants.
Incorrect Answers
B:Human developers' Owner grants do not directly fix missing permissions for the build service account and violate least privilege.
C:A custom service account has distinct IAM bindings. Permissions on a former identity do not automatically move to a new one.
D:Publishing a repository neither fixes a KMS authorization issue nor provides an appropriate general remedy for an unidentified missing build permission.
Question 690
An infrastructure deployment job must modify Google Cloud project resources with auditable least-privilege authority. Which approach should be selected?
- Run the deployment under a dedicated automation service account with scoped roles
- Grant the pipeline's effective build service account the necessary Artifact Registry writer access
- Distinguish the build/deploy service account from the Cloud Run runtime service account
- Create a user-managed service account dedicated to the inventory application
- 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.