# Free Salesforce MuleSoft Integration Foundations Practice Questions

*Last updated September 2026 · https://www.certifyforce.com/mulesoft-integration-foundations-practice-exam/free-questions*

18 free MuleSoft Integration Foundations practice questions from the Certifyforce bank of 151 reviewed questions, spread across the 6 official exam sections in proportion to their weight. Each has the correct answer, an explanation, and the official documentation it was verified against.

## Identify the roles, responsibilities, and lifecycle of a integration project (17%)

### Question 1

Cumulus Financial's project plan lists "apply rate-limiting and client ID policies to the Accounts API" as an implementation-stage task because developers are already working in the code. The integration analyst says the task is in the wrong stage. Why is the analyst correct?

- A. Policies are written inside the Mule flows during testing, so they belong to a separate quality-assurance stage
- B. Policies are configured only after an API is retired, so that former consumers can no longer call the old endpoint
- C. Securing an API with policies applied at runtime is a management-stage step, separate from building the API logic
- D. Policies are part of the design stage, because the API specification must define every policy before mocking begins

**Correct answer:** C. Securing an API with policies applied at runtime is a management-stage step, separate from building the API logic

**Explanation:** MuleSoft places securing APIs by applying policies to them at runtime, along with deploying, monitoring, troubleshooting and managing, in the management stage of the lifecycle; implementation covers building and testing the logic. The design stage defines the contract and gathers feedback but does not enforce runtime policies. Policies protect live APIs, so applying them only after retirement makes no sense. MuleSoft's lifecycle has no separate quality-assurance stage, and runtime policies are applied by the management platform rather than coded into flows.

**Sources:** [What is Full Lifecycle API Management?](https://www.mulesoft.com/api/management/what-is-full-lifecycle-api-management)

### Question 2

AW Computing's integration director wants to start a DevOps practice for the MuleSoft program and asks the integration analyst where to begin building the DevOps team structure. Which first step should the analyst recommend?

- A. Start running continuous delivery right away, then align the team's goals with the business once releases speed up
- B. Measure deployment frequency and error volume before any team exists, so that the targets decide who gets hired
- C. Buy a full set of DevOps tools first, so that the team structure can be designed around what the tools support
- D. Assemble a tiger team of existing or new experts with a multidisciplinary skill set

**Correct answer:** D. Assemble a tiger team of existing or new experts with a multidisciplinary skill set

**Explanation:** MuleSoft's DevOps team structure guidance starts by assembling resources: a tiger team of existing or new experts with a multidisciplinary skill set, because people are the most important component of the equation. Tools are adopted in a later step, after the team is formed and aligned with business goals. The guidance warns against jumping into DevOps practices before aligning business goals with the team. Measuring KPIs such as deployment frequency and the volume of errors is the final, ongoing step that evaluates a team already in place.

**Sources:** [DevOps team structure](https://www.mulesoft.com/resources/api/devops-team-structure)

### Question 3

Universal Containers is building an application network to close its IT delivery gap. Central IT is writing the standard that every API placed on the network must meet so that other teams will actually reuse it. Which description of these APIs should the standard use?

- A. Discoverable and accessible, productized for reuse across projects, and managed for security and performance
- B. Built for one consuming application, so later changes made for other teams can never affect that original consumer
- C. Hidden from other teams until central IT approves each request, so that only the original project team can call them
- D. Exposing each system's raw database tables directly, so that consumers can query any data without a defined contract

**Correct answer:** A. Discoverable and accessible, productized for reuse across projects, and managed for security and performance

**Explanation:** Trailhead describes modern APIs, the building blocks of an application network, as discoverable and accessible, productized and reusable across multiple projects, and managed for security and performance; MuleSoft adds that everything posted on the network is discoverable, managed, governed and secured. An API built for a single consumer is the single-use integration that application networks replace. Hiding APIs from other teams blocks the discovery and self-service that reuse depends on. Raw table access with no defined contract skips the API abstraction, whereas Trailhead describes APIs as contracts that let systems exchange information in a secure and controlled way.

**Sources:** [Discover Application Networks (Trailhead unit)](https://trailhead.salesforce.com/content/learn/modules/application-networks-and-api-led-connectivity-in-mulesoft/discover-application-networks), [What is an application network?](https://www.mulesoft.com/api/what-is-an-application-network)

## Recognize and interpret essential integration concepts and terminology (20%)

### Question 4

AW Computing applies a Client ID Enforcement policy to its Pricing API. A partner's quoting tool will call the API. Which party must be registered in Anypoint Platform with a client ID and client secret that it sends with its calls?

- A. The ERP database behind the API, which needs credentials so the API implementation can read the price data
- B. The API implementation, which uses the credentials to authenticate itself to the partner's quoting tool
- C. The API proxy, which must present its own client ID to the partner before the partner can send requests
- D. The partner's quoting tool, which is the client application (consumer) that invokes the protected API

**Correct answer:** D. The partner's quoting tool, which is the client application (consumer) that invokes the protected API

**Explanation:** The Client ID Enforcement policy allows requests only from registered client applications: registering a client application generates a client ID and client secret, and those credentials accompany its requests to the API. The partner's quoting tool is the API client or consumer, so it holds the credentials. The API implementation and the proxy are on the providing side and do not present client credentials to the caller. Backend database credentials are a separate concern from API client identification.

**Sources:** [Client ID Enforcement Policy](https://docs.mulesoft.com/mule-gateway/policies-included-client-id-enforcement), [Configure Proxies for Your APIs](https://docs.mulesoft.com/api-manager/latest/api-proxy-landing-page)

### Question 5

A developer at Cumulus Financial designs a REST API in which the server remembers the branch a user selected in the first call, and later calls rely on that stored value instead of sending it again. The integration analyst flags the design. Which REST constraint does it break, and what is the consequence?

- A. Cacheability, because responses that depend on a stored branch can no longer be marked as cacheable or non-cacheable
- B. Uniform interface, because the stored branch prevents clients from reaching resources through unique URIs
- C. Statelessness, because each request must carry its own context, so the load balancer must pin users to one instance
- D. Layered system, because the server can no longer place load balancers or security proxies in front of the API

**Correct answer:** C. Statelessness, because each request must carry its own context, so the load balancer must pin users to one instance

**Explanation:** REST requires statelessness: the server holds no session information between requests, and every request must contain all the context needed to process it. Storing the selected branch on the server breaks this, so a load balancer must route each user back to the same instance, which creates bottlenecks and undermines horizontal scaling. Cacheability concerns whether responses declare themselves cacheable, not where client context lives. A uniform interface concerns accessing resources through URIs and standard representations. A layered system lets intermediaries such as proxies sit between client and server and is not what this design breaks.

**Sources:** [What is a REST (RESTful) API?](https://www.mulesoft.com/api/rest/what-is-rest-api), [What is REST API design?](https://www.mulesoft.com/resources/api/what-is-rest-api-design)

### Question 6

Cumulus Financial sends loan-approval messages to a partner through an API. The security team requires that nobody can read the messages in transit and that the partner can detect whether a message was altered after it was sent. Which two measures should the integration analyst recommend? Choose 2 answers.

- A. Digitally sign each message so that the partner can verify it was not modified
- B. Rate limit the API to a set number of requests per minute for each calling IP address
- C. Cache the API responses so that repeated requests return the same stored message
- D. Encrypt traffic in transit with TLS so that intercepted messages cannot be read
- E. Deploy additional replicas of the API so that one failing server does not stop processing

**Correct answers:** A. Digitally sign each message so that the partner can verify it was not modified; D. Encrypt traffic in transit with TLS so that intercepted messages cannot be read

**Explanation:** MuleSoft describes message confidentiality and integrity as core API security principles: encryption, such as TLS for data in transit, keeps intercepted messages unreadable, and digital signatures let the receiver verify a message was not modified. Rate limiting protects availability by preventing request floods such as DDoS attacks, not message secrecy. Additional replicas improve availability. Caching improves performance and does not protect confidentiality or prove integrity.

**Sources:** [Guide to Maximizing your API Security](https://www.mulesoft.com/api/security/what-is-api-security), [API Security Best Practices](https://www.mulesoft.com/api/security/best-practices)

### Question 7

Cumulus Financial's design team plans to describe its trade-event interfaces with AsyncAPI in Anypoint Design Center. An integration analyst new to MuleSoft asks what characterizes this kind of API. Which three statements are accurate? Choose 3 answers.

- A. AsyncAPI describes event-driven messaging interfaces rather than request-reply resource endpoints
- B. Channels define the destination where a message is sent or from which it is received
- C. Clients send a query to one endpoint that names exactly which fields the server should return
- D. The client must block and wait for the server's reply before it can carry on with other tasks
- E. The transport is the technology that carries the messages, such as Kafka or Anypoint MQ

**Correct answers:** A. AsyncAPI describes event-driven messaging interfaces rather than request-reply resource endpoints; B. Channels define the destination where a message is sent or from which it is received; E. The transport is the technology that carries the messages, such as Kafka or Anypoint MQ

**Explanation:** MuleSoft describes AsyncAPI as a technology-agnostic language for messaging interfaces that separates an API into events (the messages shared), channels (where messages are sent or received) and transport (the technology that carries them, such as RabbitMQ, Kafka or Anypoint MQ). Asynchronous APIs are non-blocking, so clients do not wait for a reply before continuing; blocking describes synchronous APIs. A single endpoint where clients choose the fields returned describes GraphQL.

**Sources:** [AsyncAPI Specifications](https://docs.mulesoft.com/design-center/design-async-api), [What are asynchronous APIs?](https://www.mulesoft.com/api/what-is-asynchronous-api)

## Recognize common integration problems, use cases, and technical solutions (17%)

### Question 8

Universal Containers' business intelligence team needs several years of sales, inventory and reference data pulled from distributed databases every night, reshaped and loaded into a data warehouse for next-morning reporting. No operational application needs the data in real time. Which type of integration technology is most suitable?

- A. An ETL tool that moves large volumes of data in batches into the data warehouse
- B. A GraphQL API that lets reporting clients request only the sales fields they need
- C. An enterprise service bus that delivers each sales event to subscribers as soon as it occurs
- D. An API gateway that enforces rate limits and authentication on calls to a sales API

**Correct answer:** A. An ETL tool that moves large volumes of data in batches into the data warehouse

**Explanation:** ETL tools have historically enabled business intelligence by extracting data from distributed sources, transforming it and loading it into staging areas and data warehouses, and they are optimized for moving large amounts of data in a batch-oriented manner. An ESB's strength is real-time, API-based connectivity between operational applications, which this nightly load does not need. An API gateway manages traffic to APIs but does not extract and load warehouse data. A GraphQL API helps clients fetch exactly the fields they want, but it is not a bulk data-movement technology.

**Sources:** [From ETL tools to ESBs](https://www.mulesoft.com/integration/etl-tools-vs-esb)

### Question 9

Bloomington Caregivers keeps client records in its scheduling system, its billing system and its CRM, and the three often disagree about addresses and contact details. Leadership wants one governed reference point for core client and service data that every system and team can see through a single interface. Which class of enterprise system should the integration analyst recommend?

- A. An enterprise service bus that stores each client record as it passes between systems
- B. A second CRM instance dedicated to holding the reconciled copy of every single client record
- C. A master data management solution that serves as the single source of truth for that data
- D. An ERP finance module that becomes the owner of every client address the company holds

**Correct answer:** C. A master data management solution that serves as the single source of truth for that data

**Explanation:** Master data management is the process and tooling for defining and managing an organization's master data, such as customer and product data, so it is visible and accessible through a single reference point that acts as a single source of truth. An enterprise service bus is an integration architecture that moves and transforms messages between systems; it is generally stateless and is not a system of record for client data. A second CRM instance would just add another copy that must be kept in step, which deepens the inconsistency. An ERP finance module manages accounting processes and is not designed to govern master data for every system; MuleSoft also notes that MDM depends on integration with systems such as ERP and CRM to work.

**Sources:** [What is Master Data Management (MDM)?](https://www.mulesoft.com/resources/esb/what-is-master-data-management-mdm), [What is ERP (Enterprise Resource Planning)?](https://www.mulesoft.com/integration/what-is-enterprise-resource-planning)

### Question 10

Cumulus Financial has used an ETL tool for years to load nightly data from its core databases into a data warehouse. A new project must pass account updates between operational applications, including cloud applications whose internal databases the team cannot access, within seconds of each change. Which tradeoff should the integration analyst highlight?

- A. ETL tools exchange real-time messages through a decoupled bus, so the existing tool already fits the need.
- B. ETL tools hide each application's internals behind APIs, so cloud applications are the ideal targets for them.
- C. ETL tools are batch-oriented and need deep access to each system's data, while an ESB offers real-time API-based links.
- D. An ESB is designed mainly for loading data warehouses in large batches, so it would not meet the latency target.

**Correct answer:** C. ETL tools are batch-oriented and need deep access to each system's data, while an ESB offers real-time API-based links.

**Explanation:** MuleSoft explains that ETL tools are optimized for moving large amounts of data in a batch-oriented manner and need comprehensive knowledge of each database or application, which is often impossible for cloud applications whose internals are not visible. An ESB instead provides API-based, real-time connectivity through a middle service layer that decouples applications and databases from one another. Real-time messaging through a decoupled bus describes the ESB, not the ETL tool. Batch loading of data warehouses is the traditional ETL use case, not the purpose of an ESB, and it is APIs, not ETL tools, that hide a system's internals from integration developers.

**Sources:** [From ETL tools to ESBs](https://www.mulesoft.com/integration/etl-tools-vs-esb)

## Explain the common technical complexities and patterns in integration development (18%)

### Question 11

At checkout on Cloud Kicks' web store, the shopper must not see an order confirmation until the payment processor has approved or declined the card. An integration analyst is choosing the interaction pattern for the call from the store to the payment processor. Which pattern fits?

- A. Synchronous request-reply, because the store waits for the processor's answer before continuing
- B. One-way messaging, because the store drops the payment on a queue and continues without an answer
- C. Batch, because card payments are collected through the day and then sent to the processor together
- D. Multicast, because the same payment message is copied to several processors at the same moment

**Correct answer:** A. Synchronous request-reply, because the store waits for the processor's answer before continuing

**Explanation:** In a synchronous request-reply interaction the client sends a request and waits for the server's response before moving on, and MuleSoft names payment processing as a case where an immediate response is essential. One-way messaging lets the sender continue without waiting, which would let the confirmation appear before the card is approved. Batch processing collects and processes large sets of records later, which is far too slow for a shopper waiting at checkout. Multicast delivers one message to several receivers, but the store needs one answer from one processor.

**Sources:** [What are asynchronous APIs?](https://www.mulesoft.com/api/what-is-asynchronous-api)

### Question 12

Cumulus Financial's scanning software saves statement files into a folder on a disk that is mounted locally on the Mule server. A Mule application must pick up the files and archive each one after processing. Which two File Connector capabilities should the integration analyst plan to use? Choose 2 answers.

- A. Connecting to a partner's remote SFTP server over the network with keys
- B. Listing a directory's contents and reading the files it holds on demand
- C. Exposing the folder to partners as an HTTPS endpoint with TLS
- D. Running SQL statements against the files as though they were a database
- E. Moving or renaming each processed file into an archive folder

**Correct answers:** B. Listing a directory's contents and reading the files it holds on demand; E. Moving or renaming each processed file into an archive folder

**Explanation:** File Connector manages files and folders on a locally mounted file system, and its features include reading files or listing directory contents on demand and common operations such as writing, copying, moving, renaming and deleting files, which cover pick-up and archiving. Connecting to a remote SFTP server is the job of SFTP Connector, which File Connector is designed to be consistent with but does not replace. Running SQL statements is a Database Connector capability. Serving an HTTPS endpoint is handled by HTTP Connector, not by File Connector.

**Sources:** [File Connector](https://docs.mulesoft.com/file-connector/latest/)

### Question 13

AW Computing's project manager asks why the integration team wants to write an API specification in RAML or OAS before anyone writes implementation code. What should the integration analyst explain?

- A. The specification is generated from finished code, so it is the last step and only documents the API
- B. The specification is a blueprint of the API's structure that exposes design flaws before coding
- C. The specification is needed only for SOAP services, because REST APIs are described by their URLs
- D. The specification replaces the implementation, because Mule runs the RAML or OAS file as the API

**Correct answer:** B. The specification is a blueprint of the API's structure that exposes design flaws before coding

**Explanation:** MuleSoft describes an API specification as a plan of how the API should look structurally, like a blueprint of a house, and notes that it helps isolate design flaws or problems before a line of code is written. Generating the specification from finished code is the code-first habit that design-first avoids, and it loses the early chance to fix the design. A specification is a contract that an API implementation realizes; it does not replace that implementation. RAML and OAS are specification languages for REST APIs, so they are not limited to SOAP services.

**Sources:** [Choosing a great API spec saves time and hassle](https://www.mulesoft.com/resources/api/api-spec), [Getting Started with API Designer](https://docs.mulesoft.com/design-center/design-create-publish-api-specs)

## Describe the components and benefits of Anypoint Platform for system integration (18%)

### Question 14

An integration analyst at Bloomington Caregivers is cataloging the connectors in a Mule application. It uses Salesforce Connector to update CRM records, Database Connector to run SQL queries, and LDAP Connector to reach Active Directory and retrieve user attributes. Following MuleSoft's grouping of connectors by what they connect to, how should the analyst classify LDAP Connector?

- A. As a database connector, because LDAP stores user records in relational tables queried with SQL
- B. As a template connector, because it ships with prebuilt mappings for common user attributes
- C. As a software application connector, because Active Directory is a packaged business application
- D. As a protocol connector, because it connects to an LDAP server to send and receive directory data

**Correct answer:** D. As a protocol connector, because it connects to an LDAP server to send and receive directory data

**Explanation:** MuleSoft groups connectors by whether they connect to software applications, databases or protocols, and it lists LDAP Connector under protocols: it connects to an LDAP server to access Active Directory and add, delete or read user attributes. Salesforce and SAP connectors are the software-application examples. Database Connector targets relational databases with SQL, which is not how LDAP works. Templates are a separate kind of Exchange asset, not a connector category.

**Sources:** [Anypoint Connectors Overview](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors), [Anypoint Connectors](https://www.mulesoft.com/platform/cloud-connectors)

### Question 15

Get Cloudy Consulting is coaching a client team through its first project on Anypoint Platform. The team will find existing reusable assets, create a new API specification, build and test the Mule application, then deploy and monitor it. Which mapping of project activities to Anypoint Platform components should the consultant recommend?

- A. Discover in Design Center, design in Anypoint Studio, build in Runtime Manager, deploy and monitor in Exchange
- B. Discover in Exchange, design in Runtime Manager, build in API Designer, deploy and monitor in Anypoint Studio
- C. Discover in API Manager, design in Exchange, build in Anypoint Studio, deploy and monitor in Design Center
- D. Discover in Exchange, design in API Designer, build in Anypoint Studio, deploy and monitor in Runtime Manager

**Correct answer:** D. Discover in Exchange, design in API Designer, build in Anypoint Studio, deploy and monitor in Runtime Manager

**Explanation:** MuleSoft's getting-started path uses Exchange to discover existing specifications, templates and examples, Design Center's API Designer to create and publish a new specification, Anypoint Studio to build and test the Mule application, and Runtime Manager to deploy and monitor it. Starting discovery in API Manager and designing in Exchange swaps the roles of those products, and Design Center does not deploy apps. Runtime Manager does not design specifications, and API Designer is not the tool for building Mule application flows. Design Center is not the discovery catalog, and Exchange does not monitor deployed applications.

**Sources:** [MuleSoft Documentation: The Road to Digital Transformation](https://docs.mulesoft.com/general/), [Enterprise Integration](https://www.mulesoft.com/platform/enterprise-integration)

### Question 16

Ursa Major Solar is comparing MuleSoft-hosted CloudHub with running Mule on its own servers. Which two benefits of the MuleSoft-hosted option should the integration analyst present? Choose 2 answers.

- A. It keeps every application inside the company's own trust boundary and data center network
- B. It is an elastic cloud that scales on demand without changing the apps or causing downtime
- C. It lets the operations team choose and patch the operating system on each of the servers
- D. It provides server functionality, so apps deploy without configuring a hosting environment
- E. It lets the team deploy Mule domain projects that share configurations across several apps

**Correct answers:** B. It is an elastic cloud that scales on demand without changing the apps or causing downtime; D. It provides server functionality, so apps deploy without configuring a hosting environment

**Explanation:** CloudHub is an elastic cloud: teams can start small and scale up as needs grow without changing applications or experiencing downtime, and as a complete iPaaS it provides server functionality so applications deploy without configuring a hosting environment. Domain projects that share configurations are a strategy for on-premises deployments to the same server. Keeping applications inside the company's trust boundary is the benefit of customer-hosted options such as hybrid deployments. On CloudHub, MuleSoft applies security patches as needed, so the customer does not manage the server operating system.

**Sources:** [CloudHub Overview](https://docs.mulesoft.com/cloudhub/), [Deployment Options](https://docs.mulesoft.com/runtime-manager/deployment-strategies)

## Describe the components and benefits of Anypoint Platform for API management (10%)

### Question 17

The CIO of Northern Trail Outfitters has watched years of point-to-point connections make every system change slow and risky. She asks why an application network built with API-led connectivity on Anypoint Platform would cope better with frequent change. Which explanation should the integration analyst give?

- A. Its connections are independent of one another, so changing one system never affects any consumer
- B. It is one fixed reference architecture that moves every system onto a single shared database
- C. It lets each team change its APIs freely, because central IT no longer governs what is published
- D. Its governed building blocks let services be plugged in or unplugged easily, without tight coupling

**Correct answer:** D. Its governed building blocks let services be plugged in or unplugged easily, without tight coupling

**Explanation:** Repeated point-to-point connections create a tight interlocking of applications and data, so any change has time-consuming and complex downstream consequences. An application network instead connects applications, data and devices through reusable APIs that are discoverable, managed, governed and secured; its managed and federated nature means it bends rather than breaks, and new products and services can be plugged in and unplugged easily. An application network is explicitly not an architecture but a set of building blocks on which architectures are built, and it does not require a single shared database. Central IT keeps management and governance over the services. No design guarantees that a change never affects any consumer.

**Sources:** [What is an application network?](https://www.mulesoft.com/api/what-is-an-application-network)

### Question 18

Get Cloudy Consulting's client has APIs built on several platforms: some are Mule applications, some are Node.js microservices on Kubernetes in two public clouds, and some are event-driven APIs described with AsyncAPI. The CTO wants to discover, govern and secure all of them from one place. Which approach matches this goal?

- A. Point-to-point API management, where each platform keeps its own separate gateway, catalog and policies
- B. Universal API management, which extends full lifecycle management to APIs built, run or hosted anywhere
- C. Rewrite every API as a Mule application first, because Anypoint Platform can manage only Mule-built APIs
- D. Move every API into a single on-premises data center, because API management needs one hosting environment

**Correct answer:** B. Universal API management, which extends full lifecycle management to APIs built, run or hosted anywhere

**Explanation:** Universal API management is the ability to open the scope of full lifecycle API management capabilities to APIs regardless of where they are built, the architecture in which they are implemented or the environment in which they are hosted, including protocols such as AsyncAPI and GraphQL. Keeping a separate gateway, catalog and policy set per platform is the fragmented situation that causes API sprawl. Anypoint Platform's API management is designed to manage and secure any API built and deployed anywhere, so a rewrite is unnecessary. Universal API management lets governance and discoverability operate independently of the hosting environment, so consolidating data centers is not required.

**Sources:** [What is Universal API Management?](https://www.mulesoft.com/api/management/what-is-universal-api-management), [Getting Started with API Management on Anypoint Platform](https://docs.mulesoft.com/general/learning-map-api-management)

## Related pages

- [Salesforce MuleSoft Integration Foundations practice exam](https://www.certifyforce.com/mulesoft-integration-foundations-practice-exam)
- [Practice exam packs](https://www.certifyforce.com/practice-exams)
- [Official MuleSoft Integration Foundations exam guide](https://help.salesforce.com/s/articleView?id=005298961&language=en_US&type=1)