Establishing organizational and platform foundations10% of the exam
Data Residency Across Platform Services
Trace payloads, metadata, logs, metrics and persistent state to their actual service locations, including the effects of regional moves, failover and log lifecycle changes.
Identify data residency of different kinds of data (payload, metrics, and others).
~8 min read · 7 practice questions
What the exam expects
- Identify locations separately for payloads, management metadata, telemetry and stored state.
- Explain why moving an application does not necessarily relocate its dependencies.
- Assess residency implications of regional failover and monitoring subscriptions.
- Distinguish cloud Object Store storage from Runtime Fabric Persistence Gateway.
Residency identifies where data is stored or processed; payload is application business content; telemetry describes operation; metadata describes managed resources; persistent state survives the relevant application execution (Hosting overview, Monitoring overview).
Sources for this section (2)
Key facts
Control-plane data
- Detail
- Organization, identity and design metadata belong to management.
Existing Object Store
- Detail
- An application-region move does not relocate its original store.
Separate instances
- Detail
- Monitoring data is not shared between Platform instances.
Advanced/Titanium
- Detail
- Log and metric storage follows the control-plane region.
Subscription change
- Detail
- Preserve required logs before the documented storage-clearing change.
MQ fallback
- Detail
- Standard-queue failover can place data outside the primary country.
Fabric persistence
- Detail
- The configured PostgreSQL database stores persistent values.
Application deletion
- Detail
- Monitoring logs can remain after Runtime Manager deletes the app.
Searchable deletion
- Detail
- Whole indices can cover more dates than requested.
Sources for this section (6)
- Hosting overviewdocs.mulesoft.com (opens in a new tab)
- Object Store FAQdocs.mulesoft.com (opens in a new tab)
- Monitoring overviewdocs.mulesoft.com (opens in a new tab)
- Monitoring FAQdocs.mulesoft.com (opens in a new tab)
- MQ failoverdocs.mulesoft.com (opens in a new tab)
- Persistence Gatewaydocs.mulesoft.com (opens in a new tab)
- When application deletion leaves required Monitoring logs retained for an Advanced subscriber, what documented route can retrieve them?
- Why might searchable-log deletion on Hyperforce affect dates outside the requested interval?
- When reviewing a proposed sensitive-log deletion, what evidence does MuleSoft provide before execution?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Platform Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 47 lessons of the MuleSoft Platform Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (7 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