mediummulti selectObjective-mapped

A public API is delivered through CloudFront and an Application Load Balancer. The security team wants AWS to automatically block repetitive bursts from the same client IP and also reduce exposure to common web exploits without custom code. Which two AWS WAF features should be enabled? Select two.

Question 1mediummulti select
Full question →

A public API is delivered through CloudFront and an Application Load Balancer. The security team wants AWS to automatically block repetitive bursts from the same client IP and also reduce exposure to common web exploits without custom code. Which two AWS WAF features should be enabled? Select two.

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

Best answer

A rate-based rule that blocks clients exceeding a request threshold from the same source IP.

Rate-based rules are the native WAF feature for detecting and blocking unusually high request rates from the same IP or set of IPs. This helps stop bursts that can indicate abuse or application-layer flooding.

B

Best answer

An AWS Managed Rules group for common web exploits.

AWS Managed Rules provide maintained rule sets for common threats such as injection patterns and known-bad request signatures. They add broad protection without requiring the team to write and maintain custom logic.

C

Distractor review

ALB sticky sessions for all requests.

Sticky sessions help keep a client on the same target, but they do not inspect requests for attacks or block abusive traffic patterns.

D

Distractor review

A security group rule that blocks requests based on HTTP path.

Security groups operate at the network and port layer. They cannot inspect HTTP paths or implement request-rate controls.

E

Distractor review

CloudFront origin access control for the API endpoint.

Origin access control is used to restrict access to S3 origins behind CloudFront. It does not provide API abuse protection for an ALB-backed application.

Common exam trap

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.

Technical deep dive

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.

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?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: A rate-based rule that blocks clients exceeding a request threshold from the same source IP. — AWS WAF is the right service for both requirements. A rate-based rule automatically blocks clients that exceed a request threshold, which is useful for repeated bursts from the same source. AWS Managed Rules add vendor-maintained protections for common exploit patterns and reduce the need for custom signatures. Together, they provide edge-layer protection for both abusive traffic and common web exploits. Sticky sessions affect load balancing behavior, not security inspection. Security groups cannot inspect application-layer content or count requests over time. Origin access control is designed for S3 origins, not for API-layer abuse prevention. WAF provides the application-layer controls required in this scenario.

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.