2025 Realistic Salesforce-MuleSoft-Developer-I 100% Pass Guaranteed Download Exam Q&A
Accurate Salesforce-MuleSoft-Developer-I Answers 365 Days Free Updates
Salesforce Salesforce-MuleSoft-Developer-I Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
| Topic 6 |
|
NEW QUESTION # 91
A RAML specification is defined to manage customers with a unique identifier for each customer record. What URI does MuleSoft recommend to uniquely access the customer identified with the unique ID 1234?
- A. /customers/custid=1234
- B. /customers?operation=get&custid=1234
- C. /customers/1234
- D. /customers?custid=true&custid=1234
Answer: C
Explanation:
URI parameter (Path Param) is basically used to identify a specific resource or resources . For eg : the URL to get employee details on the basis of employeeID will be GET /employees/{employeeID} where employees is resource and {employeeID} is URI parameter. Hence option 1is the correct answer
NEW QUESTION # 92
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?
- A. The API interfaces are specified as macroservices with one API representing all the business logic of an existing and proven end to end solution
- B. The API implementation are built with standards using common lifecycle and centralized configuration management tools
- C. The API interfaces are specified at a granularity intended for developers to consume specific aspect of integration processes
- D. The APIO implementations are monitored with common tools, centralized monitoring and security systems
Answer: C
Explanation:
Correct answer is The API interfaces are specified at a granularity intended for developers to consume specific aspect of integration processes
NEW QUESTION # 93
What does C4E stands for in MuleSoft recommended IT operating model?
- A. Centre for Enablement
- B. Centre for Engagement
- C. Centre for Empowerment
- D. Centre for Excellence
Answer: A
Explanation:
Centre for Enablement (C4E) is an IT operating model that enables an enterprise to build reusable assets, accumulate API's, leverage best practices and knowledge to enable self service and efficient delivery in the organization and implement new solutions faster
NEW QUESTION # 94
According to MuleSoft. what is the first step to create a Modern API?
- A. Gather a list of requirements to secure the API
- B. Create a prototype of the API implementation
- C. Create an API specification and get feedback from stakeholders
- D. Performance tune and optimize the backend systems and network
Answer: C
Explanation:
First step in creating Modern API is to create an API specification and get feedback from stakeholders so that any future issues can be identified at early stage thereby reducing overall delivery time
NEW QUESTION # 95
An API was designed in API Designer, published to Anypoint Exchange, then imported into API Manager.
A Mule application implements this API and is deployed to CloudHub. API Manager manages this deployed API implementation.
What is the easiest and most idiomatic (used for its intended purpose) way to enforce a Client ID Enforcement policy on this Mule application?
- A. In API Manager, apply a Client ID Enforcement policy for the API instance
- B. In Anypoint Studio, code a custom policy tor Client ID Enforcement and then add the custom policy to Runtime Manager for the Mule application deployment
- C. In API Designer, add Client ID Enforcement policy requirements to the API specification
- D. In Anypoint Design Center, code a custom policy for Client ID Enforcement and then publish the custom policy to the API portal in Anypoint Exchange
Answer: A
NEW QUESTION # 96
What execution model is used by For Each and Batch Job scopes?
- A. For Each is single-threaded and Batch Job is multi-threaded
- B. Batch Job is single-threaded and For Each Is multi-threaded
- C. Both are single-threaded
- D. Both are multi-threaded
Answer: A
NEW QUESTION # 97
Refer to the exhibits.
As a mulesoft developer, what you would change in Database connector configuration to resolve this error?
- A. Configure the correct host URL
- B. Configure the correct JDBC driver
- C. Configure the correct table name
- D. Configure the correct database name
Answer: B
Explanation:
Correct answer is Configure the correct JDBC driver as error message suggests the same Caused by: java.sql.SQLException: Error trying to load driver: com.mysql.jdbc.Driver : Cannot load class 'com.mysql.jdbc.Driver': [ Class 'com.mysql.jdbc.Driver' has no package mapping for region 'domain/default/app/mule_app'., Cannot load class 'com.mysql.jdbc.Driver': [
NEW QUESTION # 98
A Mule project contains a DataWeave module like WebStore.dwl that defines a function named loginUser. The module file is located in the project's src/main/resources/libs/etl folder.
What is correct DataWeave code to import all of the WebStore.dwl file's functions and then call the loginUser function for the login "[email protected]"?
- A. 1. 1. import libs.etl
2. 2. ---
3. 3. WebStore.loginUser("[email protected]") - B. 1. 1. import * from libs::etl::WebStore
2. 2. ---
3. 3. loginUser("[email protected]") - C. 1. 1. import * from libs::etl
2. 2. ---
3. 3. WebStore::loginUser("[email protected]") - D. 1. 1. import libs.etl.WebStore
2. 2. ---
3. 3. loginUser("[email protected]")
Answer: B
Explanation:
* To use custom modules, you need to import the module or functions you want to use by adding the import directive to the head of your DataWeave script, for example:
1) Does not identify any functions to import from the String module:
import dw::core::Strings
2) To identify a specific function to import from the String module:
import camelize, capitalize from dw::core::Strings
3) To import all functions from the String module:
import * from dw::core::Strings
The way you import a module impacts the way you need to call its functions from a DataWeave script. If the directive does not list specific functions to import or use * from to import all functions from a function module, you need to specify the module when you call the function from your script.
* In given scenario, it's mentioned to import all of the WebStore.dwl
So correct answer is:
NEW QUESTION # 99
Refer to the exhibits.
Set paylaod transformer is set the firstName and lastName of the customer as shown in below images.
What is the correct Dataweave expression which can be added in message attribute of a Logger activity to access firstName (which in this case is Madhav) from the incoming event?
- A. customer.firstName
- B. vars."customer"."firstName"
- C. vars."customer.firstName"
- D. firstName
Answer: B
Explanation:
Correct answer is vars."customer"."firstName"
Please note that you can also access firstName using this syntax vars.customer.firstName.
Mule Ref Doc : Variables in Mule Apps | MuleSoft Documentation
NEW QUESTION # 100
What should this endpoint return? http://dev.acme.com/api/patients?name=John&surname=Bell
- A. Patient with surname as bell
- B. Patients with either name as John or surname as Bell
- C. Patients with name as John and surname as Bell
- D. Patient with name as John
Answer: C
Explanation:
Query parameters are a defined set of parameters attached to the end of a url. They are extensions of the URL that are used to help define specific content or actions based on the data being passed. To append query params to the end of a URL, a '?' Is added followed immediately by a query parameter.
To add multiple parameters, an '&' is added in between each.
Hence coming back to question, endpoint would return Patients with name as John and (and is very important here) surname as Bell
NEW QUESTION # 101
Refer to the exhibits. In the color flow , both the variable named color and payload are set to "red".
An HTTP POST request is then sent to the decideColor flow's HTTP Listener.
What is the payload value at the Logger component after the HTTP request completes?
- A. white
- B. Error message
- C. blue
- D. red
Answer: C
NEW QUESTION # 102
Where are values of query parameters stored in the Mule event by the HTTP Listener?
- A. Payload
- B. Inbound Properties
- C. Variables
- D. Attributes
Answer: D
Explanation:
Correct answer is Attributes.
Query parameters , URI parameters and headers are some of examples which are part of attributes.
Bottom of Form
Top of Form
NEW QUESTION # 103
Refer to the exhibits.
What is valid text to set the field in the Database connector configuration to the username value specified in the config.yaml file?
- A. ${db:username>
- B. #[db.username]
- C. #[db:username]
- D. ${db.username>
Answer: D
Explanation:
option 3 is the correct syntz to access application properties
NEW QUESTION # 104
Refer to the exhibit.
What is the correct syntax to add an employee ID as a URI parameter in an HTTP Listener path?
- A. ${emp!oyeelD}
- B. (employeelD)
- C. {employeelD}
- D. # [employeelD]
Answer: C
Explanation:
Paths
The path of an HTTP listener can be static, which requires exact matches, or feature placeholders. Placeholders can be wildcards (*), which match against anything they are compared to, or parameters ({param}), which not only match against anything but also capture those values on a URI parameters map.
Take the following example paths for three listeners using a configuration that establishes api/v1 as the base path:
account/mulesoft/main-contact: only match the exact path request http://awesome-company.com/api/v1/account/mulesoft/main-contact account/{accountId}/main-contact: matches all path requests structured similarly, such as http://awesome-company.com/api/v1/account/salesforce/main-contact, and save salesforce as the value of accountId.
account/{accountId}/*: matches all path requests different from main-contact, such as http://awesome-company.com/api/v1/account/mulesoft/users, and save mulesoft as the value of accountId.
Mule Ref Doc : https://docs.mulesoft.com/http-connector/1.6/http-listener-ref#paths
NEW QUESTION # 105
What valid RAML retrieves details on a specific customer by its customerId as a URI parameter?
- A. 1. /customers:
2. get:
3. /{customerId}: - B. 1. /customers:
2. /{customerId}:
3. get: - C. 1. /customers:
2. /customerId:
3. get: - D. 1. /customers:
2. /get:
3. /customerId:
Answer: B
Explanation:
Correct answer is below as it follows the correct syntax.
/customers:
/{customerId}:
get:
NEW QUESTION # 106
Which one of them is NOT a flow in Mule?
- A. subflow
- B. async sub flow
- C. sync flow
- D. async flow
Answer: B
Explanation:
Correct answer is async sub flow. Rest are valid flows in Mule.
Sub flow is always synchronous.
NEW QUESTION # 107
Mule application contains ActiveMQ JMS dependency. Mule application was compiled and run successfully in Anypoint Studio. The mule application must now be exported from Anypoint Studio and shared with other developer. What export options should be selected to create the smallest JAR file that can be imported into other developer's Anypoint Studio and run successfully?
- A. Select only Attach Project Sources only
- B. Select both Attach Project Sources and Include project modules and dependencies option
- C. Select the Include project modules and dependencies option only
- D. De-select both Attach Project Sources and Include project modules and dependencies option
Answer: A
Explanation:
Correct answer is Select only Attach Project Sources only
You must keep the Attach Project Sources option selected to be able to import the packaged JAR file back into a Studio workspace.
Deselect the Include project modules and dependencies option.
This option skips bundling the actual modules and external dependencies required to run the Mule application in a Mule runtime engine, creating a lightweight JAR file package that does not include any dependencies specified in the Mule application's pom.xml file.
The generated JAR file is not a functional deployable archive and cannot be deployed to a Mule runtime engine, but instead offers a way to archive only the source files that make up the Mule application. This is the same as using the -lightWeightPackage flag when packaging using the Mule Maven Plugin and is useful if you want to distribute your project to other Studio installations because it only keeps a reference to all its dependencies. When you import a lightweight package into Studio, all your dependencies are automatically downloaded MuleSoft Doc Ref : https://docs.mulesoft.com/studio/7.8/import-export-packages
NEW QUESTION # 108
A web client submits a request to http://localhost:8081?accountType=personal. The query parameter is captured using a Set Variable transformer to a variable named accountType.
What is the correct DataWeave expression to log accountType?
- A. Account Type: #[message.inboundProperties.accountType]
- B. Account Type: #[flowVars.accountType]
- C. Account Type: #[vars.accountType]
- D. Account Type: # [attributes.accountType]
Answer: C
Explanation:
vars: Keyword for accessing a variable, for example, through a DataWeave expression in a Mule component, such as the Logger, or from an Input or Output parameter of an operation. If the name of your variable is myVar, you can access it like this: vars.myVar Hence correct answer is Account Type: #[vars.accountType]
NEW QUESTION # 109
A Mule application contains two HTTP Listeners, each configured for different API endpoints: http://acme.com/apis/orders and http: //acme .com/a pis/customers.
What base path value should be set in an HTT? Listener config element so that it can be used to configure both HTTP Listeners?
- A. /apis/orders|customers
- B. /apis/*
- C. /apis/
- D. /apis/?
Answer: B
Explanation:
Option 2 is the correct answer as /api/* accespts everything starting with /api/
NEW QUESTION # 110
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?
- A. Change the path attribute value to "/api/ship"
- B. Change the allowed method attributes value to "POST"
- C. Change the protocol attribute value to "HTTPS"
- D. Change the method attribute value to "*''
Answer: B
Explanation:
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)
NEW QUESTION # 111
Refer to the exhibits. A web client submits a request to http://localhost:8081/fliqhts?destination=SFO and the Web Service Consumer throws a WSC:BAD_REQUEST error.
What is the next step to fix this error?
- A. set a JSON payload before the Consume operation that contains the destination query parameter
- B. Set a header In the Consume operation equal to the destination query parameter
- C. set a SOAP payload before the Consume operation that contains the destination query parameter
- D. set a property m the Consume operation equal to the destination query parameter
Answer: C
Explanation:
As can be seen in error message , SOAP service findFlights expects the SOAP paylaod. This can be set using transform message processor which forms SOAP payload before the Consume operation that contains the destination query parameter
NEW QUESTION # 112
A flow has a JMS Publish consume operation followed by a JMS Publish operation. Both of these operations have the default configurations. Which operation is asynchronous and which one is synchronous?
- A. Publish consume: Synchronous. Publish: Synchronous
- B. Publish consume: Asynchronous. Publish: Asynchronous
- C. Publish consume: Synchronous. Publish: Asynchronous.
- D. Publish consume: Asynchronous. Publish: Synchronous
Answer: C
Explanation:
Publish consume: Synchronous. Publish: Asynchronous.
NEW QUESTION # 113
What is minimal requirement in a flow for a Mule application to compile?
- A. Source and processors both
- B. Event Processors
- C. Event Source
- D. Error handlers
Answer: B
Explanation:
Process section is must to get compiles. Process section must have one or more processors
NEW QUESTION # 114
Refer to the exhibit. The Batch Job processes, filters and aggregates records, What is the expected output from the Logger component?
- A. [10. 20] [30, 40] [50, 60]
- B. [20. 40] [60]
- C. [10. 20, 30. 40, 50, 60]
- D. [20, 40, 60]
Answer: B
Explanation:
* Batch scope has filter criteria which says paylod mod 2 = 0 whch means only 2, 4 and 6 will be in batch scope.
* So payload for each of these will be incremented by 10.
* Aggregator has batch size defined as 2. So it will process in batch of two records.
* Hence option 3 is correct answer.
[20,40]
[60]
Behavior with aggregator configured with fixed size
In this scenario, the batch step sends the processed records to an aggregator, which starts processing the records and buffering them until the configured aggregator's size is reached. After that, the aggregator sends the aggregated records to the stepping queue.
The batch job builds record blocks of the configured block size and sends them to their corresponding batch step for processing. Each batch step receives one or more record blocks and starts processing them in parallel. After the batch step processes a record, the batch step sends the record to the aggregator for further processing. The aggregator continues processing records until the number of aggregated records reaches the configured aggregator's size.
https://docs.mulesoft.com/mule-runtime/4.3/batch-processing-concept
NEW QUESTION # 115
......
Salesforce-MuleSoft-Developer-I dumps Exam Material with 237 Questions: https://www.lead1pass.com/Salesforce/Salesforce-MuleSoft-Developer-I-practice-exam-dumps.html
Salesforce-MuleSoft-Developer-I DUMPS Q&As with Explanations Verified & Correct Answers: https://drive.google.com/open?id=1qJekYrMWA5Mydq7aRsG_7Ow_G8FRl0rK