Amazon SAP-C02 Exam - Topic 4 Question 63 Discussion

Actual exam question for Amazon's SAP-C02 exam

Question #: 63
Topic #: 4

A company is running a web application in a VPC. The web application runs on a group of Amazon EC2 instances behind an Application Load Balancer (ALB). The ALB is using AWS WAF.

An external customer needs to connect to the web application. The company must provide IP addresses to all external customers.

Which solution will meet these requirements with the LEAST operational overhead?

AReplace the ALB with a Network Load Balancer (NLB). Assign an Elastic IP address to the NLB.

BAllocate an Elastic IP address. Assign the Elastic IP address to the ALProvide the Elastic IP address to the customer.

CCreate an AWS Global Accelerator standard accelerator. Specify the ALB as the accelerator's endpoint. Provide the accelerator's IP addresses to the customer.

DConfigure an Amazon CloudFront distribution. Set the ALB as the origin. Ping the distribution's DNS name to determine the distribution's public IP address. Provide the IP address to the customer.

Show Suggested Answer

Suggested Answer: C

https://docs.aws.amazon.com/global-accelerator/latest/dg/about-accelerators.alb-accelerator.html Option A is wrong. AWS WAF does not support associating with NLB. https://docs.aws.amazon.com/waf/latest/developerguide/waf-chapter.html Option B is wrong. An ALB does not support an Elastic IP address.https://aws.amazon.com/elasticloadbalancing/features/

by Herschel at Jan 05, 2026, 05:16 AM

Limited Time Offer

25%

Off

Get Premium SAP-C02 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Carissa

4 days ago

I think option C is the best. Global Accelerator is easy to manage.

upvoted 0 times

...

Matthew

10 days ago

Just allocate an Elastic IP and assign it to the ALB, super simple!

upvoted 0 times

...

Louvenia

15 days ago

NLB with Elastic IP is a solid option too, though.

upvoted 0 times

...

Florinda

20 days ago

Wait, can you really use CloudFront for this? Sounds odd.

upvoted 0 times

...

Felicidad

25 days ago

I disagree, I think D could work just as well!

upvoted 0 times

...

Xuan

1 month ago

Option C is the best choice for minimal overhead.

upvoted 0 times

...

Selma

1 month ago

Option C is the clear winner here. Who needs a bunch of IP addresses when you can just use Global Accelerator? That's the lazy man's solution!

upvoted 0 times

...

Delmy

2 months ago

C is the way to go, but I'm curious - why not just use a Network Load Balancer? Seems like that would be a good option too.

upvoted 0 times

...

Lindsey

2 months ago

Hmm, I'm not sure. Wouldn't an Elastic IP be simpler? Option B seems like the easiest solution.

upvoted 0 times

...

Freeman

2 months ago

I agree, C is the best solution. Global Accelerator is the perfect fit for this use case.

upvoted 0 times

...

Aileen

2 months ago

Option C is the way to go. Least operational overhead and the customer gets the IP addresses they need.

upvoted 0 times

...

Val

3 months ago

CloudFront could work too, but I remember it adds some complexity with caching. I wonder if that would really be the least operational overhead option.

upvoted 0 times

...

Shay

3 months ago

I think using AWS Global Accelerator could be a good solution since it provides static IPs and improves performance, but I’m not completely confident about the operational overhead part.

upvoted 0 times

...

Mauricio

3 months ago

I practiced a similar question where we had to provide static IPs. I feel like using an Elastic IP directly on the ALB could work, but it seems like there might be a better option.

upvoted 0 times

...

Ardella

3 months ago

I remember studying about load balancers, and I think the ALB is better for HTTP traffic, but I'm not sure if replacing it with an NLB is the best choice.

upvoted 0 times

...

Leonard

3 months ago

I'm pretty confident I can tackle this one. Based on the information provided, option C using AWS Global Accelerator seems like the best choice. It allows the company to give the customer a stable set of IP addresses to connect to, while also leveraging the benefits of the ALB in the background. The fact that it's described as the "least operational overhead" solution is a big plus in my book.

upvoted 0 times

...

Tammara

3 months ago

Okay, I think I've got this. The key here is that the company needs to provide IP addresses to external customers, so options that involve an Elastic IP or public IP address are going to be the most straightforward. I'm leaning towards option B - allocating an Elastic IP and assigning it to the ALB. That seems like the simplest solution that meets the requirements.

upvoted 0 times

...

Toshia

4 months ago

Hmm, I'm a bit confused on this one. I'm not sure I fully understand the differences between the load balancer options. I'd probably need to review the details of each one to decide which would be the best fit. Maybe I'll start by looking up the key features of NLBs, ALBs, and Global Accelerator to see which one aligns best with the requirements.

upvoted 0 times

...

Jospeh

4 months ago

This seems like a straightforward networking question. I'd start by considering the requirements - the company needs to provide IP addresses to external customers, and they want the solution with the least operational overhead. I'm leaning towards option C, using AWS Global Accelerator, as that seems like it would be the easiest to set up and maintain.

upvoted 0 times

...