mediummultiple choiceObjective-mapped

You use Amazon CloudFront in front of a private content S3 origin. To mitigate an OWASP Top 10 issue, you created a WAF web ACL and associated it to the CloudFront distribution, but attacks are still reaching the origin.

CloudWatch logs show the web ACL rules never match for the CloudFront requests.

What is the most likely configuration mistake?

Question 1mediummultiple choice
Full question →

You use Amazon CloudFront in front of a private content S3 origin. To mitigate an OWASP Top 10 issue, you created a WAF web ACL and associated it to the CloudFront distribution, but attacks are still reaching the origin.

CloudWatch logs show the web ACL rules never match for the CloudFront requests.

What is the most likely configuration mistake?

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

The WAF web ACL intended for CloudFront must be created in the us-east-1 (N. Virginia) region (CloudFront scope), even if the rest of the stack is in another region.

CloudFront-scoped WAF web ACLs use a global scope that is provisioned/managed in us-east-1. Creating the web ACL in the wrong region (or with the wrong scope) prevents CloudFront from evaluating the expected web ACL rules, which would lead to no rule matches in logs.

B

Distractor review

WAF rules only evaluate requests after they reach the origin, so the absence of matches means the origin is blocking traffic first.

WAF evaluates requests at the edge (before the request is forwarded to the origin). If rules never match, the issue is more likely related to WAF association/scope/rule logic than the origin blocking first.

C

Distractor review

For CloudFront, you must use a regional WAF endpoint and cannot use a global web ACL.

CloudFront uses a global WAF web ACL scope. The service expects a CloudFront-scoped web ACL, which is created/managed in us-east-1.

D

Distractor review

WAF web ACL rules never apply to signed URLs or signed cookies, so the web ACL is bypassed by design.

Signed URLs and signed cookies are still requests that WAF evaluates. WAF does not bypass evaluation solely due to the request being signed.

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: The WAF web ACL intended for CloudFront must be created in the us-east-1 (N. Virginia) region (CloudFront scope), even if the rest of the stack is in another region. — For CloudFront, WAF uses a global (CloudFront) scope that is managed/provisioned in us-east-1. If the web ACL was created with the wrong region/scope and then associated, CloudFront may not evaluate the intended rules, resulting in zero rule matches in logs. The most likely fix is to recreate the web ACL with the correct CloudFront scope in us-east-1 and re-associate it to the CloudFront distribution. Why others are wrong: B is incorrect because WAF inspects requests before they reach the origin. C is incorrect because CloudFront requires a CloudFront-scoped (global) web ACL. D is incorrect because WAF evaluates signed requests as well; the signed nature does not bypass WAF rule evaluation.

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.