Use Real MCD-Level-2 - 100% Cover Real Exam Questions [Oct-2024]
Dumps Brief Outline Of The MCD-Level-2 Exam - PassLeader
NEW QUESTION # 14
A developer has created the first version of an API designed for business partners to work commodity prices.
What should developer do to allow more than one major version of the same API to be exposed by the implementation?
- A. In Design Center, open the RAML and modify baseUn to include a variable that indicates the version number
- B. In Anypoint Studio, generate scaffolding from the RAML, and then modify the flow names generated by APIKit to include a variable with the major version number
- C. In Design Center, open the RAML and modify each operation to include the major version number
- D. In Anypoint Studio, generate scaffolding from the RAML, and the modify the <http:listerner> in the generated flows to include a parameter to replace the version number
Answer: A
Explanation:
To allow more than one major version of the same API to be exposed by the implementation, the developer should modify the baseUri property in the RAML file to include a variable that indicates the version number.
The baseUri property defines the base URL of the API and can include variables that are replaced with actual values when mocking or deploying the API. By using a variable for the version number, the developer can expose different versions of the API using different base URLs and avoid conflicts or confusion. References:
https://docs.mulesoft.com/api-designer/design-modify-raml-specs#baseurihttps://docs.mulesoft.com/api-manager
NEW QUESTION # 15
Which pattern should be used to invoke multiple HTTP APIs in parallel and roll back failed requests in sequence?
- A. A database as a transactional outbox and an Until Successful router to retry any requests
- B. A Parallel for Each scope with each HTTP request wrapped in a Try scope
- C. Scatter-Gather as central Saga orchestrator for all API request with compensating actions for failing routes
- D. VM queues as a reliability pattern with error handlers to roll back any requests
Answer: C
Explanation:
To invoke multiple HTTP APIs in parallel and roll back failed requests in sequence, the developer should use a Scatter-Gather router as a central Saga orchestrator for all API requests with compensating actions for failing routes. A Scatter-Gather router executes multiple routes concurrently and aggregates the results. A Saga orchestrator coordinates a series of actions across different services and handles failures by executing compensating actions. Therefore, using a Scatter-Gather router as a Saga orchestrator allows invoking multiple HTTP APIs in parallel and rolling back any failed requests in sequence. References:
https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concepthttps://docs.mulesoft.com/mule-runtime/4.3/sa
NEW QUESTION # 16
Which statement is true when working with correlation IDS?
- A. The HTTP Listener generates correlation IDS unless a correlation ID is received in the HTTP request
- B. The HTTP Listener regenerates correlation IDs regardless of the HTTP request
- C. The VM Connector does not automatically propagate correction IDs
- D. The Anypoint MQ Connector automatically propagates correlation IDS
Answer: A
Explanation:
When working with correlation IDs, the HTTP Listener generates correlation IDs unless a correlation ID is received in the HTTP request. In that case, it propagates the received correlation ID throughout the flow execution. Correlation IDs are used to track events across different flows or applications.
References:https://docs.mulesoft.com/mule-runtime/4.3/about-mule-message#message-attributes
NEW QUESTION # 17
Two APIs are deployed to a two-node on-prem cluster. Due to a requirements change, the two APIs must communicate to exchange data asynchronously.
- A. The VM Connector is used to inter-application communication, so it is not possible to use the VM Connector
- B. If the two APIs use the same domain, the VM Connector can be leveraged
- C. It is not possible to use the VM Connector since the APIs are running in a cluster mode and each mode has it own set of VM Queues
- D. Instead of using the VM Connector use <flow-ref>directly
Answer: B
Explanation:
To communicate asynchronously between two APIs deployed to a two-node on-prem cluster, the developer can use the VM Connector if the two APIs use the same domain. The VM Connector allows passing messages between different Mule applications within a single Mule runtime instance or across different instances using shared memory or persistent storage. If two APIs are deployed under the same domain, they can share resources such as VM queues and communicate asynchronously using VM Connector operations. References:
https://docs.mulesoft.com/mule-runtime/4.3/vm-connectorhttps://docs.mulesoft.com/mule-runtime/4.3/shared-res
NEW QUESTION # 18
A Mule application defines as SSL/TLS keystore properly 'tis,keystore.keyPassword'' as secure.
How can this property be referenced to access its value within the application?
- A. p{secure::tiskeystore,keyPassowrd}
- B. #{secure::tiskeystore,keyPassowrd}
- C. ${secure::tiskeystore,keyPassowrd}
- D. ${secure::tiskeystore,keyPassowrd}
Answer: D
Explanation:
secure::tiskeystore,keyPassowrdShortExplanationofCorrectAnswerOnly:Toreferenceasecurepropertyvaluewithin In this case, the property name is tiskeystore,keyPassword, so the correct syntax is
${secure::tiskeystore,keyPassowrd}.References:
https://docs.mulesoft.com/mule-runtime/4.3/secure-configuration-properties#referencing-secure-properties
NEW QUESTION # 19
Refer to the exhibit.
What action must be performed to log all the errors raised by the VM Connector?
- A. Add <AsyncLOgger name='orgroute.extensions vm' level=ERROR'/> inside the Appenders tag
- B. Add <AsyncLOgger name='orgroute.extensions vm' level=ERROR'I> inside the Logger tag
- C. Configure <Logger level-'ERROR'/> inside the VM Connector configuration
- D. Nothing, as error-level events are automatically logged
Answer: A
Explanation:
To log all the errors raised by the VM Connector, the developer needs to add an async logger with the name
'org.mule.extension.vm' and the level 'ERROR' inside the appenders tag of the log4j2.xml file. This will enable logging all error-level events generated by the VM Connector to the console appender.
References:https://docs.mulesoft.com/mule-runtime/4.3/logging-in-mule#configuring-custom-logging-settings
NEW QUESTION # 20
Refer to the exhibit.
What action must be performed to log all the errors raised by the VM Connector?
- A. Add <AsyncLOgger name='orgroute.extensions vm' level=ERROR'/> inside the Appenders tag
- B. Add <AsyncLOgger name='orgroute.extensions vm' level=ERROR'I> inside the Logger tag
- C. Configure <Logger level-'ERROR'/> inside the VM Connector configuration
- D. Nothing, as error-level events are automatically logged
Answer: A
Explanation:
Explanation
To log all the errors raised by the VM Connector, the developer needs to add an async logger with the name
'org.mule.extension.vm' and the level 'ERROR' inside the appenders tag of the log4j2.xml file. This will enable logging all error-level events generated by the VM Connector to the console appender. References:
https://docs.mulesoft.com/mule-runtime/4.3/logging-in-mule#configuring-custom-logging-settings
NEW QUESTION # 21
An organization uses CloudHub to deploy all of its applications.
How can a common-global-handler flow be configured so that it can be reused across all of the organization's deployed applications?
- A. Create a Mule plugin project
Create a common-global-error-handler flow inside the plugin project.
Use this plugin as a dependency in all Mute applications.
Import that configuration file in Mute applications. - B. Create a Mule daman project.
Create a common-global-error-handler flow inside the domain project.
Use this domain project as a dependency. - C. Create a common-global-error-handler flow in all Mule Applications Refer to it flow-ref wherever needed.
- D. Create a Mule Plugin project
Create a common-global-error-handler flow inside the plugin project.
Use this plugin as a dependency in all Mule applications
Answer: D
Explanation:
Explanation
To configure a common-global-handler flow that can be reused across all of the organization's deployed applications, the developer should create a Mule Plugin project, create a common-global-error-handler flow inside the plugin project, and use this plugin as a dependency in all Mule applications. This way, the developer can import the common-global-error-handler flow in any application that needs it and avoid duplicating the error handling logic. References:
https://docs.mulesoft.com/mule-runtime/4.3/error-handling#global-error-handler
NEW QUESTION # 22
An order processing system is composed of multiple Mule application responsible for warehouse, sales and shipping. Each application communication using Anypoint MQ. Each message must be correlated against the original order ID for observability and tracing.
How should a developer propagate the order ID as the correlation ID across each message?
- A. Use the default correlation ID, Anypoint MQ will sutomatically propagate it.
- B. Set a custom Anypoint MQ user property to propagate the order ID and set the correlation ID in the receiving applications.
- C. Use the underlying HTTP request of Anypoint MQ to set the 'X-CORRELATION_ID' header to the order ID
- D. Wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID
Answer: D
Explanation:
Explanation
To propagate the order ID as the correlation ID across each message using Anypoint MQ, the developer should wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID. The With CorrelationID scope allows setting a custom correlation ID for any event that occurs within it. The Tracing module also enables distributed tracing across different Mule applications and services using Anypoint Monitoring. References:
https://docs.mulesoft.com/tracing-module/1.0/tracing-module-reference#with-correlation-id-scope
https://docs.mulesoft.com/tracing-module/1.0/tracing-module-concepts
NEW QUESTION # 23
Refer to the exhibits.
Bioinfo System API is implemented and published to Anypoint Exchange. A developer wants to invoke this API using its REST Connector.
What should be added to the POM?
- A.
- B.
- C.
- D.
- E.
Answer: B
Explanation:
To invoke Bioinfo System API using its REST Connector, option E should be added to the pom.xml file. This option adds a dependency for Bioinfo System API REST Connector with its group ID, artifact ID, version, classifier, and type. The classifier specifies that it is a REST Connector (raml-client), and the type specifies that it is a Mule plugin (mule-plugin).
References:https://docs.mulesoft.com/apikit/4.x/apikit-4-generate-from-rest-api-task#add-the-api-dependency-to
NEW QUESTION # 24
A scatter-gather router is configured with four routes:Route A, B, C and D.
Route C false.
- A. Payload ['2']
- B. Error,errorMessage,payload.failures['2']
- C. Payload failures['2']
- D. Error,errorMesage.payload.results ['2']
Answer: B
Explanation:
Explanation
The result of accessing route C failure is Error,errorMessage,payload.failures['2']. This is because a scatter-gather router returns an aggregated message that contains an array of results from each route and an array of failures from each route. The failures array contains error objects with information about each failed route execution. To access route C failure, which is the third route (index 2), the developer needs to use Error.errorMessage.payload.failures['2'] expression. References:
https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-reference#scatter-gather-output
NEW QUESTION # 25
Which properties are mandatory on the HTTP Connector configuration in order to use the OAuth 2.0 Authorization Code grant type for authentication?
- A. External callback URL, access token URL, client ID, response refresh token
- B. External callback URL, access token URL, local authorization URL, authorization URL, client ID, client secret
- C. Token URL, authorization URL, client ID, client secret local callback URL
- D. External callback URL, access token URL, client ID response access token
Answer: C
Explanation:
Explanation
To use the OAuth 2.0 Authorization Code grant type for authentication, the HTTP Connector configuration requires the following properties: token URL, authorization URL, client ID, client secret, and local callback URL. The token URL is the endpoint of the authorization server that provides access tokens. The authorization URL is the endpoint of the authorization server that initiates the user consent flow. The client ID and client secret are the credentials of the Mule application registered with the authorization server. The local callback URL is the endpoint of the Mule application that receives the authorization code from the authorization server.
References: https://docs.mulesoft.com/http-connector/1.6/http-authentication#oauth-2-0
NEW QUESTION # 26
Refer to the exhibit.
When creating a new project, which API implementation allows for selecting the correct API version and scaffolding the flows from the API specification?
- A. Import RAML from local file
- B. Download RAML from Design Center'
- C. Import a published API
- D. Generate a local RAML from anypoint Studio
Answer: C
Explanation:
Explanation
To create a new project that selects the correct API version and scaffolds the flows from the API specification, the developer should import a published API. This option allows importing an API specification that has been published to Anypoint Exchange or Design Center, and selecting a specific version of that API specification.
The developer can also choose to scaffold flows based on that API specification. References:
https://docs.mulesoft.com/apikit/4.x/apikit-4-new-project-task
NEW QUESTION # 27
A developer is working on a project that requires encrypting all data before sending it to a backend application. To accomplish this, the developer will use PGP encryption in the Mule 4 Cryptography module.
What is required to encrypt the data before sending it to the backend application?
- A. The application needs to configure HTTPS TLS context information to encrypt the data
- B. The application needs the public key from the backend service to encrypt the data
- C. The application needs the private key from the backend service to encrypt the data
- D. The application needs to both the private and public keys to encrypt the data
Answer: B
Explanation:
Explanation
To encrypt the data before sending it to the backend application using PGP encryption, the application needs the public key from the backend service. PGP encryption uses a public-key cryptography system, which means that each party has a pair of keys: a public key and a private key. The public key is used to encrypt data, and the private key is used to decrypt data. Therefore, to encrypt data for a specific recipient (the backend service), the application needs to use the recipient's public key. The recipient can then use its own private key to decrypt the data. References: https://docs.mulesoft.com/mule-runtime/4.3/cryptography-pgp
NEW QUESTION # 28
A Mule application uses API autodiscovery to access and enforce policies for a RESTful implementation.
- A. Any of the APIkit generate implement flows
- B. The name of the flow that has HTTP listener to receive all incoming RESTful operation requests
- C. The name of the flow that has APlkit Console to receive all incoming RESTful operation requests.
- D. Northing because flowRef is an optional attribute which can be passed runtime
Answer: B
Explanation:
To use API autodiscovery to access and enforce policies for a RESTful implementation, flowRef must be set to the name of the flow that has HTTP listener to receive all incoming RESTful operation requests. This way, API autodiscovery can identify the API implementation andassociate it with the corresponding API specification and policies in API Manager. The flow that has HTTP listener is usually the main flow that contains the APIKit Router.
References:https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept#flowref
NEW QUESTION # 29
Refer to the exhibit.
A developer generates the base scaffolding for an API in Anypoint Studio.
Which HTTP status code is returned while testing using the API Kit console if no values are entered in client-secret?
- A. HTTP status code:403
- B. HTTP status code:200
- C. HTTP status code:400
- D. HTTP status code:500
Answer: A
Explanation:
Explanation
Based on the code snippet and schema.json file below, when testing using the API Kit console if no values are entered in client-secret, HTTP status code 403 (FORBIDDEN) is returned. This is because client-secret is defined as a required header parameter in schema.json file, which means that it must be present in every request. If no values are entered in client-secret, then it is equivalent to omitting this header parameter, which violates the schema and causes APIKit Router to return HTTP status code 403. References:
https://docs.mulesoft.com/apikit/4.x/apikit-4-headers
NEW QUESTION # 30
......
Certification Training for MCD-Level-2 Exam Dumps Test Engine: https://www.passleader.top/MuleSoft/MCD-Level-2-exam-braindumps.html