Salesforce MuleSoft-Platform-Architect-I Practice Exam Questions & Answers
Salesforce MuleSoft-Platform-Architect-I Exam Details
Key details for this exam, checked against the published exam outline
- Exam Code
- MuleSoft-Platform-Architect-I
- Full Name
- Salesforce Certified MuleSoft Platform Architect
- Issuing Body
- Salesforce
- Question Format (Our Bank)
- Multiple Choice
- Delivery
- Online proctored or at a Pearson VUE test centre
- Eligibility
- No strict prerequisites
- Validity
- 2 years
- Full Question Set
- 171 questions Get All Questions
Free MuleSoft-Platform-Architect-I Practice Questions
Each question shows the correct answer and an explanation of why it is right
Question 1 Domain 6 Architecting and deploying API implementations
A Mule application exposes an API. Its HTTP Listener connector configuration uses the HTTPS protocol and has a fixed port
number written directly into it. The application is deployed to an Anypoint VPC and receives all inbound traffic through the CloudHub 1.0 Shared Load Balancer (SLB).
Which port number should be set in the HTTP Listener's connector configuration so that the Mule application correctly receives HTTPS API calls forwarded by the
SLB?
When a Mule application configured for HTTPS in an Anypoint VPC uses CloudHub 1.0's Shared Load Balancer (SLB), the application must listen on specific ports so that incoming traffic is routed correctly:
Port Requirement for SLB:
The CloudHub Shared Load Balancer for HTTPS traffic requires applications to listen on port 8092 for secure (HTTPS) communication. This port is reserved specifically for SSL traffic when SLB is used with Anypoint VPCs.
Why Option B Is Correct:
Setting the HTTP Listener's connector configuration to 8092 matches CloudHub's requirements for HTTPS through the Shared Load Balancer.
Why the Other Options Are Incorrect:
Option A (8082) is used for non-HTTPS (HTTP) traffic.
Option C (80) and Option D (443) are standard web ports but do not apply to CloudHub SLB's internal configuration for VPC routing.
Reference For more information on the Shared Load Balancer port configurations, refer to MuleSoft's documentation on CloudHub and VPC load balancer requirements.
Question 2 Domain 6 Architecting and deploying API implementations
Which layer of API-led connectivity is responsible for opening up core systems, legacy platforms, data sources and similar assets, while exposing their functionality?
Correct Answer: System Layer

The APIs used in an API-led approach to connectivity are grouped into three types:
System APIs: these typically connect to the core systems of record and act as a buffer that shields consumers from the intricacies or any changes in the underlying systems. Once they are developed, many consumers can retrieve data without needing to understand those systems, and these APIs can be reused across several projects.
Process APIs: these APIs communicate with and transform data within a single system or across multiple systems (removing data silos), and they are designed independently of both the source systems where the data originates and the target channels through which it is delivered.
Experience APIs: these are the means of reshaping data so it can be most readily consumed by its intended audience, all drawn from one common data source, instead of building separate point-to-point integrations for each channel. An Experience API is typically created using API-first design principles, where the API is shaped around the specific user experience it serves.
Question 3 Domain 7 Deploying API implementations to CloudHub
See the exhibit.
Which approach is the most effective way to break down a single end-to-end business process into a set of Experience, Process, and System APIs that work together?
A) Implement end-user application customizations within the Process API layer instead of the Experience API layer
B) Permit System APIs to expose data that is NOT presently needed by the identified Process or Experience APIs
C) Adopt a tiered model that always builds exactly one API per layer (Experience, Process, and System APIs)
D) Have a Process API orchestrate calls across multiple System APIs, but NOT call other Process APIs

Correct Answer: Permit System APIs to expose data that is NOT presently needed by the identified Process or Experience APIs.
*****************************************
>> All end-user application customizations should be placed in the Experience API layer only, not in the Process API layer.
>> A tiered approach should be used, but it is not required to build exactly one API per layer. Experience APIs may be a single API, while Process APIs and System APIs are often multiple. System APIs will almost always be multiple, since they are the smallest, most modular APIs built in front of backend systems.
>> Process APIs can call both System APIs and other Process APIs. API-led connectivity contains no anti-pattern stating that Process APIs must not call other Process APIs.
So, the correct option among those given, consistent with API-led connectivity principles, is to permit System APIs to expose data that is NOT presently needed by the identified Process or Experience APIs. This way, future Process APIs can use that data from System APIs, and the System layer APIs do not need to be modified again and again.

Get the complete MuleSoft-Platform-Architect-I question set
$20$40
Question 4 Domain 4 Designing APIs using System, Process, and Experience Layers
Which key advantages does the operating model proposed by MuleSoft for IT offer?
Correct answer:
1. Reduce the IT delivery gap
2. Satisfy business demands without increasing IT capacity
3. Ensure assets are consumed at the same pace as they are produced.
*****************************************
Question 5 Domain 4 Designing APIs using System, Process, and Experience Layers
Refer to the exhibit.
Three business processes must be implemented, and these implementations must communicate with a number of different SaaS applications.
The processes belong to separate (siloed) LOBs and are largely independent of one another, although they share a few business entities. Each LOB has a single development team and its own budget.
Given this organizational context, what is the most effective approach for choosing the API data models for the APIs that will implement these business processes while keeping data model redundancy to a minimum?
A) Develop several Bounded Context Data Models that correspond to cohesive segments of the business processes and the definitions of the business entities involved

B) Create a separate data model for each API, following established microservices and Agile API-centric practices
C) Define all API data models with XML schema to promote consistency and reuse across the organization
D) Establish one central Canonical Data Model (Enterprise Data Model) covering all data types from the three business processes, so the model stays consistent and free of redundancy
Correct Answer: Develop several Bounded Context Data Models that correspond to cohesive segments of the business processes and the definitions of the associated business entities.
*****************************************
>>The choices involving XML schema or Agile API-centric practices have no bearing on the scenario described in the question, so both are INVALID.
>>Creating an EDM (Enterprise Data Model) is neither feasible nor appropriate here, since the teams and LOBs operate in silos and pursue different initiatives and budgets. An EDM would demand intensive coordination across all teams, which is clearly unrealistic in this scenario.
Therefore, the best fit is to develop several Bounded Context Data Models that align with coherent parts of the business processes and the definitions of the associated business entities.

Question 6 Domain 9 Monitoring and analyzing application networks
Choose the accurate owner and layer pairings from the options below
The right answer is:
1. App Developers take ownership of and focus on Experience Layer APIs
2. LOB IT is responsible for and focuses on Process Layer APIs
3. Central IT is responsible for and focuses on System Layer APIs

https://blogs.mulesoft.com/biz/api/experience-api-ownership/
https://blogs.mulesoft.com/biz/api/process-api-ownership/
https://blogs.mulesoft.com/biz/api/system-api-ownership/
Question 7 Domain 6 Architecting and deploying API implementations
An API client invokes a single method from an existing API implementation, and that implementation is subsequently modified. Which modification to the API implementation would also force the API client's invocation logic to be changed?
Correct answer: C, which says a new mandatory field is introduced into the method the API client invokes
*****************************************
>> In general, API client logic has to be changed only when the API contract is broken.
>> Introducing a new method or a subordinate method into an API does not break the client, since the client can keep calling the methods it already uses. Therefore these two options are ruled out.
>> That leaves two candidates: altering the response data type and adding a new required field.
>> Changing the response data type does violate the API contract, but the question focuses on invocation logic rather than response handling logic. The client can still call the API and receive a response, although some field will come back with a different data type.
>> Adding a new required field breaks the invocation contract. This breaks the RAML or API spec agreement shared by the API consumer and the API provider, so the invocation logic of the API client must be updated as well.
Question 8 Domain 2 Establishing organizational and platform foundations
Which statement is generally NOT a role of the APIs built within the API-led connectivity framework?
Correct answer: They supply an extra resilience layer over the backend system, shielding clients from prolonged outages of those systems.
*****************************************
In API-led connectivity,
>> Experience APIs: enable innovation at the user interface level by using the underlying assets without being aware of how data is retrieved from backend systems.
>> Process APIs: aggregate data from various sources and merge it with orchestration logic to create higher level value.
>> System APIs: lessen dependency on the underlying backend systems by unlocking data from those systems in a reusable and consumable way.
However, they NEVER guarantee that they supply an extra resilience layer over the underlying backend system, shielding clients from extended failure of these systems.
https://dzone.com/articles/api-led-connectivity-with-mule
What the Salesforce MuleSoft-Platform-Architect-I Exam Covers
Exam domains verified against the Official Salesforce MuleSoft-Platform-Architect-I exam guide, last checked November 2026.
Domain 1 Explaining application network basics
7%Identify and differentiate between technologies for deploying API-led connectivity. Assign APIs to tiers according to ownership, change level, and functional focus.
Domain 2 Establishing organizational and platform foundations
10%Suggest how to establish a Center for Enablement and explain KPIs for measuring its success. Contrast Identity Management and Client Management choices.
Sample question from this domain above Q8
Domain 3 Designing and sharing APIs
10%Identify dependencies between an API, its specification, implementation, and clients. Explain creation and publication of reusable API-related assets.
Domain 4 Designing APIs using System, Process, and Experience Layers
12%Identify the right APIs to implement a business process and assign them to layers of API-led connectivity. Assign APIs based on change rate, ownership, and functional focus.
Domain 5 Governing web APIs on Anypoint Platform
17%Make the right utilization choice of API instances and environments in API Manager. Choose the right API policy to support non-functional requirements and identify changes needed to API specifications.
Domain 6 Architecting and deploying API implementations
11%Describe and utilize auto-discovery to link a web API implementation to an API instance managed with API Manager. Explain the needs of using an Anypoint Virtual Private Cloud.
Domain 7 Deploying API implementations to CloudHub
11%Describe scenarios for which Object Store should be used with CloudHub. Choose CloudHub worker sizes and configurations as appropriate.
Sample question from this domain above Q3
Domain 8 Meeting API quality goals
10%Design and differentiate between scenarios using Object Store or caching. Choose resilience strategies that help web API clients guard against failures.
Domain 9 Monitoring and analyzing application networks
12%Pinpoint the elements of Anypoint Platform that generate data for monitoring and alerting. Define the metrics collected for API invocations across all layers of API-led connectivity.
Sample question from this domain above Q6
MuleSoft-Platform-Architect-I Exam FAQ
Common questions about the exam itself
What background do I need to take the MuleSoft Platform Architect exam?
Is the Governing web APIs objective the hardest part of this exam?
How long should I study for the MuleSoft Platform Architect exam?
Can I take the MuleSoft Platform Architect exam online from home?
What score do I need to pass the MuleSoft Platform Architect exam?
What happens if I don't pass the MuleSoft Platform Architect exam on my first try?
How long does the MuleSoft Platform Architect certification stay valid?
What job title does the MuleSoft Platform Architect certification support?
Should I take the MuleSoft Developer exam before attempting the Platform Architect exam?
How does the MuleSoft Platform Architect exam differ from the Integration Architect exam?
Other Salesforce Exams
Free practice questions for more Salesforce certification exams
