Free Preparation Discussions
MENU
Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Exam Questions
- Topic 1: Explaining Application Network Basics: This topic includes subtopics related to identifying and differentiating between technologies for API-led connectivity, describing the role and characteristics of web APIs, assigning APIs to tiers, and understanding Anypoint Platform components.
- Topic 2: Establishing Organizational and Platform Foundations: Advising on a Center for Enablement (C4E) and identifying KPIs, describing MuleSoft Catalyst's structure, comparing Identity and Client Management options, and identifying data residency types are essential subtopics.
- Topic 3: Designing and Sharing APIs: Identifying dependencies between API components, creating and publishing reusable API assets, mapping API data models between Bounded Contexts, and recognizing idempotent HTTP methods.
- Topic 4: Designing APIs Using System, Process, and Experience Layers: Identifying suitable APIs for business processes, assigning them according to functional focus, and recommending data model approaches are its subtopics.
- Topic 5: Governing Web APIs on Anypoint Platform: This topic includes subtopics related to managing API instances and environments, selecting API policies, enforcing API policies, securing APIs, and understanding OAuth 2.0 relationships.
- Topic 6: Architecting and Deploying API Implementations: It covers important aspects like using auto-discovery, identifying VPC requirements, comparing hosting options, and understanding testing methods. The topic also involves automated building, testing, and deploying in a DevOps setting.
- Topic 7: Deploying API Implementations to CloudHub: Understanding Object Store usage, selecting worker sizes, predicting app reliability and performance, and comparing load balancers. Avoiding single points of failure in deployments is also its sub-topic.
- Topic 8: Meeting API Quality Goals: This topic focuses on designing resilience strategies, selecting appropriate caching and OS usage scenarios, and describing horizontal scaling benefits.
- Topic 9: Monitoring and Analyzing Application Networks: It discusses Anypoint Platform components for data generation, collected metrics, and key alerts. This topic also includes specifying alerts to define Mule applications.
Free Salesforce Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Exam Actual Questions
Note: Premium Questions for Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) were last updated On Oct. 27, 2026 (see below)
What is a key requirement when using an external Identity Provider for Client Management in Anypoint Platform?
https://www.folkstalk.com/2019/11/mulesoft-integration-and-platform.html
Correct Answe r: To invoke OAuth 2.0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider
*****************************************
>> It is NOT necessary that single sign-on is required to sign in to Anypoint Platform because we are using an external Identity Provider for Client Management
>> It is NOT necessary that all APIs managed by Anypoint Platform must be protected by SAML 2.0 policies because we are using an external Identity Provider for Client Management
>> Not TRUE that the application network must include System APIs that interact with the Identity Provider because we are using an external Identity Provider for Client Management
Only TRUE statement in the given options is - 'To invoke OAuth 2.0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider'
https://docs.mulesoft.com/api-manager/2.x/external-oauth-2.0-token-validation-policy
https://blogs.mulesoft.com/dev/api-dev/api-security-ways-to-authenticate-and-authorize/
When should idempotency be taken into account?
Understanding Idempotency:
Idempotency is a concept in APIs where an operation can be performed multiple times without changing the result beyond the initial application. This is particularly important for operations that may be repeated due to network retries or client errors.
When to Consider Idempotency:
Idempotency should be taken into account when there is a risk of duplicate processing due to multiple requests being sent (e.g., retries or errors). This ensures that repeated requests do not result in unintended side effects, such as creating multiple records or processing the same transaction more than once.
Evaluating the Options:
Option A: While locked entities may need special handling, this is not directly related to idempotency.
Option B: Storing results for future responses could be useful but does not relate to idempotent operations.
Option C: Concurrent requests for the same entity might require handling for conflicts, but this scenario is better suited for transaction management or concurrency control.
Option D (Correct Answer): Preventing duplicate processing from multiple requests is a key reason to implement idempotency, ensuring that repeat requests have no adverse effects.
Conclusion:
Option D is the correct answer as idempotency is specifically used to handle scenarios where duplicate requests might be sent, preventing unintended processing.
Refer to MuleSoft's documentation on best practices for idempotency in API design for more details.
A circuit breaker strategy is planned in order to meet the goal of improved response time and demand on a downstream API.
* Circuit Open: More than 10 errors per minute for three minutes
* Circuit Half-Open: One error per minute
* Circuit Closed: Less than one error per minute for five minutes
Out of several proposals from the engineering team, which option will meet this goal?
Understanding Circuit Breaker Policy:
A circuit breaker is a design pattern used to detect failures and prevent an application from continually trying to execute a failing operation. In this case, it will help improve response time and reduce demand on the downstream API.
The specified configuration includes conditions for opening, half-opening, and closing the circuit based on error rates over time:
Circuit Open: Triggered if there are more than 10 errors per minute for three consecutive minutes.
Circuit Half-Open: The circuit transitions to half-open if there is one error per minute.
Circuit Closed: The circuit closes if the error rate is less than one error per minute for five minutes.
Evaluating the Options:
Option A: Creating a custom policy with template expressions could work, but it would require custom development. Since the Anypoint Platform already has a Circuit Breaker policy available, this would be a less efficient and more complex solution.
Option B: Anypoint Monitoring alerts can be used for monitoring the API, but they do not provide circuit-breaking functionality. Additionally, implementing a retry strategy for the half-open state is not sufficient to achieve the required circuit breaker behavior.
Option C (Correct Answer): Adding the Circuit Breaker policy to the API instance on Anypoint Platform allows you to set up circuit-breaking conditions directly. This approach uses the built-in Circuit Breaker policy, where you can configure parameters such as error thresholds and time intervals to match the requirements. This solution is efficient, reliable, and leverages Anypoint's out-of-the-box capabilities.
Option D: Implementing the strategy within a Mule application with a YAML configuration could be complex and less manageable. Additionally, it does not leverage Anypoint Platform's built-in Circuit Breaker policy, which is more suited to this scenario.
Conclusion:
Option C is the correct choice, as it leverages Anypoint Platform's Circuit Breaker policy. This solution allows for configuring thresholds and time intervals as specified, improving response time and reducing demand on the downstream API while utilizing Anypoint's managed policy feature.
Refer to MuleSoft's documentation on implementing the Circuit Breaker policy in API Manager for detailed configuration guidance.
What is true about where an API policy is defined in Anypoint Platform and how it is then applied to API instances?
Correct Answe r: The API policy is defined in API Manager for a specific API instance, and then ONLY applied to the specific API instance.
*****************************************
>> Once our API specifications are ready and published to Exchange, we need to visit API Manager and register an API instance for each API.
>> API Manager is the place where management of API aspects takes place like addressing NFRs by enforcing policies on them.
>> We can create multiple instances for a same API and manage them differently for different purposes.
>> One instance can have a set of API policies applied and another instance of same API can have different set of policies applied for some other purpose.
>> These APIs and their instances are defined PER environment basis. So, one need to manage them seperately in each environment.
>> We can ensure that same configuration of API instances (SLAs, Policies etc..) gets promoted when promoting to higher environments using platform feature. But this is optional only. Still one can change them per environment basis if they have to.
>> Runtime Manager is the place to manage API Implementations and their Mule Runtimes but NOT APIs itself. Though API policies gets executed in Mule Runtimes, We CANNOT enforce API policies in Runtime Manager. We would need to do that via API Manager only for a cherry picked instance in an environment.
So, based on these facts, right statement in the given choices is - 'The API policy is defined in API Manager for a specific API instance, and then ONLY applied to the specific API instance'.
What best describes the Fully Qualified Domain Names (FQDNs), also known as DNS entries, created when a Mule application is deployed to the CloudHub Shared Worker Cloud?
Correct Answe r: The FQDNs are determined by the application name chosen, IRRESPECTIVE of the region
*****************************************
>> When deploying applications to Shared Worker Cloud, the FQDN are always determined by application name chosen.
>> It does NOT matter what region the app is being deployed to.
>> Although it is fact and true that the generated FQDN will have the region included in it (Ex: exp-salesorder-api.au-s1.cloudhub.io), it does NOT mean that the same name can be used when deploying to another CloudHub region.
>> Application name should be universally unique irrespective of Region and Organization and solely determines the FQDN for Shared Load Balancers.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Maria Miller
25 days agoLisa Clark
2 months agoGerald Morgan
2 months agoCarol Rogers
3 months agoThomas Wilson
3 months agoKaren Phillips
4 months agoHarold Mitchell
4 months agoGary Davis
5 months agoMelissa Lopez
5 months agoEmma Edwards
6 months agoMark Campbell
6 months agoNathan Miller
6 months agoKenneth Green
6 months agoMargaret Scott
5 months agoSarah Wright
5 months agoRonald Wilson
6 months agoAntione
7 months agoWade
7 months agoLeatha
7 months agoLashawnda
7 months agoAnabel
8 months agoRosio
8 months agoJanna
8 months agoYuriko
9 months agoSharita
9 months agoYun
9 months agoRosio
9 months agoCarlton
10 months agoKandis
10 months agoJunita
10 months agoBrandon
10 months agoCassi
11 months agoBambi
11 months agoBrock
11 months agoMing
11 months agoRosenda
12 months agoProvidencia
12 months agoLenna
1 year agoVictor
1 year agoJanet
1 year agoTrina
1 year agoErick
1 year agoJeniffer
1 year agoLeontine
1 year agoGoldie
1 year agoMose
1 year agoKirby
2 years agoLakeesha
2 years agoCandra
2 years agoBuck
2 years agoRomana
2 years agoTonette
2 years agoLouisa
2 years agoDenae
2 years agoHelga
2 years agoErick
2 years agoMollie
2 years agoAlaine
2 years agoFidelia
2 years agoMelinda
2 years agoFidelia
2 years agoTherese
2 years agoBoris
2 years agoRolland
2 years agoBeckie
2 years agoLai
2 years agoWenona
2 years agoIlene
2 years agoSophia
2 years agoCarry
2 years agoRoxanne
2 years agoSylvia
2 years agoMattie
2 years agoJacinta
2 years agoAntonio
2 years agoIlene
2 years ago