easymultiple choiceObjective-mapped

Your organization hosts an internet-facing application behind an Amazon CloudFront distribution. You want to mitigate common web exploits (for example, SQL injection and XSS) at the edge. Which action is the most appropriate way to do this using AWS services?

Question 1easymultiple choice
Full question →

Your organization hosts an internet-facing application behind an Amazon CloudFront distribution. You want to mitigate common web exploits (for example, SQL injection and XSS) at the edge. Which action is the most appropriate way to do this using AWS services?

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

Create an AWS WAF web ACL using managed rule sets and associate it with the CloudFront distribution.

AWS WAF examines incoming HTTP/HTTPS requests at the edge (when associated to CloudFront) and applies rule logic to detect common exploit patterns. Managed rule sets provide pre-built protections for threats like SQL injection and XSS before requests reach your origin.

B

Distractor review

Add inbound rules to the security group so that only port 443 is open from the internet.

Security groups control network reachability (instance-level inbound/outbound), not application-layer payload inspection. Allowing port 443 does not prevent SQL injection or XSS because those attacks occur within the HTTP request content.

C

Distractor review

Enable AWS Shield Advanced to block SQL injection and XSS.

AWS Shield Advanced primarily provides protection against Distributed Denial of Service (DDoS) attacks. It is not designed for application exploit detection such as SQL injection/XSS, which is addressed by WAF.

D

Distractor review

Restrict IAM permissions for the application’s EC2 instances so that SQL injection payloads cannot be executed.

IAM permissions do not inspect or block malicious HTTP request payloads. SQL injection/XSS mitigation requires request filtering or input validation at the application or edge (for example, via AWS WAF).

Common exam trap

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Technical deep dive

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

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?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: Create an AWS WAF web ACL using managed rule sets and associate it with the CloudFront distribution. — Associate AWS WAF with your CloudFront distribution and use managed rule sets for common web exploit patterns. WAF evaluates HTTP/HTTPS requests at the edge and can block requests that match SQL injection/XSS signatures before they reach the origin. This directly targets exploit mitigation at the request-processing layer rather than only network access controls. Why others are wrong: Option B addresses only transport/network-level access, not application-layer exploit payloads. Option C focuses on DDoS protection rather than SQLi/XSS detection. Option D confuses authorization (IAM) with request filtering; IAM does not prevent execution of malicious content delivered over HTTP.

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.