Question 1,136 of 1,740
Resilient Cloud SolutionsmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to implement a predictive scaling policy combined with dynamic scaling, as this directly addresses the need for proactive capacity management to prevent 503 errors during peak hours. Predictive scaling uses historical traffic data to forecast demand and pre-warm the Auto Scaling group, while dynamic scaling handles real-time deviations, ensuring the healthy host count never drops to zero. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this scenario tests your understanding of how reactive policies like simple or step scaling fail under sudden spikes, whereas predictive scaling aligns with the exam’s focus on automation and resilience. A common trap is choosing scheduled scaling, which works only for rigid patterns, or increasing the health check grace period, which doesn’t solve the scaling lag. Memory tip: “Predict before you react” — predictive scaling forecasts, dynamic scaling corrects, together they prevent the dip.

DOP-C02 Resilient Cloud Solutions Practice Question

This DOP-C02 practice question tests your understanding of resilient cloud solutions. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. 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 company runs a multi-tier web application on AWS. The web tier consists of EC2 instances behind an Application Load Balancer (ALB) in an Auto Scaling group across three Availability Zones. The application tier runs on a separate Auto Scaling group of EC2 instances that process requests from the web tier. The database tier uses an Amazon RDS for PostgreSQL Multi-AZ deployment. All application servers write logs to Amazon CloudWatch Logs. Recently, the operations team reported that during peak hours, the web tier experiences intermittent 503 errors. The ALB access logs show that the errors occur when the target group's healthy host count drops to zero momentarily. The Auto Scaling group's minimum and desired capacity is 6, with a maximum of 12. The scaling policy is based on average CPU utilization, with a target of 60%. The health check grace period is 300 seconds. The application health check endpoint returns a 200 status when healthy. The DevOps engineer suspects that the scaling policy is too slow to react to traffic spikes. The engineer wants to implement a more proactive scaling approach. Which solution should the engineer implement?

Clue words in this question

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

  • Clue: "minimum / minimize"

    Why it matters: Asks for the least resource use — fewest addresses, smallest subnet, lowest overhead. Eliminate over-provisioned options even if they would technically work.

Question 1mediummultiple choice
Full question →

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

Implement a predictive scaling policy combined with dynamic scaling to proactively adjust capacity based on forecasted traffic.

Option D is correct because using a predictive scaling policy combined with dynamic scaling provides a proactive approach that anticipates traffic patterns and adjusts capacity in advance. Option A (increasing health check grace period) does not help with scaling speed. Option B (step scaling with a lower cooldown) is reactive and may still cause dips. Option C (scheduled scaling) works only if traffic patterns are predictable and doesn't handle spikes well.

Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.

Answer analysis

Option-by-option breakdown

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

  • Implement a predictive scaling policy combined with dynamic scaling to proactively adjust capacity based on forecasted traffic.

    Why this is correct

    Predictive scaling uses historical data to forecast demand and proactively adjust capacity, preventing the healthy host count from dropping to zero.

    Clue confirmation

    The clue word "minimum / minimize" in the question point toward this answer.

    Related concept

    Static NAT maps one inside address to one outside address.

  • Implement a scheduled scaling policy that increases capacity 30 minutes before the expected peak.

    Why it's wrong here

    Scheduled scaling is useful for predictable patterns but may not handle unexpected spikes.

  • Increase the health check grace period to 600 seconds to give new instances more time to become healthy.

    Why it's wrong here

    Increasing grace period delays the inclusion of new instances, potentially worsening the issue.

  • Switch to a step scaling policy with a lower cooldown period and a greater scaling adjustment.

    Why it's wrong here

    Step scaling is reactive; even with lower cooldown, it may not prevent the momentary zero healthy hosts.

Common exam traps

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Detailed technical explanation

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

Key takeaway

NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.

Real-world example

How this comes up in practice

A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.

What to study next

Got this wrong? Here's your next step.

Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related DOP-C02 NAT questions on configuration and troubleshooting.

Related practice questions

Related DOP-C02 practice-question pages

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

Practice this exam

Start a free DOP-C02 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 DOP-C02 question test?

Resilient Cloud Solutions — This question tests Resilient Cloud Solutions — Static NAT maps one inside address to one outside address..

What is the correct answer to this question?

The correct answer is: Implement a predictive scaling policy combined with dynamic scaling to proactively adjust capacity based on forecasted traffic. — Option D is correct because using a predictive scaling policy combined with dynamic scaling provides a proactive approach that anticipates traffic patterns and adjusts capacity in advance. Option A (increasing health check grace period) does not help with scaling speed. Option B (step scaling with a lower cooldown) is reactive and may still cause dips. Option C (scheduled scaling) works only if traffic patterns are predictable and doesn't handle spikes well.

What should I do if I get this DOP-C02 question wrong?

Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related DOP-C02 NAT questions on configuration and troubleshooting.

Are there clue words in this question I should notice?

Yes — watch for: "minimum / minimize". Asks for the least resource use — fewest addresses, smallest subnet, lowest overhead. Eliminate over-provisioned options even if they would technically work.

What is the key concept behind this question?

Static NAT maps one inside address to one outside address.

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

Last reviewed: Jun 20, 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 DOP-C02 practice question is part of Courseiva's free Amazon Web Services 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 DOP-C02 exam.