mcAfee Secure Website
23

Google Associate Cloud Engineer Bundle

Exam Code: Associate Cloud Engineer

Exam Name Associate Cloud Engineer

Certification Provider: Google

Corresponding Certification: Associate Cloud Engineer

Associate Cloud Engineer Training Materials $44.99

Reliable & Actual Study Materials for Associate Cloud Engineer Exam Success

The Latest Associate Cloud Engineer Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    Associate Cloud Engineer Questions & Answers

    391 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    Associate Cloud Engineer Video Course

    Associate Cloud Engineer Training Course

    234 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    Associate Cloud Engineer Study Guide

    849 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

Associate Cloud Engineer Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Google Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    391 Questions

    $124.99
    exam =35
  • exam =37
    Associate Cloud Engineer Video Course

    Training Course

    234 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    849 PDF Pages

    $29.99

Google Associate Cloud Engineer Practice Test 39

Question 380

Two Kubernetes namespaces use the same short service account name, but they must receive different Google Cloud resource permissions through GKE Workload Identity Federation. Which identity detail lets IAM distinguish them?

  1. Assume every service account named default is one global identity.
  2. Use only a VM network tag to distinguish IAM principals.
  3. Change the project's Cloud Billing currency.
  4. Use the namespaced Kubernetes service account principal identity, including the cluster and namespace context.

Explanation

Correct Answer

D:

GKE federation principal identifiers distinguish Kubernetes identities by namespace and other trust scope rather than the short name alone.

Incorrect Answers

A:

Kubernetes service accounts are scoped within namespaces and clusters.

B:

Network tags do not encode Kubernetes service account identity for IAM.

C:

Payer currency does not identify a workload principal.

Question 381

A GKE application uses Workload Identity Federation and a Google Cloud service supports IAM grants directly to the Kubernetes workload principal. The platform team wants to avoid an extra impersonation hop. Which model should it use?

  1. Always create and download an IAM service account key for every Pod.
  2. Grant all permissions to the entire cluster's node service account.
  3. Bind the supported resource IAM role directly to the GKE workload principal identity.
  4. Use Cloud DNS aliases as IAM principal names.

Explanation

Correct Answer

C:

Direct federation grants can authorize eligible Kubernetes principals without requiring them to impersonate a separate IAM service account.

Incorrect Answers

A:

Key files are not necessary for supported direct federation and increase secret-handling risk.

B:

Broad node identity permissions erase separation among different Pods.

D:

DNS records cannot substitute for a workload identity member string.

Question 382

A GKE application requires compatibility with a Google Cloud service that does not accept a direct GKE principal grant. The team will use IAM service account impersonation through workload identity. Which relationship must be configured?

  1. Set the Pod's Cloud Billing label to the IAM service account name.
  2. Allow the named Kubernetes service account to impersonate the target IAM service account through the supported workload identity binding.
  3. Put an IAM service account private key in a public bucket.
  4. Add a VPC firewall rule for the IAM service account email address.

Explanation

Correct Answer

B:

Workload identity impersonation maps a Kubernetes principal to an IAM service account with the required permissions.

Incorrect Answers

A:

Billing labels do not authorize the federation impersonation path.

C:

Publishing keys is insecure and unrelated to the keyless binding.

D:

Firewall rules do not implement workload identity principal impersonation.

Question 383

A Compute Engine VM's attached service account has a required Storage IAM role, but OAuth-based API calls still fail due to the VM's restrictive access scopes. What additional configuration must be examined?

  1. The VM's OAuth access scopes in addition to its service account IAM permissions.
  2. Only the project display name.
  3. The Cloud Billing budget's alert percentages.
  4. Cloud DNS MX records for the service account.

Explanation

Correct Answer

A:

Compute Engine access scopes can further restrict token capability even when the attached service account has appropriate IAM grants.

Incorrect Answers

B:

Cosmetic resource metadata cannot increase an OAuth scope.

C:

Financial thresholds do not change VM metadata token scopes.

D:

Mail DNS records have no OAuth scope effect.

Question 384

An administrator can select VM access scopes for a user-managed service account. They want IAM policies to control which Google Cloud APIs the VM may use while minimizing scope-related failures. Which recommended scope strategy fits?

  1. Give the service account basic Owner to make scopes irrelevant.
  2. Restrict scopes to a product the workload never calls.
  3. Publish the VM's service account token to DNS.
  4. Use the broad cloud-platform OAuth scope where appropriate and enforce least privilege with the service account's IAM roles.

Explanation

Correct Answer

D:

The cloud-platform scope avoids unnecessarily constraining eligible APIs while IAM determines which resources and methods the workload can access.

Incorrect Answers

A:

Owner grants excessive IAM permissions and does not justify ignoring scope or policy.

B:

An unrelated narrow scope could block required API access.

C:

DNS publication is insecure and cannot fix API authorization design.

Question 385

Security detects that a user-managed service account key has been copied into a public repository. The workload can transition to a managed keyless identity. What is the appropriate immediate credential response?

  1. Rename the exposed key file in the repository without disabling the credential.
  2. Delete the public repository commit but leave the leaked service account key active.
  3. Revoke or disable the exposed key, replace the workload authentication mechanism, and investigate use.
  4. Rotate the key by generating a second static key while keeping the compromised one active indefinitely.

Explanation

Correct Answer

C:

A leaked private key is reusable until invalidated, so revocation and keyless migration address both exposure and future risk.

Incorrect Answers

A:

A renamed credential is still valid if copied by an attacker; key revocation or disablement is needed to stop its use.

B:

Once exposed, the key may already have been copied; deleting a commit does not invalidate an active private key.

D:

Adding a new key does not contain the compromised credential; the exposed key must be disabled or revoked and usage investigated.

Question 386

A user-managed service account JSON private key has been stored in a legacy application for years. A team assumes Google automatically rotates every such downloaded key once a month. What should they change in their operational plan?

  1. Assume the key is always replaced by Google without application changes.
  2. Treat user-managed keys as long-lived until explicitly managed and rotate or eliminate them under a controlled lifecycle.
  3. Increase the storage bucket retrieval quota.
  4. Change the service account display name to cause key rotation.

Explanation

Correct Answer

B:

Downloaded user-managed keys are not automatically rotated merely because time passes, so owners must govern replacement and revocation.

Incorrect Answers

A:

Applications would not automatically receive a new downloaded private key from such an assumption.

C:

Increasing Cloud Storage retrieval quota affects eligible data access limits but has no effect on the private key lifecycle of a service account.

D:

Display-name changes do not replace private key material.

Question 387

A dormant user-managed service account unexpectedly calls APIs. Investigators need to stop its use temporarily while preserving its identity and existing policy bindings for review. Which management action fits?

  1. Disable the service account pending investigation.
  2. Change only the account display name to disabled.
  3. Delete the entire cloud organization.
  4. Add a Cloud Billing budget named suspicious.

Explanation

Correct Answer

A:

Disabling blocks use of the service account without immediately deleting the identity and its administrative history.

Incorrect Answers

B:

A display name does not suspend token authorization.

C:

Organization deletion is disproportionate and destroys unrelated resources.

D:

Financial metadata cannot disable a service account principal.

Question 388

A service account was deleted accidentally yesterday, and it is within the documented undelete window. The team needs to restore that same identity rather than create a new one with a matching display name. What should an authorized administrator attempt?

  1. Create a fresh service account with the same display name and assume it has the identical unique identity.
  2. Change the project's billing account to its previous payer.
  3. Create a DNS record for the deleted email.
  4. Undelete the original service account using its unique identifier within the supported recovery window.

Explanation

Correct Answer

D:

Restoring the deleted identity can preserve the original unique principal continuity when recovery is still available.

Incorrect Answers

A:

Re-creating an account yields a new unique identity even if an email/name is reused under allowed rules.

B:

Cloud Billing linkage determines the payer, not the lifecycle of a deleted service-account principal that must be recovered by its unique ID.

C:

A DNS record is not an IAM account restoration action.

Question 389

An IAM engineer sees a service account but needs to find which resource permissions it actually has, including project-scoped grants that might affect a bucket. What must be inspected?

  1. Only the service account's description field.
  2. The Cloud Billing account payment methods.
  3. The relevant resource IAM policies, including inherited bindings, for that service account principal.
  4. A DNS reverse lookup on the service account email.

Explanation

Correct Answer

C:

A service account receives permissions through allow policies on target resources and their ancestors, not from its display name alone.

Incorrect Answers

A:

A description is metadata and does not list all effective resource grants.

B:

Payment instruments cannot reveal API permissions granted to a workload.

D:

DNS has no authority over Google Cloud resource IAM bindings.

Question 390

A service account created in project A must read an approved BigQuery dataset in project B, and cross-project principal grants are allowed by policy. Where should the data authorization be attached?

  1. Give the service account Project Owner in project A only.
  2. Grant the service account an appropriate dataset-scoped role in project B, with separate query-job permission where necessary.
  3. Change the two project display names to match.
  4. Put the dataset name in the service account key file.

Explanation

Correct Answer

B:

IAM identity creation project and target resource project may differ; resource policies in B decide access to its data.

Incorrect Answers

A:

Ownership in A does not automatically authorize access to a protected dataset in B.

C:

Matching display names across projects does not merge their IAM policies; the service account must receive appropriate access on the target dataset.

D:

Credential file content cannot replace target-resource IAM grants.