easymultiple choiceObjective-mapped

A system uses multiple AWS Lambda functions behind different event sources. One Lambda occasionally spikes and causes other Lambdas to be throttled due to shared concurrency limits. Which setting best helps ensure the important Lambda keeps capacity during spikes?

Question 1easymultiple choice
Full question →

A system uses multiple AWS Lambda functions behind different event sources. One Lambda occasionally spikes and causes other Lambdas to be throttled due to shared concurrency limits. Which setting best helps ensure the important Lambda keeps capacity during spikes?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Increase the function timeout so throttling is less likely.

Timeout affects how long a request can run, not how many requests can run concurrently. Throttling is typically related to concurrency limits rather than time limits. Increasing timeout does not reserve capacity for another function.

B

Best answer

Set Reserved Concurrency for the important Lambda function.

Reserved concurrency allocates a guaranteed amount of concurrent execution capacity to a specific Lambda. This prevents other functions from consuming all concurrency and throttling the important one. If the reserved limit is reached, only that function is throttled, isolating impact.

C

Distractor review

Enable Provisioned Concurrency for every Lambda in the account.

Provisioned Concurrency is useful for reducing cold starts, but it is not primarily a mechanism to guarantee capacity against account-wide spikes. Applying it to every function increases cost. Reserved concurrency is the direct control for prioritizing concurrency capacity.

D

Distractor review

Reduce the number of IAM policies attached to the Lambda roles.

IAM policy count does not control Lambda concurrency throttling. Throttling behavior depends on concurrency limits, scaling, and provisioned settings. Reducing IAM complexity improves manageability, not runtime concurrency availability.

Common exam trap

Common exam trap: OSPF can fail even when IP connectivity looks correct

OSPF neighbour formation depends on matching areas, timers, network type, authentication and passive-interface behaviour. Do not choose an answer only because the devices can ping.

Technical deep dive

How to think about this question

OSPF questions usually test the details that control adjacency and route selection. Read the neighbour state, area, router ID and interface configuration before deciding what is wrong.

KKey Concepts to Remember

  • OSPF neighbours must agree on key parameters.
  • Router ID selection can affect neighbour relationships and LSDB output.
  • OSPF cost influences the preferred path.
  • A route can appear in OSPF information but not become the installed route.

TExam Day Tips

  • Check area mismatch first when OSPF adjacency fails.
  • Review passive interfaces when a network is advertised but no neighbour forms.
  • Use show ip ospf neighbor and show ip route clues carefully.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

OSPF neighbours must agree on key parameters.

What is the correct answer to this question?

The correct answer is: Set Reserved Concurrency for the important Lambda function. — Lambda throttling from shared limits is best addressed by controlling concurrency at the function level. Reserved Concurrency reserves a specific concurrency amount for the chosen Lambda, ensuring it can keep executing even when other functions spike. When the reserved limit is exhausted, only that Lambda is throttled, which isolates the noisy neighbor problem. This is the most direct way to guarantee capacity for a critical workload without overprovisioning everything. Why others are wrong: Timeout does not increase concurrency; it only changes how long executions can run. Provisioned Concurrency can reduce cold starts but doesn’t reserve execution capacity against contention unless carefully configured; also doing it for every function is unnecessary and costly. Changing IAM policies cannot resolve concurrency throttling because concurrency limits are enforced by the Lambda runtime scaling and account limits.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.