In a service mesh, which two planes are commonly identified?

• A. Data plane and processing plane
• B. Control plane and orchestration plane
• C. Management plane and data plane
• D. Data plane and control plane

Answer: (D)

In a service mesh, traffic handling and configuration are kept separate into two planes. The data plane is the network path that actually forwards and secures the service-to-service calls, typically implemented by sidecar proxies that enforce routing, mTLS, retries, timeouts, and observability as requests flow between services. The control plane is the management brain that defines how traffic should be treated—setting routing rules, policies, and service mesh state—and pushes that configuration to the data plane so proxies can enforce it in real time. This separation—data plane for traffic enforcement and control plane for configuration and policy—is what makes a service mesh work.

Other terms like processing, orchestration, or management planes don’t capture this fundamental split between where traffic is handled versus where the rules and policies are defined and distributed, so they aren’t the standard paired concepts in a service mesh.