Initiating integration solutions on the Anypoint Platform8% of the exam

Control plane and runtime plane deployment options

Choose a control plane (MuleSoft-managed clouds, Government Cloud, Private Cloud Edition) and a compatible runtime plane (CloudHub 2.0, CloudHub, Runtime Fabric, hybrid standalone), and know who operates each part, including Runtime Fabric's shared-responsibility model.

Official exam objective
Select deployment options of the Anypoint Platform control plane and runtime plane.

~7 min read · 8 practice questions

What the exam expects

  • Choose a control plane from the MuleSoft-managed clouds, Government Cloud, Government Cloud Plus and Private Cloud Edition (PCE) given data-residency and compliance constraints.
  • Confirm that a chosen runtime plane is supported from the chosen control plane.
  • Select Runtime Fabric, hybrid standalone, CloudHub or CloudHub 2.0 from infrastructure, isolation, runtime-version and operations requirements.
  • Assign responsibilities correctly: what MuleSoft provides and what the customer operates for Runtime Fabric and hybrid runtimes.

Control plane: the management layer where you design, deploy and manage APIs and Mule apps, holding the organization, identity and design-time metadata. Runtime plane: where APIs and Mule apps are deployed, including the Mule runtime engine and supporting services. Cloud: a regional MuleSoft-managed control plane, such as US Cloud. Runtime Fabric: a MuleSoft product for deploying Mule apps and API proxies to a Kubernetes cluster that you create, configure and manage. Hybrid standalone runtime: a Mule runtime on your infrastructure managed from the control plane (Hosting overview, Runtime Fabric).

Sources for this section (2)

Key facts

Organization placement
Detail
Each organization lives in exactly one cloud.
Government Cloud runtimes
Detail
CloudHub and hybrid standalone; not CloudHub 2.0 or Runtime Fabric.
PCE runtimes
Detail
Hybrid standalone only.
Regional clouds
Detail
Canada, Japan, India, Australia, UK: no CloudHub 1.0.
Runtime Fabric isolation
Detail
One Mule runtime per app; several runtime versions on shared resources.
Agent connection
Detail
Outbound mTLS to the control plane, opened at startup.
Node OS
Detail
Linux required on nodes running Runtime Fabric components.
Core services
Detail
Do not multiply as applications or nodes increase.
Ingress
Detail
Customer provides the ingress controller and external load balancing.
Hybrid patching
Detail
Apply security updates for the runtime version manually.
Sources for this section (3)
  • When does an on-premises Mule runtime become a hybrid standalone runtime?
  • Which Runtime Fabric core service lets Mule applications discover their peers in the cluster?
  • Why does the Runtime Fabric agent report application state without the control plane asking?
  • Which Java versions do the CloudHub 2.0 and CloudHub deployment options list?

The questions are free to read. Answers with their sources and self-grading are included with the pack.

Keep reading with the MuleSoft Platform Integration Architect pack

  • Core concepts
  • Exam traps
  • Worked scenario

The pack includes:

  • All 40 lessons of the MuleSoft Platform Integration Architect guide, with reading progress
  • Interactive decision walks and step-by-step sequence steppers
  • Practice exams purchase adds inline bank questions and topic practice (8 questions for this lesson)
  • An official source cited for every claim
  • An AI tutor that answers from the guide
  • Choose guide-only, practice-only, or save $4 with both

Practice for the MuleSoft Platform Integration Architect exam