When planning and designing business security, ELB can be set to provide services to the public network to ensure business scalability while avoiding the direct opening of business nodes to the…

Question

Options

• ATrue
• BFalse

• A
  83% (30)
• B
  17% (6)

Explanation

Option A is correct because an Elastic Load Balancer (ELB) is designed to sit at the edge of your infrastructure, accepting inbound traffic from the public internet and distributing it to backend business nodes that remain in a private or internal network. This means the ELB serves as the single, controlled public-facing entry point, so backend servers never need a public IP or direct internet exposure. The architecture inherently supports scalability because you can add or remove backend nodes without changing what the public sees, while also reducing the attack surface since only the ELB is reachable from the internet.

Option B is incorrect because it contradicts how ELB is architecturally designed to function - the separation of public-facing load balancer from private backend nodes is a core feature, not a limitation.

Memory tip: Think of ELB as a hotel front desk. Guests (public traffic) only interact with the front desk (ELB), never wandering directly into staff areas (business nodes). The hotel can add more staff rooms in the back without exposing them to guests.

No community discussion yet for this question.