The correct approach is to add a test step in Cloud Build that uses the built image to run integration tests before deploying to Cloud Run. This works because Cloud Build’s pipeline allows you to define sequential steps, so after the container image is built and pushed to Artifact Registry, you can insert a step that runs that exact image with your integration test suite—often using a test runner like pytest inside a Cloud Build custom step or a cloud-run-jobs-like container. This validates your application in an environment identical to production, catching issues like missing dependencies or configuration errors early, which is the essence of shift-left testing. On the Google Professional Cloud Developer exam, this scenario tests your understanding of Cloud Build’s step orchestration and the principle that tests should run on the built artifact, not on source code alone. A common trap is to run unit tests before the image build, which misses integration issues, or to deploy first and test later, which defeats the purpose of CI/CD safety. Memory tip: “Build, Test, Deploy” in that order—the test step must use the built image, not the source.
PCD Building and testing applications Practice Question
This PCD practice question tests your understanding of building and testing applications. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
A team wants to implement automated testing for a Python application deployed on Cloud Run. They want the tests to run as part of the CI/CD pipeline after the image is built but before it is deployed. Which approach should they use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Add a test step in Cloud Build that uses the built image to run integration tests before deploying
Option C is correct because Cloud Build allows you to add a test step that runs the built container image before deploying it to Cloud Run. This ensures integration tests validate the application in an environment identical to production, catching issues early in the CI/CD pipeline. Running tests after the image is built but before deployment is a standard practice for shift-left testing.
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.
✗
Use Cloud Function to run tests triggered by a Pub/Sub message after the image is published
Why it's wrong here
This adds complexity and may not have the built image available.
✗
Run unit tests before building the image using Cloud Build, but skip integration tests
Why it's wrong here
Integration tests should be run after build but before deploy.
✓
Add a test step in Cloud Build that uses the built image to run integration tests before deploying
Why this is correct
Cloud Build allows running containers from the built image as part of the pipeline.
Related concept
Read the scenario before looking for a memorised answer.
✗
Deploy the image to a staging environment, run tests, and then promote to production
Why it's wrong here
This deploys before testing, which is not the desired order.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that integration tests must be run in a separate staging environment or after deployment, when in fact Cloud Build can run them directly from the built image before deployment.
Detailed technical explanation
How to think about this question
Cloud Build supports running custom test steps using the same container image that will be deployed, enabling integration tests against services like Cloud SQL or Redis via environment variables and service accounts. Under the hood, Cloud Build executes each step in a Docker container, and the built image can be referenced by its tag (e.g., `gcr.io/$PROJECT_ID/my-image:latest`) in subsequent steps. This approach avoids the overhead of a separate staging deployment and ensures the test environment matches production exactly, including the base image and dependencies.
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.
Building and testing applications — This question tests Building and testing applications — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Add a test step in Cloud Build that uses the built image to run integration tests before deploying — Option C is correct because Cloud Build allows you to add a test step that runs the built container image before deploying it to Cloud Run. This ensures integration tests validate the application in an environment identical to production, catching issues early in the CI/CD pipeline. Running tests after the image is built but before deployment is a standard practice for shift-left testing.
What should I do if I get this PCD 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 →
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.
This PCD 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 PCD exam.
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.
Sign in to join the discussion.