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 40

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.

Question 391

A Compute Engine VM in project B must use a user-managed service account owned by project A. Administrators have verified IAM actAs grants, but an organizational policy blocks cross-project service account attachment. What else must be considered?

  1. Review the cross-project service account usage Organization Policy and permitted exceptions before attempting attachment.
  2. Add the service account email as a Cloud DNS A record.
  3. Increase project B's VM memory quota.
  4. Put the service account into a Billing budget.

Explanation

Correct Answer

A:

Project-crossing service account attachment is subject to organizational constraints in addition to the usual actor permissions.

Incorrect Answers

B:

DNS records cannot override an organization-level IAM attachment constraint.

C:

Quota does not lift a service account cross-project policy.

D:

Financial metadata does not grant permission to attach a service account across projects; the relevant Organization Policy constraint controls that boundary.

Question 392

An internal Cloud Run sender service calls a private receiver Cloud Run service using a signed identity token. Which receiver-side IAM binding determines whether that particular sender is authorized?

  1. Grant the sender Storage Object Viewer on an unrelated bucket.
  2. Change only the sender's Cloud Billing budget.
  3. Set the receiver DNS TTL to zero.
  4. Grant the receiver's Cloud Run Invoker role to the sender's runtime service account at the receiver service.

Explanation

Correct Answer

D:

The receiving service evaluates the authenticated caller principal against its invoker authorization policy.

Incorrect Answers

A:

Bucket data access does not authorize the receiver's HTTP invocation.

B:

Billing amount does not grant request invocation rights.

C:

DNS caching does not decide Cloud Run invoker authorization.

Question 393

A legacy integration requires a signed JSON Web Token assertion created by an authorized service account, not an OAuth access token for a Google API. Which IAM Credentials method is relevant when supported?

  1. Use a Cloud Billing invoice as the JWT signature.
  2. Pass the service account display name as a complete signed token.
  3. Use the service account signJwt capability through authorized IAM Credentials access.
  4. Put the JWT payload in public DNS and rely on DNSSEC to sign it as an IAM assertion.

Explanation

Correct Answer

C:

The signJwt operation signs a supplied token payload with Google-managed service account key material for the eligible JWT workflow.

Incorrect Answers

A:

Invoice documents have no cryptographic relationship to service account JWT signing.

B:

A principal name is not a cryptographically signed JWT.

D:

DNSSEC validates DNS answers rather than producing a service account JWT.

Question 394

A backend needs to sign an application-defined byte sequence using authorized service account signing without exporting its private key, for an integration that verifies Google-managed signatures. Which credential operation should it evaluate?

  1. Call generateAccessToken with the target service account and treat the OAuth token as a signature over the arbitrary bytes.
  2. The IAM Credentials signBlob method under the required Token Creator-style permissions.
  3. Call signJwt with claims encoded as an application-defined raw byte stream.
  4. Export the service account’s private key and sign locally in the application.

Explanation

Correct Answer

B:

signBlob signs arbitrary bytes with managed service account key material without distributing the service account private key.

Incorrect Answers

A:

OAuth access tokens authorize API calls; they are not signatures of the application-defined payload returned by the signBlob operation.

C:

signJwt signs a structured JWT claim set, whereas signBlob provides a cryptographic signature over the arbitrary bytes requested.

D:

The scenario explicitly prohibits exporting the key; IAM Credentials signBlob signs the provided bytes without sharing that private material.

Question 395

An automation identity requires the ability to impersonate exactly one deployment service account and no others in the organization. What is the appropriate grant placement?

  1. Bind the required token-creation role on that single target service account, not at the organization root.
  2. Grant Service Account Token Creator at the entire organization.
  3. Give the automation a project label named deployer.
  4. Create a shared service account key usable for all projects.

Explanation

Correct Answer

A:

IAM resource scoping can limit which identity the caller may impersonate and reduce unnecessary lateral access.

Incorrect Answers

B:

Organization-wide authority could allow impersonation of many unrelated identities.

C:

Adding a descriptive project label does not change which target service accounts allow the caller to mint impersonation tokens.

D:

A reusable key expands credential reach rather than narrowing it.

Question 396

A Compute Engine application uses Application Default Credentials but no credential JSON file exists on disk. Its attached service account is authorized. How does the application normally obtain usable Google Cloud tokens?

  1. Read the service account email from VM metadata and use that email address directly as a bearer token.
  2. Run an interactive gcloud auth login every time the VM application starts.
  3. Load a user-managed JSON key from the VM’s boot image even though none is provisioned.
  4. Through the Compute Engine metadata server for the attached service account.

Explanation

Correct Answer

D:

The metadata server provides short-lived credentials to eligible guest workloads using the assigned service identity.

Incorrect Answers

A:

A service account email identifies a principal but is not a credential; ADC obtains actual short-lived tokens from the metadata service.

B:

Attached service account ADC does not require an interactive human login; the metadata server supplies scoped workload credentials.

C:

The premise says no key file exists, and attaching a service account enables a keyless metadata token flow instead.

Question 397

Security wants to identify user-managed service account keys that remain active across a project so it can plan keyless migration and detect stale secrets. Which IAM inventory should be reviewed?

  1. Search only Cloud Storage object labels.
  2. Read the latest Cloud Billing invoice.
  3. Enumerate user-managed keys for the project's service accounts and inspect their status and creation metadata.
  4. Inspect VM startup logs instead of IAM key inventory.

Explanation

Correct Answer

C:

Service account key inventory identifies credential material requiring lifecycle governance without assuming all workload keys are managed by Google.

Incorrect Answers

A:

Bucket metadata cannot enumerate IAM key resources across service accounts.

B:

An invoice does not list credential keys and their ages.

D:

Guest logs are not an authoritative list of service account key resources.

Question 398

A company wants its external workforce members to sign in to Google Cloud with corporate identity-provider credentials, not use nonhuman CI workload assertions. Which federation family is designed for human users?

  1. Workload Identity Federation configured as a shared human password vault.
  2. Workforce Identity Federation using the corporate workforce identity provider.
  3. A permanent project Owner account shared by every worker.
  4. Public DNS authentication with email aliases only.

Explanation

Correct Answer

B:

Workforce federation is intended for external human users, whereas Workload Identity Federation addresses nonhuman workloads.

Incorrect Answers

A:

Workload federation is not the human workforce sign-in model or a password vault.

C:

One permanent Owner identity shared by employees would remove individual attribution and distribute excessive administrative privileges across the workforce.

D:

DNS aliases are not a federated Google Cloud workforce authentication process.

Question 399

An external OIDC issuer can sign tokens for many repositories, but only tokens from one trusted automation repository should exchange for Google Cloud credentials. Which federation-side control narrows the trust?

  1. Configure the workload identity provider's supported attribute mapping and condition to accept only the intended repository identity.
  2. Trust every token from the external issuer without subject restrictions.
  3. Put the repository name in a billing account label.
  4. Add a public DNS TXT record with the repository name.

Explanation

Correct Answer

A:

Provider attribute conditions can restrict which external token subjects are eligible for exchange before downstream IAM grants are evaluated.

Incorrect Answers

B:

Broad issuer trust can grant unintended repositories access if IAM mappings are also broad.

C:

Financial metadata does not constrain federated OIDC identities.

D:

DNS publication is not a token attribute policy.

Question 400

A workload identity OIDC token is validly signed by its issuer, but credential exchange rejects it due to an audience mismatch. What configuration dimension needs to agree?

  1. Match only the OIDC token issuer URL while ignoring its aud claim.
  2. Increase the service account’s token-creation IAM permissions without changing audience configuration.
  3. Change the OIDC token subject claim to the Cloud project ID without correcting the configured audience.
  4. The token's intended audience and the workload identity provider's configured allowed audience settings.

Explanation

Correct Answer

D:

Token exchange validates more than signature; the accepted audience must match the provider's trust configuration.

Incorrect Answers

A:

A trusted issuer signature is insufficient; audience validation ensures the token was intended for this workload identity provider.

B:

IAM grants do not turn an incorrectly targeted external OIDC assertion into one whose audience the provider accepts.

C:

Subject identifies the workload principal; an audience mismatch remains until the token’s aud value satisfies the provider’s accepted audience rules.