1V0-71.21 · Question #50
What is a defining characteristic of a Microservice?
The correct answer is A. An architectural pattern that encapsulates a specific business capability. A microservice is defined by its encapsulation of a single, well-bounded business capability (e.g., "user authentication" or "order processing"), deployed and scaled independently - making A the defining characteristic. B is wrong because microservices are a forward-looking…
Question
What is a defining characteristic of a Microservice?
Options
- AAn architectural pattern that encapsulates a specific business capability.
- BA failover mechanism for legacy applications.
- CA new technology to handle API management.
- DSoftware for automation of container orchestration.
How the community answered
(41 responses)- A88% (36)
- B2% (1)
- C2% (1)
- D7% (3)
Explanation
A microservice is defined by its encapsulation of a single, well-bounded business capability (e.g., "user authentication" or "order processing"), deployed and scaled independently - making A the defining characteristic. B is wrong because microservices are a forward-looking architectural pattern, not a failover mechanism for legacy systems. C is wrong because API management (e.g., gateways, rate limiting) is a separate concern that supports microservices but isn't what defines them. D is wrong because container orchestration (e.g., Kubernetes) is infrastructure tooling that runs microservices, not a definition of them.
Memory tip: Think "micro = one job." Each microservice does exactly one business job - if you can name it with a single business noun ("payments," "inventory"), it's a microservice.
Topics
Community Discussion
No community discussion yet for this question.