Mule-Dev-301 sample questions

Question 1

A MuleSoft Architect is designing a versioning strategy for a suite of System APIs that connect to a legacy mainframe. The business requirement dictates that existing consumers must not be forced to update their integrations immediately when minor non-breaking changes are deployed. However, major breaking changes must run in parallel with the old version. Which URI-based versioning strategy in the RAML definition and API implementation best supports these requirements while adhering to semantic versioning principles?

Accepted Answer

Include only the major version in the base URI (e.g., /api/v1/customers) and handle minor updates in the implementation logic without changing the URI.

Answer

Include the full semantic version in the base URI (e.g., /api/v1.0.1/customers) to ensure strict client coupling to specific builds.

Answer

Use a custom HTTP header 'X-API-Version' to route requests to the correct flow within a single Mule application deployment.

Answer

Define the version as a query parameter (e.g., ?version=v1) to allow caching policies to differentiate responses based on the parameter.

Question 2

A developer is configuring API Auto-Discovery for a Mule application deployed to CloudHub. The API is managed in API Manager, and the correct Client ID and Secret have been configured in the `AnyPoint Platform` properties. However, the API status remains 'Unregistered' in API Manager. Upon reviewing the logs, the developer sees the application has started successfully. What is the most likely cause of this issue?

Accepted Answer

The `api-gateway:autodiscovery` global element is missing the `flowRef` attribute pointing to the main API flow.

Answer

The API instance in API Manager is not set to 'Public'.

Answer

The `apiId` in the auto-discovery configuration matches the Asset ID instead of the API Instance ID.

Answer

The deployment property `anypoint.platform.base_uri` is pointing to the wrong control plane region.

Question 3

An organization requires strict governance where an API must automatically reject requests if they exceed 100 requests per minute from a specific client ID. However, brief bursts of traffic up to 50% above the limit are acceptable for short durations (milliseconds) to accommodate network jitter. Which out-of-the-box API policy should be applied to meet this requirement?

Accepted Answer

Spike Control

Answer

Rate Limiting - SLA Based

Answer

Rate Limiting

Answer

Client ID Enforcement

Question 4

A banking application exposes a webhook endpoint that receives transaction notifications from a third-party payment provider. To ensure the integrity and authenticity of the notifications, the provider signs the payload using HMAC-SHA256. Which implementation strategy correctly validates this signature in the Mule application?

Accepted Answer

Use the Crypto module to calculate the HMAC-SHA256 hash of the raw payload using the shared secret, then compare the result with the signature header provided by the webhook.

Answer

Configure a Client ID Enforcement policy and map the signature header to the Client Secret field.

Answer

Use the Validation module's 'Is True' operation to check if the payload contains the signature string.

Answer

Decode the signature header using Base64 and compare it directly to the JSON payload.

Question 5

A developer is configuring an API Policy to implement server-side caching for a System API. The API returns customer details based on a `customerId` query parameter and an `Accept-Language` header. To ensure the cache returns the correct localized data for the specific customer, how should the cache key be configured?

Accepted Answer

#[attributes.queryParams.customerId ++ '-' ++ attributes.headers['Accept-Language']]

Answer

#[attributes.queryParams.customerId]

Answer

#[attributes.requestPath]

Answer

#[authentication.principal]

Question 6

A developer is creating a Mule application that uses a custom library (JAR) containing a set of reusable DataWeave modules. This library is used across multiple applications in the organization. The developer notices that when the library is updated, consumers are not picking up the changes during their build process despite the version number remaining `1.0.0-SNAPSHOT`. What is the correct Maven configuration in the consumer application's `pom.xml` to ensure snapshot updates are checked daily?

Accepted Answer

Configure the ` ` element for the snapshot repository with ` true daily `.

Answer

Add the `-U` flag to the MUnit test execution command.

Answer

Increment the consumer application's version to force a dependency refresh.

Answer

Change the dependency scope to `provided`.

Top vendors

Top exams

Free Mule-Dev-301 sample questions

6 more free samples are waiting