VendorsExamsEnterprise
Support
Request an ExamContact UsFAQ

Salesforce Certified MuleSoft Developer II Free Sample Questions

Description

Covers exposing production-ready APIs, modular Mule applications and Maven builds, health checks and logging, fault-tolerant messaging, and securing data at rest and in transit.

12 free sample questions180 in the full practice test Other version: certified-mulesoft-developer-ii(34)

Try simulator

Mule-Dev-301 Sample Questions

  1. Question 1

    Intermediate

    Expose Production-Ready Anypoint Platform-Managed APIs from Mule Applications · Implement versioning of specific API-related artifacts

    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?

    Answer and explanation

    Correct answer: B

    According to semantic versioning best practices for APIs, the URI should typically contain only the MAJOR version (v1). Minor and patch versions (v1.1, v1.2) should be backward compatible and thus should not require a URI change. This allows existing consumers to benefit from non-breaking changes without modification, while breaking changes trigger a new major version (v2) deployed in parallel.

  2. Question 2

    Intermediate

    Expose Production-Ready Anypoint Platform-Managed APIs from Mule Applications · Code API implementations to perform API auto-discovery

    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?

    Answer and explanation

    Correct answer: C

    For API Auto-Discovery to function, the api-gateway:autodiscovery element must reference the specific flow (usually the one containing the APIkit Router or HTTP Listener) via the flowRef attribute. Without this link, the runtime cannot associate incoming traffic on that flow with the managed API instance, resulting in an 'Unregistered' status even if credentials and API IDs are correct.

  3. Question 3

    Intermediate

    Expose Production-Ready Anypoint Platform-Managed APIs from Mule Applications · Configure custom or out-of-the-box (OOTB) API policies

    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?

    Answer and explanation

    Correct answer: B

    Spike Control is designed to smooth out traffic bursts. Unlike Rate Limiting (which hard-stops traffic over a window), Spike Control uses a sliding window algorithm and allows queuing of requests or configurable burst windows. It is the correct choice when 'brief bursts' need to be accommodated rather than immediately rejected, or when protection against sudden load spikes is priority over strict quota enforcement.

  4. Question 4

    Advanced

    Expose Production-Ready Anypoint Platform-Managed APIs from Mule Applications · Implement HTTP callbacks (webhooks)

    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?

    Answer and explanation

    Correct answer: B

    To validate an HMAC signature, the receiver must independently compute the hash of the received message body using the pre-shared secret key and the specified algorithm (HMAC-SHA256). This computed hash is then compared against the signature sent in the HTTP header. If they match, the message is authentic and unmodified.

  5. Question 5

    Intermediate

    Expose Production-Ready Anypoint Platform-Managed APIs from Mule Applications · Implement server-side caching of API invocations using API policies

    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?

    Answer and explanation

    Correct answer: C

    The cache key must uniquely identify the resource representation. Since the response varies by both customerId (content) and Accept-Language (localization), both values must be part of the key expression. Concatenating them ensures that a request for Customer A in English does not return cached data for Customer A in Spanish or Customer B.

  6. Question 6

    Advanced

    Implement Maintainable and Modular Mule Applications and Their Maven Builds · Modularize and optimize Mule application Maven build configurations

    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?

    Answer and explanation

    Correct answer: C

    In Maven, SNAPSHOT dependencies are mutable. By default, Maven might not check for updates frequently. Explicitly configuring the updatePolicy to daily (or always) inside the element of the repository declaration forces Maven to check the remote repository for a newer timestamped version of the SNAPSHOT artifact.

Register free for 6 more questions

Or unlock all 180 Mule-Dev-301 questions with explanations, timed mode and flashcards.

Related practice tests

All Salesforce practice exams