The correct answer is Automatic service discovery.

Automatic service discovery is the cloud native networking feature that lets a client such as the web UI dynamically find available API instances and route requests only to those that are healthy. It exposes service endpoints through DNS, APIs, or sidecar proxies and integrates with health checks so clients do not send traffic to failed backends.

Automatic service discovery is commonly implemented by platform primitives and service meshes. These implementations use a backing Service registry to record instances and health state and then present that information to clients so they can resolve and load balance to healthy targets.

eBPF is incorrect because it is a kernel level technology for packet processing, observability, and custom networking logic. It does not by itself provide a service level mechanism for automatically locating healthy service instances.

Service registry is incorrect as a standalone choice because it is a component used by discovery systems to store instance metadata. A registry supports discovery but the feature that performs dynamic resolution and client routing is the broader service discovery capability.

Cloud Load Balancing is incorrect because load balancers distribute traffic and can perform health checks at the network edge. They are not the same as the client side or platform feature that enables the web UI to automatically discover and resolve only healthy API instances, although load balancers may be used in combination with service discovery.

Full AWS Practitioner Certification Question