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 38

Question 370

A platform engineer is authorized to impersonate a least-privilege deployment service account. They want a single gcloud deployment command to use that identity without switching permanently to a service account key file. Which CLI approach fits?

  1. Copy a long-lived JSON private key into shell history.
  2. Use the gcloud --impersonate-service-account flag for the command with the necessary target-account permission.
  3. Change the default project name to the service account email.
  4. Add a Cloud Billing label called impersonation.

Explanation

Correct Answer

B:

gcloud can mint temporary credentials for the specified identity for that invocation without persistent exported keys.

Incorrect Answers

A:

That distributes a reusable credential and defeats keyless impersonation.

C:

Project context does not select the caller identity.

D:

A Cloud Billing label is financial reporting metadata and does not instruct gcloud to mint credentials for a target service account.

Question 371

A trusted workload needs to call a Google Cloud API that accepts OAuth 2.0 access tokens. It must use short-lived service account credentials obtained through an authorized identity workflow. Which token type is appropriate?

  1. Generate an OAuth access token for the target service account through the supported IAM Credentials API.
  2. Use a public DNS A record as the bearer token.
  3. Send the service account display name as the HTTP Authorization bearer value.
  4. Use a Billing Account ID as an access token.

Explanation

Correct Answer

A:

OAuth access tokens authorize calls to Google Cloud APIs and can be short-lived when minted through managed credentials.

Incorrect Answers

B:

A DNS address is not an OAuth credential.

C:

A name alone does not authenticate the API caller.

D:

A Billing Account ID identifies the payer and cannot authenticate OAuth requests or be exchanged for access credentials.

Question 372

A scheduled job must invoke a private Cloud Run HTTPS endpoint that validates a caller identity token for a specific service URL. Which service account token type and claim are relevant?

  1. Use only an arbitrary OAuth access token with no consideration of audience.
  2. Put the service URL in a Cloud Billing budget name.
  3. Use a Cloud DNS TXT record as the caller's signature.
  4. Generate a signed OIDC ID token with the correct target audience for the service.

Explanation

Correct Answer

D:

Cloud Run authenticated HTTP invocation commonly uses an ID token whose audience identifies the intended recipient, rather than a generic OAuth API scope.

Incorrect Answers

A:

An access token for Google API methods is not automatically an appropriate audience-bound OIDC invocation token.

B:

Cloud Billing budget names are financial metadata and cannot set signed OIDC identity token audience claims for Cloud Run.

C:

DNS responses do not provide an OIDC signed identity assertion.

Question 373

Security investigators observe API activity attributed to a deployment service account but need to identify which authorized human or workload impersonated it. Which evidence should they correlate?

  1. Inspect the target service account’s IAM role grants only.
  2. Read the service account’s display name and metadata labels as the impersonator identity.
  3. Relevant IAM Credentials and target API audit logs, including delegation information when available.
  4. Inspect only the current access token’s expiry time.

Explanation

Correct Answer

C:

Impersonated requests can carry principal and delegation metadata, enabling attribution beyond the final service account identity.

Incorrect Answers

A:

Role bindings describe which principals can receive permissions, not which identity actually impersonated the account in a particular API call.

B:

Names and labels are descriptive metadata; API audit-log delegation fields are needed to attribute an observed impersonated call.

D:

Token lifetime alone cannot identify which human or workload obtained the credential; audit delegation records can supply that provenance.

Question 374

An external deployment process uses an OAuth access token minted for a service account. The token works initially but fails after its expiration time even though the IAM binding remains. What is the correct remedy?

  1. Change the service account display name to refresh the token.
  2. Obtain a fresh authorized short-lived token rather than assuming the previous token remains valid indefinitely.
  3. Increase the Cloud Billing budget.
  4. Open an ingress firewall port on the application database.

Explanation

Correct Answer

B:

Access tokens have finite lifetimes and must be renewed through a supported credential flow.

Incorrect Answers

A:

Display names do not alter token expiry claims.

C:

A billing threshold can notify about spending but cannot extend the cryptographically bounded expiration of an issued OAuth access token.

D:

Network changes cannot renew an expired identity credential.

Question 375

A Compute Engine VM already has a dedicated service account with Storage Object Admin on one bucket. A client library running on the VM can read objects but receives an insufficient authentication scope error when uploading them. The VM was created with only the Cloud Storage read-only OAuth scope. What should the operator correct?

  1. Use a suitable cloud-platform OAuth access scope on the VM while retaining least-privilege bucket IAM for the attached service account.
  2. Grant Storage Admin to the same service account at the project level without changing VM access scopes.
  3. Grant the VM operator iam.serviceAccounts.actAs again without changing the running VM credentials.
  4. Make the storage bucket publicly writable so the VM does not need its current scope.

Explanation

Correct Answer

A:

The read-only OAuth scope prevents this client from obtaining authorization for object writes even though the identity has Storage Object Admin; a compatible scope removes that extra restriction.

Incorrect Answers

B:

Broader IAM rights do not overcome the VM’s restrictive OAuth scope; they would also extend object permissions beyond the named bucket.

C:

The VM already has its service account attached; actAs governs attachment, not the OAuth scope of the client library token used for uploads.

D:

Anonymous writes would expose the bucket and bypass the intended service-account access model rather than correct the client’s restricted OAuth scope.

Question 376

A Cloud Run application must call the Cloud Storage API using an assigned least-privilege workload identity. The deployment operator has their own human role, but application calls need a separate identity. What should the deployment specify?

  1. Rely on the human deployer's Owner role for every application request.
  2. Put the service account email in a public DNS record.
  3. Copy a static human password into the container image.
  4. Configure the intended user-managed service account as the Cloud Run service identity and grant that account the required storage role.

Explanation

Correct Answer

D:

Cloud Run containers can use the configured runtime service account for ADC/API calls independently of the deployer's principal.

Incorrect Answers

A:

Deployment authorization is not the intended runtime workload identity or least-privilege mechanism.

B:

DNS does not configure Cloud Run service identity.

C:

Embedded credentials are insecure and unrelated to managed runtime identity.

Question 377

A Cloud Run job downloads restricted records during each execution. A developer can start the job, but the code needs its own permitted data-access identity. Which principal must be given the dataset access?

  1. Every user who can view the job's Cloud Billing charges.
  2. The public DNS zone administrator.
  3. The job's configured execution service account used by its container tasks.
  4. The developer's personal project Owner role, assuming it transfers to the job.

Explanation

Correct Answer

C:

Runtime API calls originate from the job's service identity, not automatically from the human who started the job.

Incorrect Answers

A:

Billing viewers are not the runtime execution principals.

B:

DNS management does not authenticate a Cloud Run job's data calls.

D:

Human permissions do not automatically become the job's workload permissions.

Question 378

An event-triggered Cloud Run function is invoked successfully but fails when reading a private bucket during execution. The trigger has permission to deliver events. Which identity needs the read access?

  1. The event producer's billing account.
  2. The function's runtime service account, separately from event-delivery/trigger identities.
  3. The Cloud DNS public zone.
  4. The human who originally clicked Deploy, with no runtime change.

Explanation

Correct Answer

B:

Delivery authorization and the running function's API permissions are distinct identity boundaries.

Incorrect Answers

A:

Payer account identity does not grant the function's runtime storage read permission.

C:

Zone permissions cannot access bucket objects on behalf of function code.

D:

A deployer's personal IAM grants are not automatically inherited by the function container.

Question 379

A GKE application needs to read a private Google Cloud resource without shipping JSON service-account keys into Pod Secrets. Which native workload-authentication architecture is recommended where supported?

  1. Configure Workload Identity Federation for GKE and grant the Pod workload identity least-privilege resource access.
  2. Create a user-managed service account key and mount it in a private Kubernetes Secret.
  3. Grant the GKE node service account Project Owner so every Pod inherits broad permissions.
  4. Use a Kubernetes ServiceAccount without configuring workload identity or resource IAM.

Explanation

Correct Answer

A:

GKE workload identity can provide keyless workload credentials tied to Kubernetes identities for supported Google Cloud APIs.

Incorrect Answers

B:

Even a restricted Secret still distributes a long-lived JSON key, violating the explicit keyless workload identity requirement.

C:

Node-wide ownership overprivileges all workloads and does not establish per-Pod least-privilege workload identity.

D:

A Kubernetes ServiceAccount identifies a Pod to Kubernetes, but by itself does not grant Google Cloud API permissions through federation.

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.