The fundamental principle of a microservices architecture is to structure an application as a collection of small, autonomous services. Each service is a self-contained, independently deployable artifact that encapsulates a specific business capability. This independence allows teams to develop, deploy, and scale each service without affecting others, leading to increased agility, resilience, and maintainability. This contrasts directly with monolithic architectures where the entire application is a single, tightly-coupled deployment unit.

A. This describes a monolithic architecture, where all components are packaged into a single deployment unit, which is the antithesis of the microservices approach.

B. This is the definition of a monolithic application. Microservices architecture breaks down core business capabilities into multiple, independently deployable services.

D. This is a primary drawback of a monolithic architecture. A key benefit of microservices is that a change to one service does NOT require redeploying the entire application.

---

1. MuleSoft Whitepaper, "Building a Microservices Architecture with Anypoint Platform": Page 4, Section: "What are microservices?". The document states, "Each microservice is independently deployable and scalable. This means that an individual service can be updated or rolled back if something goes wrong, without affecting other services." This directly supports the correctness of option C.

2. MuleSoft Documentation, "Microservices Architecture": In the "Characteristics of a microservices architecture" section, it lists "Independently deployable" as a key characteristic, explaining that "Each service can be modified and deployed without having to redeploy the entire application." This confirms that services are independent artifacts.

3. MuleSoft Blog, "Microservices architecture explained": Under the heading "Benefits of microservices," the article states, "Each service can be deployed, upgraded, scaled, and restarted independently of other services in the application...". This reinforces the concept of independent deployment and scaling central to option C.