VPC Lattice for Microservice Service Discovery

SAA-C03 By islever Editorial Last updated

Determine high-performing and/or scalable network architectures.

Short answer

B Create a VPC Lattice service network to provide service discovery and HTTPS communication with least administrative overhead.

Question

Use Amazon Elastic Kubernetes Service (Amazon EKS) with Amazon EC2 worker nodes. A company has deployed an application in an AWS account. The application consists of microservices that run on AWS Lambda and Amazon Elastic Kubernetes Service (Amazon EKS). A separate team supports each microservice. The company has multiple AWS accounts and wants to give each team its own account for its microservices. A solutions architect needs to design a solution that will provide service-to-service communication over HTTPS (port 443). The solution also must provide a service registry for service discovery. Which solution will meet these requirements with the LEAST administrative overhead?
  1. Create an inspection VPC. Deploy an AWS Network Firewall firewall to the inspection VPC. Attach the inspection VPC to a new transit gateway. Route VPC-to-VPC traffic to the inspection VPC. Apply firewall rules to allow only HTTPS communication.
  2. Create a VPC Lattice service network. Associate the microservices with the service network. Define HTTPS listeners for each service. Register microservice compute resources as targets. Identify VPCs that need to communicate with the services. Associate those VPCs with the service network. Correct Answer
  3. Create a Network Load Balancer (NLB) with an HTTPS listener and target groups for each microservice. Create an AWS PrivateLink endpoint service for each microservice. Create an interface VPC endpoint in each VPC that needs to consume that microservice.
  4. Create peering connections between VPCs that contain microservices. Create a prefix list for each service that requires a connection to a client. Create route tables to route traffic to the appropriate VPC. Create security groups to allow only HTTPS communication.

Key Takeaways

The question tests knowledge of modern AWS networking services, specifically how VPC Lattice replaces complex manual routing and load balancing setups for microservice architectures.

Amazon VPC Lattice simplifies service-to-service communication and discovery across multiple AWS accounts with minimal configuration. This page explains why VPC Lattice is the optimal solution for HTTPS traffic between microservices.

Common mistake: Candidates often choose Network Load Balancer (NLB) or Peering Connections because they are familiar traditional AWS networking tools, but these require significantly more administrative overhead to manage service discovery and cross-account access.

Expert Analysis

Why the Answer Is Correct

Amazon VPC Lattice is a network service that provides service connectivity and observability for services running anywhere on AWS. It natively integrates service discovery, allowing you to define services and their dependencies without managing complex route tables or endpoints. By associating microservices with a VPC Lattice service network and defining listeners, you automatically handle service discovery and secure HTTPS communication. This approach drastically reduces administrative overhead compared to manually configuring NLBs, PrivateLink endpoints, or VPC peering routes for each microservice.

Why the Other Options Are Wrong

Option A involves AWS Network Firewall and Transit Gateways, which adds significant complexity and cost for simple service-to-service communication. Option C requires creating individual NLBs, PrivateLink endpoint services, and interface VPC endpoints for every microservice, leading to high administrative overhead. Option D relies on VPC peering and manual route table management, which becomes unmanageable as the number of microservices and accounts grows.

Community Comment Notes

Community consensus strongly supports VPC Lattice. As user 1dd noted, "VPC Lattice is a completely new way to simplify API communication." Another commenter, zinabu, highlighted that it is designed to "simplify networking for service-to-service communication." The unanimous vote distribution reflects a clear understanding of this newer AWS capability.

Official Reference

https://docs.aws.amazon.com/vpc-lattice/latest/adminguide/what-is-vpc-lattice.html

This link opens the official vendor documentation in a new tab.

Exam Strategy

Focus on keywords like 'least administrative overhead' and 'service registry'. When these appear together with microservices, look for managed service mesh or service networking solutions like VPC Lattice rather than traditional load balancers or peering.

Frequently Asked Questions

Why not use NLB for microservice discovery?

NLB requires manual creation of target groups and endpoints for each service, increasing overhead. VPC Lattice automates discovery.

Does VPC Lattice support cross-account communication?

Yes, VPC Lattice is designed to simplify service connectivity across multiple AWS accounts and regions seamlessly.

More SAA-C03 FAQ →

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. 1dd 👍 7 Answered B
    VPC Lattice is a completely new way to simplify API communication between services or microservices in one or more AWS accounts.
  2. zinabu 👍 4 Answered B
    Amazon VPC Lattice is a new capability of Amazon Virtual Private Cloud (Amazon VPC) designed to simplify networking for service-to-service communication. link: https://www.bing.com/search?q=what+VPC+Lattice+service+used+for+microservices&cvid=d706d95737274f388660cbda9b7b2c4e&gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIICAEQ6QcY_FXSAQkyMTY1N2owajSoAgCwAgE&FORM=ANAB01&PC=U531
  3. stephensimudemy 👍 3 Answered B
    IT's B. Google VPC Lattice service network
  4. Andy_09 👍 4
    Option B

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

S3 Multi-Region Access Point and Replication Strategy

S-grade

Securing NLB with Security Groups for Minimal Change

S-grade

Most Cost-Effective 7-Year Retention for EBS Snapshots?

S-grade

AWS Forecast vs SageMaker for Time-Series Prediction

S-grade

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide