Your organization has a highly available application that is not HTTP-based. The application runs on multiple TCP ports and is hosted in multiple regions. You need to design a solution to load…

Question

Options

• AConfigure multiple regional internal proxy Network Load Balancers and enable global access. Use
• BConfigure multiple regional internal Application Load Balancers and enable global access. Use
• CConfigure a single cross region internal proxy Network Load Balancer.
• DConfigure multiple regional internal passthrough Network Load Balancers and enable global

• A
  27% (13)
• B
  6% (3)
• C
  10% (5)
• D
  57% (28)

Explanation

Internal passthrough Network Load Balancer: - This load balancer works at the Layer 4 (TCP/UDP) level and is ideal for non-HTTP applications that run on multiple TCP ports. - It preserves the client's true source IP address, which is a requirement in your case. Multiple regional load balancers: - Deploying a regional load balancer in each region ensures that traffic is handled locally within a region for lower latency and redundancy. - This also aligns with your application's multi-region hosting design. Global access and DNS routing policies: - Enabling global access on each regional passthrough Network Load Balancer ensures that traffic from one region can be directed to another if needed. - Using DNS routing policies (e.g., weighted, latency-based, or geo-based) allows you to balance traffic across regions intelligently and ensure high availability. No public internet access: - The internal passthrough Network Load Balancer is internal-only, meaning it does not expose the application to the public internet. This meets the requirement of avoiding public internet This design is optimized for multi-region, highly available, non-HTTP applications running on multiple TCP ports, while meeting the requirement to retain the client's true source IP address and avoid public internet access.

No community discussion yet for this question.