nerdexam
CompTIA

SY0-701 · Question #596

Which of the following best describe the benefits of a microservices architecture when compared to a monolithic architecture? (Choose two.)

The correct answer is C. Improved scalability of the system D. Increased compartmentalization of the system. Microservices architecture improves scalability (C) because individual services can be scaled independently based on demand - you can spin up more instances of just the payment service during peak checkout traffic without touching the rest of the system. It also increases…

Submitted by naveen.iyer· Mar 6, 2026Security architecture

Question

Which of the following best describe the benefits of a microservices architecture when compared to a monolithic architecture? (Choose two.)

Options

  • AEasier debugging of the system
  • BReduced cost of ownership of the system
  • CImproved scalability of the system
  • DIncreased compartmentalization of the system
  • EStronger authentication of the system
  • FReduced complexity of the system

How the community answered

(34 responses)
  • A
    6% (2)
  • B
    3% (1)
  • C
    88% (30)
  • E
    3% (1)

Explanation

Microservices architecture improves scalability (C) because individual services can be scaled independently based on demand - you can spin up more instances of just the payment service during peak checkout traffic without touching the rest of the system. It also increases compartmentalization (D) because each service is isolated with its own codebase, data store, and deployment lifecycle, so a failure or change in one service doesn't cascade through the whole application.

The distractors fail for these reasons:

  • A (easier debugging) - the opposite is true; distributed systems introduce complex tracing and networking issues that make debugging harder.
  • B (reduced cost) - microservices typically increase infrastructure and operational costs due to orchestration, networking, and tooling overhead.
  • E (stronger authentication) - auth strength depends on implementation, not architecture style; microservices can actually complicate auth by requiring inter-service trust management.
  • F (reduced complexity) - again the opposite; microservices trade monolithic complexity for distributed system complexity.

Memory tip: Think "microservices = micro-focus" - each service focuses on one thing, so it can scale independently (C) and stay compartmentalized (D). Everything else - cost, debugging, auth, overall complexity - gets harder, not easier.

Topics

#Microservices#Monolithic architecture#System architecture#Scalability

Community Discussion

No community discussion yet for this question.

Full SY0-701 Practice