I85PREP
⌘ K
Salesforce MuleSoft Developer study materials
Salesforce MuleSoft Developer study resources

Salesforce MuleSoft Developer practice questions

One question at a time. Build your Salesforce MuleSoft Developer understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Explaining and Creating API Specifications with Anypoint Platform

In a contract-first (design-first) approach, what is the role of the API specification?

  1. It stores the compiled Mule application artifact for deployment.
  2. It records the agreed interface between API consumers and the provider. Correct answer.
  3. It defines the internal Java class hierarchy of the implementation.
  4. It holds runtime logs produced while the API processes requests.

Explanation

A specification is the machine-readable contract describing resources, methods, parameters, and payloads. Both consumers and the implementation team build against it, so changes are negotiated in the contract rather than in code.

Question 2Explaining and Creating API Specifications with Anypoint Platform

Which file extension identifies a RAML 1.0 API specification?

  1. sample.rml
  2. sample.raml Correct answer.
  3. sample.yaml
  4. sample.ramx

Explanation

RAML documents are stored with the .raml extension even though their content is YAML-based. Tooling relies on the extension to recognise the file as a RAML definition rather than a generic YAML file.

Question 3Explaining and Creating API Specifications with Anypoint Platform

Which Anypoint Platform component provides a browser-based editor for designing RAML and OpenAPI specifications?

  1. API Manager
  2. Design Center Correct answer.
  3. Access Management
  4. Runtime Manager

Explanation

Design Center hosts the API Designer, where specs are authored, validated, mocked, and published to Exchange. API Manager governs instances of deployed APIs rather than authoring contracts.

Question 4Explaining and Creating API Specifications with Anypoint Platform

RAML specifications are written using which data serialization syntax?

  1. INI
  2. CSV
  3. YAML Correct answer.
  4. XML

Explanation

RAML is a YAML-based modelling language, so indentation and key/value structure follow YAML rules. This makes the contract human-readable while remaining machine-parsable.

Question 5Explaining and Creating API Specifications with Anypoint Platform

After an API specification is published to Anypoint Exchange, what can other teams do with it?

  1. Discover, reuse, and reference it as a dependency in their projects. Correct answer.
  2. Convert it automatically into a database schema for storage.
  3. Compile it into a Java archive using the Maven plugin.
  4. Deploy it directly to CloudHub as a running application.

Explanation

Exchange is the catalogue where assets are published, versioned, and consumed by others. A published spec becomes discoverable and can be imported as a dependency into Mule projects or other fragments.

Question 6Explaining and Creating API Specifications with Anypoint Platform

Which root-level RAML property declares the base URL of the API?

  1. title
  2. version
  3. baseUri Correct answer.
  4. mediaType

Explanation

The baseUri property holds the full base URL, commonly including a version segment, to which resource paths are appended. The version property only holds the version label used in documentation and Exchange.

Question 7Explaining and Creating API Specifications with Anypoint Platform

In RAML, how is a URI parameter declared inside a resource path?

  1. with square brackets, e.g. /users/[userId]
  2. with a dollar prefix, e.g. /users/$userId
  3. with curly braces, e.g. /users/{userId} Correct answer.
  4. with angle brackets, e.g. /users/<userId>

Explanation

RAML follows the URI template convention in which variable path segments appear inside curly braces. The matching entry under the resource's uriParameters node describes the type and constraints of that variable.

Question 8Explaining and Creating API Specifications with Anypoint Platform

In RAML, which element of a method documents the HTTP status codes it can return?

  1. headers
  2. body
  3. queryParameters
  4. responses Correct answer.

Explanation

The responses node maps each status code, such as 200 or 404, to its description, headers, and payload definitions. Those documented responses are also what the mocking service uses to answer calls.

Question 9Explaining and Creating API Specifications with Anypoint Platform

An API specification documents example payloads for each response. What does the Anypoint mocking service do with them?

  1. It deploys a container running the Mule application flows.
  2. It generates Java connector code for the implementation.
  3. It validates the RAML syntax before the spec is published.
  4. It returns documented example responses without a backend. Correct answer.

Explanation

The mocking service is generated directly from the specification and replies with the examples declared in the contract. This lets consumers start integration work before any real implementation exists.

Question 10Explaining and Creating API Specifications with Anypoint Platform

Which RAML construct groups method-level properties, such as headers or query parameters, so they can be shared by several methods?

  1. a data type
  2. a library
  3. a trait Correct answer.
  4. a resource type

Explanation

Traits are declared under the root traits node and applied to a method with the is keyword. They are the mechanism for reusing cross-cutting method concerns such as pagination or correlation headers.

Question 11Explaining and Creating API Specifications with Anypoint Platform

Which RAML feature lets a designer define a reusable pattern of methods and responses that several resources can inherit?

  1. an annotation type
  2. a trait
  3. a security scheme
  4. a resource type Correct answer.

Explanation

A resource type is declared at the root and applied to a resource with the type keyword, bringing along its methods and responses. Optional methods can be marked with a question mark so each applying resource decides whether to implement them.

Question 12Explaining and Creating API Specifications with Anypoint Platform

A large RAML specification keeps the JSON schema for a request body in a separate file. Which RAML construct references that file?

  1. !reference
  2. $ref
  3. !import
  4. !include Correct answer.

Explanation

RAML uses the !include tag to pull external files, such as schemas, examples, or fragments, into the document at parse time. This keeps a single contract modular without duplicating content.

Question 13Explaining and Creating API Specifications with Anypoint Platform

Which root-level RAML property sets the default content type used for request and response bodies across the API?

  1. mediaType Correct answer.
  2. defaultMedia
  3. produces
  4. contentType

Explanation

The mediaType property at the document root declares the default MIME type, such as application/json, that applies wherever a body does not state its own type. Individual bodies can still override it.

Question 14Explaining and Creating API Specifications with Anypoint Platform

In an OpenAPI 3.0 document, where should a schema be placed so several operations can reuse it by $ref?

  1. In the tags list of each operation
  2. In the info object under a schemas key
  3. In components, under the schemas section Correct answer.
  4. In the servers array as a schema entry

Explanation

OpenAPI 3.0 collects reusable objects under the root components section, with schemas as one of its subsections. Other locations then point to them with a $ref such as #/components/schemas/Order.

Question 15Explaining and Creating API Specifications with Anypoint Platform

Which OpenAPI Specification versions can be authored in Anypoint Platform's Design Center?

  1. 2.0 and 3.0 Correct answer.
  2. 3.1 only
  3. 2.0 only
  4. 1.0 and 2.0

Explanation

Design Center supports RAML as well as OpenAPI 2.0 and OpenAPI 3.0 projects. OpenAPI 3.1 is a later revision that is not among the supported authoring options in this platform.

Question 16Explaining and Creating API Specifications with Anypoint Platform

A GET operation must accept an optional status filter that is not part of the resource path. How is it declared in the specification?

  1. As a required request header declared in the method's headers node
  2. As a URI parameter placed in curly braces in the resource path
  3. As a property inside the schema of the response body
  4. As an optional query parameter in the queryParameters node Correct answer.

Explanation

Filters that are appended to the URL after a question mark are declared as query parameters on the method, with required set to false when they are optional. URI parameters, by contrast, are segments of the path itself.

Question 17Explaining and Creating API Specifications with Anypoint Platform

Which root-level RAML section defines the security schemes that methods can require?

  1. securitySchemes Correct answer.
  2. protocols
  3. securedBy
  4. traits

Explanation

The securitySchemes section declares each mechanism, such as OAuth 2.0 or Basic Authentication, together with its settings. Methods then reference those declarations by name through the securedBy property.

Question 18Explaining and Creating API Specifications with Anypoint Platform

What does the API Console in Anypoint Exchange provide for a published API specification?

  1. Interactive, human-readable documentation generated from the spec Correct answer.
  2. A test suite that executes the deployed Mule flows
  3. A billing dashboard for API consumption
  4. A Docker image of the API ready for deployment

Explanation

The API Console renders the contract as browsable documentation, including resources, parameters, and examples. Consumers can also try requests against the mocking service from that same interface.

Question 19Explaining and Creating API Specifications with Anypoint Platform

A team must publish an updated API specification in Exchange without breaking consumers still using the current one. What should they do?

  1. Delete the asset and publish it again under a new name
  2. Copy the RAML into a Mule application project instead
  3. Publish the new specification as a new version of the asset Correct answer.
  4. Overwrite the existing asset with the same version number

Explanation

Exchange assets are versioned, so publishing a new version preserves the old one for existing consumers. Overwriting in place would silently change what dependent projects resolve.

Question 20Explaining and Creating API Specifications with Anypoint Platform

In RAML 1.0, how is a reusable object type with named, typed properties declared?

  1. With a trait that lists the property headers
  2. With a type declaration under the types section Correct answer.
  3. With the properties keyword inside a resource
  4. Only with an external JSON schema file

Explanation

RAML 1.0 introduces the types section at the root, where data types are defined with properties, types, and facets. Bodies and parameters then reference the declared type by name.

Question 21Explaining and Creating API Specifications with Anypoint Platform

A specification declares baseUri https://api.example.com/v1 and a developer enables the mocking service. Which statement is accurate?

  1. The declared baseUri is rewritten and saved in the contract.
  2. The mock needs a deployed Mule application in order to respond.
  3. The mock exposes its own URL that returns the example responses. Correct answer.
  4. Requests to https://api.example.com/v1 are proxied to the mock.

Explanation

Enabling the mocking service generates a separate mock base URL derived from the platform, which answers calls using the documented examples. The baseUri written in the contract stays as authored.

Question 22Explaining and Creating API Specifications with Anypoint Platform

A team wants to attach custom metadata, such as an internal owner name, to resources so that tooling can read it. Which RAML feature is intended for this?

  1. A library included with !include
  2. An annotation type declared under annotationTypes Correct answer.
  3. A trait applied with the is keyword
  4. A resource type with an extra method

Explanation

RAML 1.0 annotation types define custom metadata keys and their allowed values, and the annotations are then applied in parentheses on any node. This keeps extra information inside the contract without breaking the specification.

Question 23Explaining and Creating API Specifications with Anypoint Platform

In Design Center, which project type should be created to author a new REST API contract from scratch?

  1. A fragment project
  2. An API specification project Correct answer.
  3. A flow designer project
  4. A Mule application project

Explanation

An API specification project is used to design RAML or OpenAPI contracts, validate them, and publish them to Exchange. Application and fragment projects serve implementation and reuse purposes rather than contract authoring.

Question 24Explaining and Creating API Specifications with Anypoint Platform

What distinguishes a RAML library from an API fragment in Anypoint Platform?

  1. A library must be published to Exchange, while a fragment stays local.
  2. A fragment can only hold data types, while a library holds any content.
  3. A library is included from a file; a fragment is an Exchange dependency. Correct answer.
  4. A library is written in OAS, while a fragment is written in RAML.

Explanation

A RAML library is an external file pulled into a contract at design time with !include. An API fragment is a separate Design Center asset published to Exchange and consumed as a dependency by other specification projects.

Question 25Explaining and Creating API Specifications with Anypoint Platform

A RAML specification is imported from Exchange into an Anypoint Studio project that uses APIkit. What does APIkit produce?

  1. A database schema derived from the spec's data types
  2. A set of unit tests that call the mocking service
  3. A router whose flows map to the spec's resources and methods Correct answer.
  4. A CloudHub deployment configuration for each resource

Explanation

APIkit reads the contract and scaffolds a router plus generated flows, one for each resource and method combination. Incoming requests are then validated and dispatched to the matching flow.

Question 26Explaining and Creating API Specifications with Anypoint Platform

Which root-level RAML 1.0 property supplies the human-readable name of the API?

  1. mediaType
  2. version
  3. title Correct answer.
  4. baseUri

Explanation

The title property is a required root-level string that names the API for humans and appears in generated documentation. The version property identifies the API release, while baseUri and mediaType configure addressing and payload defaults.

Question 27Explaining and Creating API Specifications with Anypoint Platform

Which root-level RAML 1.0 section holds long-form prose documentation, such as usage notes, that is not tied to a single resource?

  1. traits and methods
  2. documentation Correct answer.
  3. description attached to a resource
  4. types and schemas

Explanation

The documentation section is an array of entries, each with a title and content, intended for narrative API documentation. The description property documents a specific node, while types and traits define reusable data and method behavior.

Question 28Explaining and Creating API Specifications with Anypoint Platform

In an OpenAPI 3.0 document, which object is required and carries the API title and version?

  1. paths
  2. components
  3. servers
  4. info Correct answer.

Explanation

The info object is mandatory and contains title and version, along with optional fields such as description. The paths object is also required but holds operations rather than API metadata.

Question 29Explaining and Creating API Specifications with Anypoint Platform

After an API specification is created in Design Center, which Anypoint Platform component makes the contract available for other teams to discover and consume?

  1. Runtime Manager
  2. Exchange Correct answer.
  3. Anypoint Studio
  4. API Manager

Explanation

Publishing a Design Center project creates an API asset in Exchange, where other teams can discover it and open the API Console. API Manager applies policies to deployed APIs, and Runtime Manager operates Mule runtimes.

Question 30Explaining and Creating API Specifications with Anypoint Platform

Which RAML 1.0 root-level property imports a RAML library so its traits, types, and resource types can be referenced?

  1. !include
  2. uses Correct answer.
  3. imports
  4. modules

Explanation

The uses property maps a namespace prefix to a library file, and library members are then referenced through that prefix. The !include directive splices a file's content directly into the current document instead of creating a namespace.

Question 31Explaining and Creating API Specifications with Anypoint Platform

A method must require OAuth 2.0 while the rest of the API remains public. Which RAML property is placed on that method to enforce the requirement?

  1. protocols
  2. authorization
  3. securitySchemes
  4. securedBy Correct answer.

Explanation

securedBy on a method applies one or more security schemes to that operation and overrides any root-level securedBy. The schemes themselves are declared once under securitySchemes.

Question 32Explaining and Creating API Specifications with Anypoint Platform

Which RAML 1.0 property restricts an API to HTTPS only?

  1. baseUri
  2. mediaType default
  3. protocols Correct answer.
  4. version

Explanation

The protocols property accepts an array such as [ HTTPS ] and limits the transports the API supports. The baseUri supplies the address but does not by itself restrict the allowed protocols.

Question 33Explaining and Creating API Specifications with Anypoint Platform

A RAML baseUri contains the template variable {region}. Which root-level property describes that variable?

  1. variables at the root level
  2. parameters for operations
  3. baseUriParameters Correct answer.
  4. uriParameters for resource paths

Explanation

baseUriParameters declares the parameters used in the baseUri template, including type, enum, and description. uriParameters is used for variables in resource paths, not for the base URI.

Question 34Explaining and Creating API Specifications with Anypoint Platform

In OpenAPI 3.0, which top-level array lists the base URLs where the API is available?

  1. host
  2. servers Correct answer.
  3. paths
  4. basePath

Explanation

The servers array contains objects with a url field and optional variables, replacing the Swagger 2.0 host and basePath fields. The paths object describes operations rather than server addresses.

Question 35Explaining and Creating API Specifications with Anypoint Platform

In OpenAPI 3.0, which operation-level object describes the payload a client sends to the API?

  1. security requirements
  2. responses
  3. requestBody Correct answer.
  4. parameters

Explanation

requestBody holds the content map, media types, schema, and required flag for the request payload. In Swagger 2.0 this was represented with body parameters instead.

Question 36Explaining and Creating API Specifications with Anypoint Platform

Which RAML 1.0 type property holds multiple named examples for a data type?

  1. example
  2. default value
  3. samples
  4. examples Correct answer.

Explanation

The examples property is a map of named example entries, each with a value and optional displayName or description. The singular example property supplies one unnamed sample, and default supplies a fallback value.

Question 37Explaining and Creating API Specifications with Anypoint Platform

A method must accept both JSON and XML request bodies. How is this represented in RAML 1.0?

  1. A union type that combines the JSON and XML payload definitions.
  2. A query parameter that lets the client select the media type at runtime.
  3. Separate application/json and application/xml keys under body. Correct answer.
  4. A single body key whose media type is set to application/*.

Explanation

A RAML body node is a map keyed by media type, so each supported media type gets its own key and schema. A wildcard media type is not used to declare two concrete representations.

Question 38Explaining and Creating API Specifications with Anypoint Platform

A trait declares a parameter named statusCode and uses it inside its responses section. How does a method apply that trait with the value 404?

  1. traitName: { statusCode: 404 } applied at the method level
  2. traits: { statusCode: 404 } inside the method definition
  3. is: [ traitName: { statusCode: 404 } ] Correct answer.
  4. uses: [ traitName: { statusCode: 404 } ] with the parameter inline

Explanation

A parameterized trait is applied through the is property, with a map of parameter values following the trait name. The uses property is for libraries, not for applying traits.

Question 39Explaining and Creating API Specifications with Anypoint Platform

A resource applies a resourceType that defines a get method with a 200 response. The resource itself declares a get method with a 201 response. Which response appears in the resulting specification?

  1. The specification is invalid because the method is duplicated.
  2. Only the 201 response declared on the resource. Correct answer.
  3. Only the 200 response from the resource type.
  4. Both 200 and 201 responses are merged into the get method.

Explanation

When a resource defines a method that a resourceType also defines, the resource's own method takes precedence and the resourceType method is not merged into it. Methods are inherited only when the resource does not declare them.

Question 40Explaining and Creating API Specifications with Anypoint Platform

In OpenAPI 3.0, a schema object contains a $ref alongside a description sibling. What is the result?

  1. The description overrides the referenced schema's existing description.
  2. The $ref is resolved and the sibling description is ignored. Correct answer.
  3. The document is invalid because a $ref cannot have sibling properties.
  4. The description is merged into the referenced schema.

Explanation

In OpenAPI 3.0, a $ref replaces the containing object, and sibling properties next to $ref are ignored. OpenAPI 3.1 later allows summary and description siblings, but 3.0 does not.

Question 41Deploying and Managing API Implementations

A Mule application contains an API Autodiscovery element in its main flow. What does this element associate the running application with?

  1. A dedicated load balancer, so traffic is spread across all workers
  2. An API instance in API Manager, so its policies are enforced Correct answer.
  3. A published Exchange asset, so consumers can download the RAML
  4. A connected app in Access Management, so the app can request tokens

Explanation

API Autodiscovery links a deployed implementation to an API instance that exists in API Manager in the same environment. Once the link is established, the API gateway applies the policies and governance configured for that API instance. Autodiscovery does not publish documentation, create load balancers, or grant OAuth credentials.

Question 42Deploying and Managing API Implementations

Which Anypoint Platform tool is used to start, stop, scale, and inspect the logs of an application deployed to CloudHub?

  1. API Designer
  2. Anypoint Exchange
  3. Runtime Manager Correct answer.
  4. Access Management

Explanation

Runtime Manager is the control plane for deployed applications: it handles deployments, worker or replica counts, application properties, logs, and alerts. API Designer is for authoring specifications, Exchange is a repository of assets, and Access Management handles users and permissions.

Question 43Deploying and Managing API Implementations

In API Manager, at which levels can a policy be applied to an API instance?

  1. At the API level for all resources, or narrowed to specific resources and methods Correct answer.
  2. Only at the organization level, so it covers every API at once
  3. Only at the environment level, so it covers every deployment there
  4. Only at the method level for REST APIs and at the queue level for messaging APIs

Explanation

A policy can be applied to the whole API, which affects every resource, or it can be scoped to individual resources and methods so that different operations are governed differently. Organization-wide and environment-wide application is not how API Manager policy scoping works.

Question 44Deploying and Managing API Implementations

A Rate Limiting policy rejects a request because the client exceeded its allowed quota. Which HTTP status code does the API gateway return?

  1. 503
  2. 401
  3. 400
  4. 429 Correct answer.

Explanation

When a rate limit is exceeded the gateway responds with HTTP 429, which signals that the caller has sent too many requests in the current window. A 400 indicates a malformed request, 401 indicates failed authentication, and 503 indicates an unavailable service.

Question 45Deploying and Managing API Implementations

The Client ID Enforcement policy is applied to an API instance. What must a consuming application have before the gateway accepts its requests?

  1. A contract with the API and the credentials issued for it Correct answer.
  2. An active VPN tunnel into the CloudHub virtual private cloud
  3. A platform user account with the API Consumer role assigned
  4. A local copy of the RAML downloaded from Anypoint Exchange

Explanation

Client ID Enforcement validates the client credentials presented on each request against an application that has a contract for the API in API Manager. Without a registered contract there are no valid credentials, so the gateway rejects the traffic. Roles, documentation copies, and network tunnels do not substitute for a contract.

Question 46Deploying and Managing API Implementations

Which prefix marks a property value as encrypted when the Secure Properties module is used in a Mule configuration file?

  1. vault::
  2. secure:: Correct answer.
  3. encrypted::
  4. cipher::

Explanation

Values written as secure::<encrypted value> are decrypted at runtime by the Secure Properties module using the configured encryption key. The other prefixes are not recognized by the module and would be treated as literal text.

Question 47Deploying and Managing API Implementations

An organization uses the Design, Sandbox, and Production environments. Where does the API instance that governs a production implementation live?

  1. In the Design environment, from which it is promoted automatically
  2. In Exchange, once for the whole organization
  3. In Runtime Manager, on the application's settings page
  4. In API Manager for the Production environment Correct answer.

Explanation

Each environment has its own API Manager instance with its own set of API instances and identifiers. An implementation deployed to Production is governed by the API instance registered in the Production environment, which is why the API ID used at deployment must match that environment.

Question 48Deploying and Managing API Implementations

An application runs on CloudHub 1.0 with two workers. Which change increases the number of separate Mule runtime instances processing requests?

  1. Increasing the worker size
  2. Enabling persistent queues
  3. Attaching a dedicated load balancer
  4. Increasing the number of workers Correct answer.

Explanation

Worker count determines how many runtime instances run the application, while worker size determines the CPU and memory of each instance. Persistent queues affect message durability and a load balancer affects ingress, not instance count.

Question 49Deploying and Managing API Implementations

How does the Throttling policy differ from the Rate Limiting policy?

  1. Throttling delays excess requests across the window, while rate limiting rejects them Correct answer.
  2. Throttling rejects excess requests with HTTP 429, while rate limiting queues them
  3. Throttling always applies across all clients, while rate limiting is per client application
  4. Throttling only works at the operation level, while rate limiting only at the API level

Explanation

Rate limiting accepts traffic up to a fixed count per window and returns an error for anything beyond it. Throttling instead smooths the flow by holding back excess requests so that the average rate stays within the limit, avoiding immediate rejections.

Question 50Deploying and Managing API Implementations

An API instance uses SLA-based rate limiting. What determines the limit that is applied to a particular consuming application?

  1. The length of the client secret issued to the application
  2. The priority setting chosen on the API instance
  3. The number of workers the implementation is deployed with
  4. The SLA tier of the contract the application holds with the API Correct answer.

Explanation

With SLA-based rate limiting, each tier defined on the API carries its own limits, and a client application receives the limits of the tier attached to its contract. Requests from applications with no contract, or from a tier with no capacity, are handled according to the policy defaults.