← ACE·Google Cloud

Question 67 of 500

Deploying and implementing a cloud solution →mediumMultiple ChoiceObjective-mapped

Quick Answer

The correct approach is to use built-in substitutions like `$PROJECT_ID` and `$COMMIT_SHA` for automatically resolved values, and define custom substitutions such as `$_REGION` in the trigger or via the `--substitutions` flag. This works because Cloud Build’s built-in substitutions pull environment-specific data directly from the build context—`$PROJECT_ID` resolves to the current GCP project and `$COMMIT_SHA` to the Git commit SHA—while custom substitutions prefixed with `$_` let you inject variable values like region or image tag without hardcoding them in `cloudbuild.yaml`. On the Google Associate Cloud Engineer exam, this tests your understanding of how to keep build configurations portable and secure; a common trap is trying to define `$PROJECT_ID` as a custom substitution or hardcoding `$_REGION` directly in the YAML file. Remember the mnemonic: built-in for automatic, custom with underscore for environment-specific—let Cloud Build fill the blanks.

Google ACE Deploying and implementing a cloud solution Practice Question

This ACE practice question tests your understanding of deploying and implementing a cloud solution. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Your Cloud Build pipeline needs to reference environment-specific configuration: `PROJECT_ID`, `REGION`, and `IMAGE_TAG` (generated from the Git commit SHA). Where should you define these values in `cloudbuild.yaml`?

Question 1mediummultiple choice

Full question →

A
Hardcode the values directly in each build step's `args` field.
Why wrong: Hardcoding values makes the pipeline environment-specific and non-reusable. Different environments (dev, prod) would require different cloudbuild.yaml files.
B
Use built-in substitutions (`$PROJECT_ID`, `$COMMIT_SHA`) and define custom substitutions (`$_REGION`) in the trigger or `--substitutions` flag.
$PROJECT_ID and $COMMIT_SHA are Cloud Build built-in substitutions. Custom values like REGION use the $_VAR pattern defined in trigger configuration, enabling environment-specific pipelines from a single cloudbuild.yaml.
C
Store all values in Cloud Secret Manager and retrieve them in each build step.
Why wrong: Secret Manager is for sensitive secrets (passwords, keys), not for non-sensitive configuration like region or project ID. Using it for all config adds unnecessary complexity.
D
Use a `.env` file committed to the repository and source it in build steps.
Why wrong: Environment-specific `.env` files shouldn't be committed to the repository (especially with any sensitive values). Built-in and custom substitutions are the Cloud Build native approach.

Full breakdown with real-world context →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Use built-in substitutions (`$PROJECT_ID`, `$COMMIT_SHA`) and define custom substitutions (`$_REGION`) in the trigger or `--substitutions` flag.

Option B is correct because Cloud Build provides built-in substitutions like `$PROJECT_ID` and `$COMMIT_SHA` that automatically resolve to the current project ID and the Git commit SHA, respectively. Custom substitutions like `$_REGION` can be defined in the trigger configuration or passed via the `--substitutions` flag, allowing environment-specific values to be injected without hardcoding. This approach keeps the `cloudbuild.yaml` reusable across environments and avoids exposing sensitive or variable data in the build file.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Hardcode the values directly in each build step's `args` field.
Why it's wrong here
Hardcoding values makes the pipeline environment-specific and non-reusable. Different environments (dev, prod) would require different cloudbuild.yaml files.
✓
Use built-in substitutions (`$PROJECT_ID`, `$COMMIT_SHA`) and define custom substitutions (`$_REGION`) in the trigger or `--substitutions` flag.
Why this is correct
$PROJECT_ID and $COMMIT_SHA are Cloud Build built-in substitutions. Custom values like REGION use the $_VAR pattern defined in trigger configuration, enabling environment-specific pipelines from a single cloudbuild.yaml.
Related concept
Read the scenario before looking for a memorised answer.
✗
Store all values in Cloud Secret Manager and retrieve them in each build step.
Why it's wrong here
Secret Manager is for sensitive secrets (passwords, keys), not for non-sensitive configuration like region or project ID. Using it for all config adds unnecessary complexity.
✗
Use a `.env` file committed to the repository and source it in build steps.
Why it's wrong here
Environment-specific `.env` files shouldn't be committed to the repository (especially with any sensitive values). Built-in and custom substitutions are the Cloud Build native approach.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Google Cloud often tests the distinction between built-in and custom substitutions, and the trap here is that candidates assume all environment-specific values must be hardcoded or stored in secrets, overlooking Cloud Build's native substitution mechanism for non-sensitive configuration.

Detailed technical explanation

How to think about this question

Under the hood, Cloud Build substitutions are resolved at build time using a simple text-replacement mechanism; built-in substitutions like `$COMMIT_SHA` are populated from the trigger event payload (e.g., from a GitHub push), while custom substitutions like `$_REGION` must be explicitly provided. A subtle behavior is that if a custom substitution is not defined in the trigger or `--substitutions` flag, Cloud Build will fail with an error, ensuring that missing configuration is caught early. In a real-world multi-environment pipeline (dev/staging/prod), using substitutions allows the same `cloudbuild.yaml` to deploy to different regions by simply changing the `$_REGION` value per trigger.

KKey Concepts to Remember

Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.

TExam Day Tips

Watch for words such as best, first, most likely and least administrative effort.
Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related ACE practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Setting up a cloud solution environment practice questions

Practise ACE questions linked to Setting up a cloud solution environment.

Planning and configuring a cloud solution practice questions

Practise ACE questions linked to Planning and configuring a cloud solution.

Deploying and implementing a cloud solution practice questions

Practise ACE questions linked to Deploying and implementing a cloud solution.

Ensuring successful operation of a cloud solution practice questions

Practise ACE questions linked to Ensuring successful operation of a cloud solution.

Configuring access and security practice questions

Practise ACE questions linked to Configuring access and security.

ACE fundamentals practice questions

Practise ACE questions linked to ACE fundamentals.

ACE scenario practice questions

Practise ACE questions linked to ACE scenario.

ACE troubleshooting practice questions

Practise ACE questions linked to ACE troubleshooting.

Practice this exam

Start a free ACE practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

10 questions 20 questions 30 questions 50 questions Timed 30

ACE practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this ACE question test?

Deploying and implementing a cloud solution — This question tests Deploying and implementing a cloud solution — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Use built-in substitutions (`$PROJECT_ID`, `$COMMIT_SHA`) and define custom substitutions (`$_REGION`) in the trigger or `--substitutions` flag. — Option B is correct because Cloud Build provides built-in substitutions like `$PROJECT_ID` and `$COMMIT_SHA` that automatically resolve to the current project ID and the Git commit SHA, respectively. Custom substitutions like `$_REGION` can be defined in the trigger configuration or passed via the `--substitutions` flag, allowing environment-specific values to be injected without hardcoding. This approach keeps the `cloudbuild.yaml` reusable across environments and avoids exposing sensitive or variable data in the build file.

What should I do if I get this ACE question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

This ACE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ACE exam.