Question 204 of 1,040
Design High-Performing ArchitectureshardMultiple ChoiceObjective-mapped

SAA-C03 Design High-Performing Architectures Practice Question

This SAA-C03 practice question tests your understanding of design high-performing architectures. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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

Lambda monitoring and deployment notes:
- Function: checkout-api-prod
- Current alias: live
- Invocations per day: low except weekdays 09:00-09:15 UTC
- REPORT log sample at 09:00 UTC:
  Init Duration: 842.31 ms
  Duration: 128.42 ms
  Billed Duration: 1000 ms
- REPORT log sample at 09:05 UTC:
  Init Duration: 0.00 ms
  Duration: 121.77 ms

Traffic pattern:
- Spikes are predictable and last about 15 minutes
- No need to keep high concurrency all day

Based on the exhibit, a serverless API on AWS Lambda experiences a predictable cold-start penalty every weekday at 09:00 UTC when a marketing campaign begins. The team wants the first requests to stay fast while minimizing extra cost during quiet periods. What is the best approach?

Clue words in this question

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

  • Clue: "best"

    Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

  • Clue: "first"

    Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.

Question 1hardmultiple choice
Full question →

Exhibit

Lambda monitoring and deployment notes:
- Function: checkout-api-prod
- Current alias: live
- Invocations per day: low except weekdays 09:00-09:15 UTC
- REPORT log sample at 09:00 UTC:
  Init Duration: 842.31 ms
  Duration: 128.42 ms
  Billed Duration: 1000 ms
- REPORT log sample at 09:05 UTC:
  Init Duration: 0.00 ms
  Duration: 121.77 ms

Traffic pattern:
- Spikes are predictable and last about 15 minutes
- No need to keep high concurrency all day

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

Enable provisioned concurrency on the published version and schedule it to scale up shortly before the spike.

Provisioned concurrency pre-warms a specified number of Lambda execution environments so that incoming requests do not incur a cold start. By scheduling the provisioned concurrency to scale up just before the 09:00 UTC spike and scale down afterward, the team eliminates the cold-start penalty during the campaign while minimizing cost during quiet periods. This directly addresses the predictable, time-bound traffic pattern without requiring code changes or over-provisioning.

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.

  • Enable provisioned concurrency on the published version and schedule it to scale up shortly before the spike.

    Why this is correct

    Provisioned concurrency keeps warm execution environments ready for the alias or version, which removes the cold-start penalty. Scheduling it only around the known spike keeps performance high while limiting unnecessary cost during idle periods.

    Clue confirmation

    The clue words "best", "first" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Increase the Lambda timeout so cold starts have more time to complete.

    Why it's wrong here

    A longer timeout does not reduce cold-start latency. It only allows slower executions to run longer, which does not help the first-request experience.

  • Move the function behind an Application Load Balancer to improve warm-up behavior.

    Why it's wrong here

    An ALB does not prevent Lambda cold starts. The issue is execution environment initialization, not the front-end integration type.

  • Increase the function memory to the maximum value and leave concurrency unchanged.

    Why it's wrong here

    More memory can improve execution speed, but it does not eliminate initialization delay. The exhibit specifically shows the first request suffering from init duration, which requires concurrency management.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse increasing memory or timeout with solving cold starts, or they mistakenly think an ALB can pre-warm Lambda, when in fact only provisioned concurrency guarantees warm containers for the first requests in a predictable traffic spike.

Trap categories for this question

  • Command / output trap

    More memory can improve execution speed, but it does not eliminate initialization delay. The exhibit specifically shows the first request suffering from init duration, which requires concurrency management.

Detailed technical explanation

How to think about this question

Provisioned concurrency works by keeping a configurable number of execution environments initialized and ready to handle requests, bypassing the cold-start phase that includes downloading the code, starting the runtime, and running initialization code outside the handler. Under the hood, AWS Lambda uses a pool of sandboxed micro-VMs (Firecracker) that are recycled after a period of inactivity; provisioned concurrency ensures these VMs are kept warm and allocated to a specific function version. In real-world scenarios, this is critical for latency-sensitive applications like real-time ad bidding or chatbot responses where even sub-second delays degrade user experience.

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 startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.

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 SAA-C03 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 SAA-C03 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 SAA-C03 question test?

Design High-Performing Architectures — This question tests Design High-Performing Architectures — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Enable provisioned concurrency on the published version and schedule it to scale up shortly before the spike. — Provisioned concurrency pre-warms a specified number of Lambda execution environments so that incoming requests do not incur a cold start. By scheduling the provisioned concurrency to scale up just before the 09:00 UTC spike and scale down afterward, the team eliminates the cold-start penalty during the campaign while minimizing cost during quiet periods. This directly addresses the predictable, time-bound traffic pattern without requiring code changes or over-provisioning.

What should I do if I get this SAA-C03 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: "best", "first". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

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

Last reviewed: Jun 11, 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 SAA-C03 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 SAA-C03 exam.