Salesforce MuleSoft Developer I Exam Practice Test Instant Access

Question 1

Refer to the exhibits.

The Batch Job scope processes the array of strings

After the Batch Job scope completes processing the input payload what information is logged by the Logger component?

AOption A

BOption B

COption C

DOption D

Answer : C

Question 2

An API instance of type API endpoint with API proxy is created in API manager using an API specification from Anypoint Exchange. The API instance is also configured with an API proxy that is deployed and running in CloudHub.

An SLA- based policy is enabled in API manager for this API instance.

Where can an external API consumer obtain a valid client ID and client secret to successfully send requests to the API proxy?

AIn the organization's public API portal in Anypoint Exchange, from an approved client application for the API proxy

BIn Anypoint Studio, from components generated by APIkit for the API specification

CIn Anypoint Studio, from components generated by Rest Connect for API specification

DIn Runtime Manager, from the properties tab of the deployed approved API proxy

Answer : A

* When a client application is registered in Anypoint Platform, a pair of credentials consisting of a client ID and client secret is generated.

* When the client application requests access to an API, a contract is created between the application and that API.

* An API that is protected with a Client ID Enforcement policy is accessible only to applications that have an approved contract.

---------------------------------------------------------------------------------------------------------------------------------------------

Correct Answer: In the organization's public API portal in Anypoint Exchange, from

Question 3

Refer to the exhibits. Client sends the request to ClientRequestFlow which calls ShippingFlow using HTTP Request activity.

During E2E testing it is found that that HTTP:METHOD_NOT_ALLOWED error is thrown whenever client sends request to this flow.

What attribute you would change in ClientRequestFlow to make this implementation work successfully?

AChange the method attribute value to '*''

BChange the path attribute value to '/api/ship'

CChange the allowed method attributes value to 'POST'

DChange the protocol attribute value to 'HTTPS'

Answer : C

Correct answer is Change the method attributes value to 'POST'.

It can be fixed in either of the two ways as below.

1) Changing method attribute to POST in ClientRequestFlow

2) Setting allowedMethods as PUT in ShippingFlow (but doesn't fit as question mentions about changing ClientRequestFlow)

Question 4

An organization is beginning to follow Mulesoft's recommended API led connectivity approach to use modern API to support the development and lifecycle of the integration solutions and to close the IT delivery gap.

What distinguishes between how modern API's are organized in a MuleSoft recommended API-led connectivity approach as compared to other common enterprise integration solutions?

AThe API interfaces are specified as macroservices with one API representing all the business logic of an existing and proven end to end solution

BThe API interfaces are specified at a granularity intended for developers to consume specific aspect of integration processes

CThe API implementation are built with standards using common lifecycle and centralized configuration management tools

DThe APIO implementations are monitored with common tools, centralized monitoring and security systems

Answer : B

Correct answer is The API interfaces are specified at a granularity intended for developers to consume specific aspect of integration processes

Question 5

Following Mulesoft's recommended API-led connectivity approach , an organization has created an application network. The organization now needs to create API's to transform , orchestrate and aggregate the data provided by the other API's in the application network. This API should be flexible enought ot handle the data from additional API's in future.

According to Mulesoft's recommended API-led connectivity approach , what is the best layer for this new API?

AProcess layer

BSystem layer

CExperience layer

DData layer

Answer : A

Correct answer isprocess layeras all the orchestration and transformation logic should be in process layer as per Mulesoft's recommended approach for API led connectivity.

API-led connectivity is a methodical way to connect data to applications through reusable and purposeful APIs. These APIs are developed to play a specific role -- unlocking data from systems, composing data into processes, or delivering an experience.

What are the APIs that enable API-led connectivity?

API-led connectivity provides an approach for connecting and exposing assets. With this approach, rather than connecting things point-to-point, every asset becomes a managed API -- a modern API, which makes it discoverable through self-service without losing control.

The APIs used in an API-led approach to connectivity fall into three categories:

System APIs-- these usually access the core systems of record and provide a means of insulating the user from the complexity or any changes to the underlying systems. Once built, many users, can access data without any need to learn the underlying systems and can reuse these APIs in multiple projects.

Process APIs-- These APIs interact with and shape data within a single system or across systems(breaking down data silos)and are created here without a dependence on the source systems from which that data originates, as well as the target channels through which that data is delivered.

Experience APIs-- Experience APIs are the means by which data can be reconfigured so that it is most easily consumed by its intended audience, all from a common data source, rather than setting up separate point-to-point integrations for each channel. An Experience API is usually created with API-first design principles where the API is designed for the specific user experience in mind.

Question 6

A company has defined two RAML fragments, Book Data Type and Book Example to be used in APIs.

What would be valid RAML to use these fragments ?

A1. #%RAML 1.0
2. title: Books
3. types:
4. Book: ABC/Examples/bookDataType.raml
5. /books:
6. post:
7. body:
8. application/json:
9. type: Book
10. examples:
11. input: ABC/Examples/bookExample.raml
12. responses:
13. 201:
14. body:
15. application/json:
16. example:
17. message: Book added

B1. #%RAML 1.0
2. title: Books
3. Book: !include bookDataType.raml
4. /books:
5. post:
6. body:
7. application/json:
8. type: Book
9. examples:
10. input: !include bookExample.raml
11. responses:
12. 201:
13. body:
14. application/json:
15. example:
16. message: Book added

C1. #%RAML 1.0
2. title: Books
3. Book: bookDataType.raml
4. /books:
5. post:
6. body:
7. application/json:
8. type: Book
9. examples:
10. input: bookExample.raml
11. responses:
12. 201:
13. body:
14. application/json:
15. example:
16. message: Book added

D1. #%RAML 1.0
2. title: Books
3. Book: bookDataType.raml
4. /books:
5. post:
6. body:
7. application/json:
8. type: Book
9. examples:
10. input: bookExample.raml
11. responses:
12. 201:
13. body:
14. application/json:
15. example:
16. message: Book added

Answer : D

* RAML file contains lot of information that could be considered as 'not API-describing'. Sort of 'economy-class' members.

Equally important, but not necessarily part of the main RAML file.

* Through !includes, RAML allows us to build file-distributed API definitions, which is not only useful to encourage code reuse but also improves readability.

* We can create RAML fragments with such code and then include them in main RAML project using !include like:

types:

Book: !include bookDataType.raml and

examples:

input: !include bookExample.raml

* Additionally for

----------------------------------------------------------------------------------------------------------------------------------------

Correct Answer: D

Question 7

Refer to the exhibits.

Larger image

The Mule application configures and uses two HTTP Listener global configuration elements.

Mule application is run in Anypoint Studio.

If the mule application starts correctly, what URI and port numbers can receive web client requests? If the mule applications fails to start , what is the reason for the failure?

AThe mule application fails to start
There is URL path conflict because both HTTP Listeners are configured with same path

BThe mule application start successfully
Web client requests can only be received at URI on port 2222 but not on port 3333

CThe mule application fails to start because of the port binding conflict as HTTP request also use same port i.e. 3333

DThe mule application start successfully
Web client requests can be received at URI on port 2222 and on port 3333.

Answer : D

In this case both the flows can start without any error and requests can be received on both ports. Flow names httpListener1 can call other flow using HTTP request without any issues.

Hence correct answer is

The mule application start successfully

Web client requests can be received at URI on port 2222 and on port 3333.

Lets check why other options are incorrect

1) The mule application fails to start. There is URL path conflict because both HTTP Listeners are configured with same path ---- This is incorrect as port value is different in both listeners

2) The mule application start successfully. Web client requests can only be received at URI on port 2222 but not on port 3333 --- This is incorrect as there is no reason for not receiving requests on port 3333

3) The mule application fails to start because of the port binding conflict as HTTP request also use same port i.e. 3333 --- Port binding conflict will not happen in this case. It would have if both listener configurations would have been on same port . But that is not the case here.

Mule Ref Doc :HTTP Listener Reference - Mule 4 | MuleSoft Documentation

Salesforce MuleSoft Developer I Salesforce Certified MuleSoft Developer I Exam Practice Test