CLF-C02 Cloud Technology and Services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Amazon Route 53

  Why it's wrong here

  Amazon Route 53 is a scalable DNS service that resolves hostnames to IP addresses using records you configure, but those records are not automatically created or removed when container tasks scale in or out. Its routing policies, health checks, and alias records operate against explicitly defined endpoints, so it cannot inherently track ephemeral container instances. To use Route 53 for container discovery, you would need a separate mechanism to create and delete records as services change, making it a poor fit for automated microservice discovery.

• ✓

  AWS Cloud Map

  Why this is correct

  AWS Cloud Map is a fully managed service discovery service that maintains a registry of application resources such as containers, EC2 instances, and serverless functions, and automatically registers instances when they become healthy and de-registers them when they terminate. It supports both DNS-based discovery (using automatically updated A/SRV records) and API-based discovery via the DiscoverInstances endpoint, letting clients query live, healthy endpoints. This dynamic behavior directly addresses the need to track services that scale up and down, which is why Cloud Map is the correct answer here.

• ✗

  Elastic Load Balancing

  Why it's wrong here

  Elastic Load Balancing (ELB) forwards incoming traffic to a set of registered targets, such as EC2 instances or IP addresses, but it does not maintain a service registry or expose a discovery API for clients. The load balancer relies on target groups and health checks to route traffic, and while it can work with autoscaling, target registration is a separate operational step — ELB won't automatically discover container services or update its target list based on service startup and shutdown. Its role is traffic distribution, not service instance discovery, which is why it is incorrect for this scenario.

• ✗

  Amazon VPC

  Why it's wrong here

  Amazon VPC provides logical network isolation, subnets, route tables, gateways, and security groups, giving you control over the network layer in which containers run. It contains no concept of a service registry or an API for discovering individual application instances, and it does not track the lifecycle of container tasks or pods. While VPC is necessary infrastructure for networking, it cannot fulfill the requirement of automatic registration and de-registration of dynamically scaling services, making it an incorrect choice.

Go deeper

Related to this question