Bird
0
0

You configured AWS WAF rules but still see unwanted traffic reaching your application. What is the most likely mistake?

medium📝 Debug Q14 of 15
AWS - Advanced Security
You configured AWS WAF rules but still see unwanted traffic reaching your application. What is the most likely mistake?
ANot attaching the WAF to the correct resource like CloudFront or ALB.
BUsing IAM roles instead of WAF for traffic filtering.
CEncrypting data with KMS before applying WAF rules.
DDisabling CloudTrail logging.
Step-by-Step Solution
Solution:

  1. Step 1: Understand WAF role and attachment

    WAF must be attached to resources like CloudFront or Application Load Balancer to filter traffic.

  2. Step 2: Identify common misconfiguration

    If WAF is not attached properly, it won't filter traffic, allowing unwanted requests.

  3. Final Answer:

    Not attaching the WAF to the correct resource like CloudFront or ALB. -> Option A

  4. Quick Check:

    WAF must be attached to filter traffic [OK]
Quick Trick: Attach WAF to resource to filter traffic [OK]
Common Mistakes:
  • Confusing IAM roles with traffic filtering
  • Thinking encryption affects WAF filtering
  • Ignoring resource attachment for WAF

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
CloudFormation - Resources section - Quiz 15hard CloudFormation - Nested stacks for modularity - Quiz 7medium Cost Optimization - Budgets and cost anomaly detection - Quiz 14medium ECS and Fargate - ECR for container image registry - Quiz 11easy ECS and Fargate - ECS cluster concept - Quiz 15hard Route 53 - Route 53 with ELB integration - Quiz 12easy Serverless Architecture - Lambda with S3 event triggers - Quiz 6medium Serverless Architecture - Serverless Application Model (SAM) - Quiz 11easy Serverless Architecture - Why serverless architecture matters - Quiz 11easy Serverless Architecture - Step Functions for workflows - Quiz 4medium