Refer to the exhibits. Each route in the Scatter-Gather sets the payload to the number shown in the label. Which response is returned to a web client request to the HTTP Listener?
Answer(s): C
Refer to the exhibit. What DataWeave expression transforms the conductorIds array to the XML output?
Answer(s): B
Refer to the exhibit. The Mule application’s connectors are configured with property placeholders whose values are set in the config.yaml file. What must be added to the Mule application to link the config.yaml file’s values with the property placeholders?
Refer to the exhibits -In the requestFlow an HTTP Request operation is configured to send an HTTP request with an XML payload. The request is sent to the HTTP Listener in the transformFlow. That flow transforms the incoming payload into JSON format and returns the response to the HTTP request The response of the request is stored in a target variable named theResult. What is the payload at the Logger component after the HTTP Request?
A Mule application configured with autodiscovery implements an API. Where is governance enforced for policies defined for this Mule application?
Answer(s): A
Why the correct option is AAutodiscovery registers the Mule application as an API and attaches the defined policies (e.g., rate-limiting, client-id validation) directly to the flows in that application. Governance of those policies is enforced within the same Mule application – the policies are integrated as extensions of the flows, so enforcement happens at runtime whenever the application processes a request. This design allows administrators to manage governance close to the implementation layer, ensuring that policy changes are version-controlled and scoped to the specific API implementation.Why the other options are less suitableB: In API Manager – API Manager centrally stores and manages policies, but when autodiscovery is used the policies are not administered there; they are defined inside the application and applied locally. C. In a separate API proxy application – Autodiscovery does not require a separate proxy app; the policies are attached to the existing Mule application, eliminating the need for an additional proxy layer. D. In Runtime Manager – Runtime Manager orchestrates deployment and monitoring, but governance enforcement for autodiscovered APIs occurs at runtime inside the application, not via Runtime Manager’s policy engine.
Anypoint Platform – API Manager documentation: https://docs.mulesoft.com/api-manager/overview DataWeave & API Policies – MuleSoft documentation: https://docs.mulesoft.com/api-manager/policy-reference
An API was designed in API Designer, published to Anypoint Exchange, then imported into API Manager. A Mule application implements this API and is deployed to CloudHub. API Manager manages this deployed API implementation. What is the easiest and most idiomatic (used for its intended purpose) way to enforce a Client ID Enforcement policy on this Mule application?
Technical justificationCorrect option – B: “In API Manager, apply a Client ID Enforcement policy for the API instance.”Anypoint API Manager is the runtime component that enforces policies such as Client ID, Rate-Limit, Quotas, etc. Once the API is imported and deployed, the policy can be attached directly to the API instance in the Manager UI or programmatically, providing immediate runtime enforcement without code changes. This approach follows the idiomatic MuleSoft pattern of separating design (API Designer/Exchange) from runtime governance (API Manager) . The built-in Client ID policy is pre-validated, configurable, and integrates with OAuth2 keys, making it the simplest and most native way to meet the requirement.Why the other options are less suitableA – Adding Client ID requirements in API Designer – Requirements defined in the specification only affect documentation and validation; they are not enforced at runtime unless the API Manager policy is applied. C – Custom policy coded in Studio and added to Runtime Manager – Implementing a custom policy adds unnecessary development effort, requires maintenance of custom code, and bypasses the built-in, supported policy that already solves the problem. D – Custom policy coded in Design Center and published to Exchange – Similar drawbacks as C, plus publishing a custom policy to Exchange does not automatically enforce it on the running API; the enforcement still needs to be configured in Manager.Therefore, applying the Client ID Enforcement policy directly in API Manager (Option B) is the simplest and most idiomatic method.
Client ID Enforcement policy – MuleSoft Docs API Manager Policies – MuleSoft Docs
Refer to the exhibit. How should the WHERE clause be changed to set the city and state values from the configured input parameters?
Answer(s): D
Refer to the exhibits. The Mule application does NOT define any global error handlers. The Validation component in the private flow throws an error. Which response message is returned to a web client requests to the main flow’s HTTP Listener?
Post your Comments and Discuss Salesforce Certified MuleSoft Developer exam prep with other Community members: