Exam AWS-SysOps topic 1 question 881 discussion

B and D look look to be accurate

B & D are the answers

The possible causes of the problem could be: B. The DNS is still pointing to the ALB instead of the CloudFront distribution. If the DNS is still pointing to the ALB, then the traffic would not be routed through CloudFront, and the load on the web servers would not decrease. The DNS should point to the CloudFront distribution to ensure that requests are served by CloudFront. D. The default, minimum, and maximum Time to Live (TTL) are set to 0 seconds on the CloudFront distribution. If the TTL values are set to 0, CloudFront would not cache the responses and would forward every request to the ALB, resulting in no change in the load on the web servers. The TTL values should be increased to enable caching in CloudFront. Option A is not likely because the Origin Access Identity (OAI) is used when the origin of the CloudFront distribution is an S3 bucket. Option C is not likely because CloudFront does not send requests to the ALB; instead, the ALB serves as the origin for the CloudFront distribution. Option E is not likely because sticky sessions determine how requests from a client are routed to targets in the target group, but they do not affect how requests are routed between CloudFront and the ALB.

B. The DNS is still pointing to the ALB instead of the CloudFront distribution. Explanation: When you set up an Amazon CloudFront distribution with an ALB as the origin, you need to ensure that the DNS (Domain Name System) is configured to point to the CloudFront distribution's domain name (e.g., d12345abcdefg.cloudfront.net) instead of directly to the ALB's endpoint (e.g., my-alb.example.com). If the DNS is still pointing directly to the ALB, requests will bypass CloudFront, and the load will not be reduced on the web servers. D. The default, minimum, and maximum Time to Live (TTL) are set to 0 seconds on the CloudFront distribution. Explanation: The Time to Live (TTL) settings in CloudFront control how long CloudFront caches objects before fetching a fresh copy from the origin server (in this case, the ALB). If the TTL settings are set to 0 seconds, it effectively disables caching in CloudFront, and every request will go directly to the ALB, resulting in no reduction in web server load.

I vote for B and E

B & E are correct. B. The DNS is still pointing to the ALB---Route53 has an Alias record poiting to ALB, you need to change dest to CloudFront distribution. E. Sticky sessions---With or without CF, the sticky session feature, also known as session affinity, is used to enable the ELB to bind a user's session to a specific target EC2.

B...? I'm worried