Courseiva
← PCD
Full test
Question 247 of 999
Deploying applications →easyMultiple ChoiceObjective-mapped

Why New Pods Fail to Start During Rolling Updates: Resource Requests

This PCD practice question tests your understanding of deploying applications. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.

Exhibit

Refer to the exhibit.
```
{
  "name": "my-deployment",
  "replicas": 3,
  "template": {
    "spec": {
      "containers": [{
        "name": "my-container",
        "image": "gcr.io/my-project/my-image:latest",
        "resources": {
          "requests": {
            "memory": "1Gi",
            "cpu": "500m"
          },
          "limits": {
            "memory": "2Gi",
            "cpu": "1"
          }
        }
      }]
    }
  },
  "strategy": {
    "type": "RollingUpdate",
    "rollingUpdate": {
      "maxSurge": 1,
      "maxUnavailable": 1
    }
  }
}
```

During a rolling update, the new pods are failing to start because they require more memory than available on nodes. What is the most likely cause?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "most likely"

    Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

Exhibit

Refer to the exhibit.
```
{
  "name": "my-deployment",
  "replicas": 3,
  "template": {
    "spec": {
      "containers": [{
        "name": "my-container",
        "image": "gcr.io/my-project/my-image:latest",
        "resources": {
          "requests": {
            "memory": "1Gi",
            "cpu": "500m"
          },
          "limits": {
            "memory": "2Gi",
            "cpu": "1"
          }
        }
      }]
    }
  },
  "strategy": {
    "type": "RollingUpdate",
    "rollingUpdate": {
      "maxSurge": 1,
      "maxUnavailable": 1
    }
  }
}
```

Quick Answer

The answer is that misconfigured resource requests and limits are the most likely cause of new pods failing to start during a rolling update. This happens because Kubernetes uses the resource requests field to determine node capacity; if a new pod requests 1Gi of memory but no node has that much unallocated memory after accounting for existing pods, the scheduler will leave the pod in a Pending state. On the Google Professional Cloud Developer exam, this scenario tests your understanding of how the scheduler evaluates node resources versus pod requests, often hiding the trap that limits alone do not affect scheduling—only requests do. A common mistake is confusing limits with requests, so remember the mnemonic: Requests Reserve, Limits Limit.

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

✓

The resource requests and limits are misconfigured.

Option B is correct because the most likely cause of pods failing to start due to insufficient memory is misconfigured resource requests and limits. If the memory request (spec.containers[].resources.requests.memory) is set too high, the scheduler cannot find a node with enough allocatable memory, leaving pods in a Pending state. Similarly, if the limit is set too low, the pod may be OOMKilled after starting, but the question specifically states 'failing to start,' pointing to a scheduling failure due to requests exceeding node capacity.

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.

  • ✗

    The maxSurge value is too low.

    Why it's wrong here

    maxSurge=1 allows one extra pod; it doesn't affect scheduling of new pods based on resources.

  • ✓

    The resource requests and limits are misconfigured.

    Why this is correct

    The requests are too high for the available node memory, causing the new pods to fail to schedule.

    Clue confirmation

    The clue word "most likely" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • ✗

    The replicas count is too high.

    Why it's wrong here

    Replicas=3 is not inherently too high; the issue is resource availability per pod.

  • ✗

    The strategy type is wrong.

    Why it's wrong here

    RollingUpdate is correct for zero-downtime updates; the issue is resource capacity.

Common exam traps

Common exam trap: answer the scenario, not the keyword

A common pitfall in Kubernetes rolling updates is confusing resource requests (used for scheduling) with limits (used for enforcement). Candidates often attribute the failure to a high replicas count or an insufficient maxSurge value, but the actual issue is that the pod's memory request exceeds the available capacity on any node in the cluster.

Detailed technical explanation

How to think about this question

Under the hood, the Kubernetes scheduler uses a predicate called 'NodeResourcesFit' to check if a node has enough allocatable memory to satisfy the sum of all pod requests. If the new pods have a memory request that exceeds any node's available memory, the scheduler marks them as unschedulable, and they remain in Pending state. A real-world scenario is when a developer sets a memory request equal to the limit for a large application, but the cluster nodes have less allocatable memory due to system overhead (e.g., kubelet, OS daemons), causing all new pods to fail scheduling during a rolling update.

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 PCD practice-question pages

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

Manage a Solution that Can Span Multiple Database Systems practice questions

Practise PCD questions linked to Manage a Solution that Can Span Multiple Database Systems.

Deploy Scalable and Highly Available Databases in Google Cloud practice questions

Practise PCD questions linked to Deploy Scalable and Highly Available Databases in Google Cloud.

Design Scalable and Highly Available Cloud Database Solutions practice questions

Practise PCD questions linked to Design Scalable and Highly Available Cloud Database Solutions.

Migrate Data Solutions practice questions

Practise PCD questions linked to Migrate Data Solutions.

Designing highly scalable, available, and reliable cloud-native applications practice questions

Practise PCD questions linked to Designing highly scalable, available, and reliable cloud-native applications.

Building and testing applications practice questions

Practise PCD questions linked to Building and testing applications.

Deploying applications practice questions

Practise PCD questions linked to Deploying applications.

Integrating Google Cloud services practice questions

Practise PCD questions linked to Integrating Google Cloud services.

Managing application performance monitoring practice questions

Practise PCD questions linked to Managing application performance monitoring.

PCD fundamentals practice questions

Practise PCD questions linked to PCD fundamentals.

PCD scenario practice questions

Practise PCD questions linked to PCD scenario.

PCD troubleshooting practice questions

Practise PCD questions linked to PCD troubleshooting.

Practice this exam

Start a free PCD practice session

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

10 questions20 questions30 questions50 questionsTimed 30
PCD practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this PCD question test?

Deploying applications — This question tests Deploying applications — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The resource requests and limits are misconfigured. — Option B is correct because the most likely cause of pods failing to start due to insufficient memory is misconfigured resource requests and limits. If the memory request (spec.containers[].resources.requests.memory) is set too high, the scheduler cannot find a node with enough allocatable memory, leaving pods in a Pending state. Similarly, if the limit is set too low, the pod may be OOMKilled after starting, but the question specifically states 'failing to start,' pointing to a scheduling failure due to requests exceeding node capacity.

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.

Are there clue words in this question I should notice?

Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

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

More PCD practice questions

Browse all PCD questions →

Last reviewed: Jul 4, 2026

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…

Sign in to join the discussion.

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.