- A
Incorrect image name/tag, or missing pull credentials for a private registry.
These are the two root causes: wrong image reference (404 from registry) or authentication failure (403 from registry). Both result in ImagePullBackOff.
- B
Insufficient CPU/memory on the node, or the pod's resource requests are too high.
Why wrong: Resource insufficiency causes pods to remain in Pending state, not ImagePullBackOff. ImagePullBackOff is specifically a registry/image problem.
- C
The pod's liveness probe is failing, causing the container to restart.
Why wrong: Liveness probe failures cause CrashLoopBackOff (after restarts), not ImagePullBackOff. The image must first be pulled successfully for liveness probes to run.
- D
The container's entrypoint command is failing, causing the image pull to abort.
Why wrong: Entrypoint failures happen after image pull succeeds — they result in CrashLoopBackOff, not ImagePullBackOff.
Common Causes of ImagePullBackOff in Kubernetes
This ACE practice question tests your understanding of ace exam topics. 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.
You run `kubectl get pods` and see a pod in `ImagePullBackOff` state. What are the two most common causes of this error?
Quick Answer
The answer is an incorrect image name or tag and missing pull credentials for a private registry. The ImagePullBackOff state occurs when the kubelet fails to pull the container image, entering a retry loop with increasing backoff delays. An incorrect name or tag—such as a typo or a non-existent version—returns a 404 from the registry, while missing or invalid credentials for a private registry return a 401 or 403, both preventing the image download. On the Google Associate Cloud Engineer exam, this tests your understanding of pod lifecycle and registry authentication, often appearing in troubleshooting scenarios where a pod never reaches Running. A common trap is assuming the image exists locally or that public registries never require authentication. For a quick memory tip, think “404 for name, 401 for auth”—if you see ImagePullBackOff, check the image string first, then your secrets.
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
Incorrect image name/tag, or missing pull credentials for a private registry.
The `ImagePullBackOff` state indicates that the kubelet is unable to pull the container image from the registry. The two most common causes are an incorrect image name or tag (e.g., a typo or a non-existent tag), which results in a `404 Not Found` from the registry, and missing or invalid pull credentials for a private registry, which results in a `401 Unauthorized` or `403 Forbidden` response. Both prevent the image from being downloaded, causing the pod to enter a backoff loop.
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.
- ✓
Incorrect image name/tag, or missing pull credentials for a private registry.
Why this is correct
These are the two root causes: wrong image reference (404 from registry) or authentication failure (403 from registry). Both result in ImagePullBackOff.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Insufficient CPU/memory on the node, or the pod's resource requests are too high.
Why it's wrong here
Resource insufficiency causes pods to remain in Pending state, not ImagePullBackOff. ImagePullBackOff is specifically a registry/image problem.
- ✗
The pod's liveness probe is failing, causing the container to restart.
Why it's wrong here
Liveness probe failures cause CrashLoopBackOff (after restarts), not ImagePullBackOff. The image must first be pulled successfully for liveness probes to run.
- ✗
The container's entrypoint command is failing, causing the image pull to abort.
Why it's wrong here
Entrypoint failures happen after image pull succeeds — they result in CrashLoopBackOff, not ImagePullBackOff.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the distinction between `ImagePullBackOff` (image retrieval failure) and `CrashLoopBackOff` (container runtime failure) — candidates confuse the two because both involve backoff logic, but the root cause and timing differ.
Detailed technical explanation
How to think about this question
Under the hood, when a pod is scheduled, the kubelet instructs the container runtime (e.g., containerd or CRI-O) to pull the image. The runtime sends an HTTP request to the registry (e.g., Docker Hub, GCR, ECR) and interprets the response status code. A `401` or `403` triggers a retry with backoff, but if credentials are missing or incorrect, the pull fails permanently. Similarly, a `404` for a non-existent image tag causes the same backoff loop. The backoff duration doubles each attempt (starting at 300ms up to 5 minutes) and resets after a successful pull.
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 practice questions
Related ACE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Configuring Access and Security practice questions
Practise ACE questions linked to Configuring Access and Security.
Planning and Configuring a Cloud Solution practice questions
Practise ACE questions linked to Planning and Configuring a Cloud Solution.
Ensuring Successful Operation of a Cloud Solution practice questions
Practise ACE questions linked to Ensuring Successful Operation of a Cloud Solution.
Deploying and Implementing a Cloud Solution practice questions
Practise ACE questions linked to Deploying and Implementing a Cloud Solution.
Setting Up a Cloud Solution Environment practice questions
Practise ACE questions linked to Setting Up a Cloud Solution Environment.
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.
FAQ
Questions learners often ask
What does this ACE question test?
Read the scenario before looking for a memorised answer.
What is the correct answer to this question?
The correct answer is: Incorrect image name/tag, or missing pull credentials for a private registry. — The `ImagePullBackOff` state indicates that the kubelet is unable to pull the container image from the registry. The two most common causes are an incorrect image name or tag (e.g., a typo or a non-existent tag), which results in a `404 Not Found` from the registry, and missing or invalid pull credentials for a private registry, which results in a `401 Unauthorized` or `403 Forbidden` response. Both prevent the image from being downloaded, causing the pod to enter a backoff loop.
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 →
Keep practising
More ACE practice questions
- A team's Cloud Build pipeline must: (1) run unit tests, (2) build a Docker image only if tests pass, (3) push the image…
- A team needs a database backup job to run every day at 2 AM UTC. The job calls an HTTP endpoint to trigger the backup. T…
- A team wants to receive an email alert when the average CPU utilization of VMs in a managed instance group exceeds 80% f…
- A Go service is consuming significantly more CPU than expected. The team suspects an inefficient function but doesn't kn…
- A network team is creating a new VPC and must decide between auto mode and custom mode. Why would they choose custom mod…
- A company organizes its GCP projects by business unit — Finance, Engineering, and Sales. Which resource is best suited t…
Last reviewed: Jun 30, 2026
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.
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.