SOA-C02 Deployment, Provisioning, and Automation Practice Question
A SysOps administrator needs to deploy a microservices application using AWS Elastic Beanstalk. The application consists of multiple services that need to communicate with each other. Which Elastic Beanstalk environment type should the administrator choose?
⚠ Common exam trap
Candidates often confuse a Worker environment with a general-purpose compute environment, but Worker environments are specifically for asynchronous message processing via SQS, not for synchronous HTTP communication between microservices.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Load-balanced environment
A load-balanced environment (option C) is the correct choice because it provisions an Elastic Load Balancer (ELB) in front of Amazon EC2 instances, enabling the multiple microservices to communicate via HTTP/HTTPS endpoints. This environment type supports horizontal scaling and distributes incoming traffic across instances, which is essential for inter-service communication in a microservices architecture.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Worker environment
Why it's wrong here
In Elastic Beanstalk, a worker environment runs a background daemon that processes jobs from an SQS queue. It does not have a load balancer or accept inbound HTTP traffic from clients, so it cannot serve as the front-end for a microservices app that needs to expose REST APIs and handle request routing. Worker tiers are designed for long-running tasks like processing messages, not for hosting microservices endpoints.
- ✗
Web server environment
Why it's wrong here
A web server environment in Elastic Beanstalk can be either single-instance or load-balanced, depending on the chosen configuration. The question specifically asks for an environment type that supports service-to-service communication and traffic distribution. A plain 'web server environment' is too generic—it could be a single instance without a load balancer, which wouldn't meet the requirements. The correct type is a load-balanced web server environment, so 'web server environment' alone is not precise.
- ✓
Load-balanced environment
Why this is correct
A load-balanced environment provisions an Elastic Load Balancer (ALB or NLB) in front of the EC2 instances running the microservices. This allows incoming traffic to be distributed across multiple instances, provides a stable endpoint for external clients, and enables services to discover each other via the load balancer DNS name. It also supports health checks, auto scaling, and rolling deployments, which are essential for production microservices.
- ✗
Single-instance environment
Why it's wrong here
A single-instance environment runs only one EC2 instance without a load balancer. It is intended for development and testing, not for production microservices that require high availability, fault tolerance, and horizontal scaling. Without a load balancer, there is no traffic distribution, and the instance becomes a single point of failure, making it unsuitable for a microservices architecture that needs inter-service communication and resilience.
Go deeper
Related to this question
About these practice questions
One of 1,169 original SOA-C02 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SOA-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SOA-C02 exam.