100% Pass Your MCD-Level-2 Exam Dumps at First Attempt with ExamBoosts [Q15-Q32]

100% ExamBoosts [Q15-Q32]でMCD-Level-2試験の一発試験に合格する

この記事を評価する

100% Pass Your MCD-Level-2 Exam Dumps at First Attempt with ExamBoosts

Penetration testers simulate MCD-Level-2 exam PDF

Q15. Which command is used to convert a JKS keystore to PKCS12?

Keytool-importkeystore -srckeystore keystore p12-srcstoretype PKCS12 -destkeystore keystore.jks
-deststoretype JKS

Keytool-importkeystore -srckeystore keystore p12-srcstoretype JKS -destkeystore keystore.p12
-deststoretype PKCS12

Keytool-importkeystore -srckeystore keystore jks-srcstoretype JKS -destkeystore keystore.p13
-deststoretype PKCS12

Keytool-importkeystore -srckeystore keystore jks-srcstoretype PKCS12 -destkeystore keystore.p12
-deststoretype JKS

説明
To convert a JKS keystore to PKCS12, the developer needs to use the keytool-importkeystore command with the following options: -srckeystore keystore.jks -srcstoretype JKS -destkeystore keystore.p12 -deststoretype PKCS12. This command imports all entries from a source JKS keystore (keystore.jks) into a destination PKCS12 keystore (keystore.p12). References:
https://docs.oracle.com/en/java/javase/11/tools/keytool.html#GUID-5990A2E4-78E3-47B7-AE75-6D182625954

Q16. When a client and server are exchanging messages during the mTLS handshake, what is being agreed on during the cipher suite exchange?

A protocol

The TLS version

An encryption algorithm

The Public key format

説明
A cipher suite is a set of cryptographic algorithms that are used to secure the communication between a client and a server. A cipher suite consists of four components: a key exchange algorithm, an authentication algorithm, an encryption algorithm, and a message authentication code (MAC) algorithm. During the cipher suite exchange, the client and the server agree on which encryption algorithm to use for encrypting and decrypting the data. References: https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#cipher-suites

Q17. A Mule application deployed to a standardalone Mule runtime uses VM queues to publish messages to be consumed asynchronously by another flow.
In the case of a system failure, what will happen to in-flight messages in the VM queues that have been consumed?

For nay type of queue, the message will be processed after the system comes online

For persistent queues, the message will be processed after the system comes online

For transient queues, the message will be processed after the system comes online

For any type of queue, the message will be lost

説明
In case of a system failure, in-flight messages in persistent VM queues that have been consumed will be processed after the system comes online. This is because persistent VM queues store messages on disk and guarantee delivery even if there is a system crash or restart. Therefore, any in-flight messages that have been consumed but not processed will be recovered from disk and processed when the system is back online.
References: https://docs.mulesoft.com/mule-runtime/4.3/vm-connector#persistent-queues

Q18. What is the MuleSoft recommended method to encrypt sensitive property data?

The encryption key and sensitive data should be different for each environment

The encryption key should be identical for all environments

The encryption key should be identical for all environments and the sensitive data should be different for each environment

The encryption key should be different for each environment and the sensitive data should be the same for all environments

説明
The MuleSoft recommended method to encrypt sensitive property data is to use the Secure Properties Tool that comes with Anypoint Studio. This tool allows encrypting properties files with a secret key and then decrypting them at runtime using the same key. The encryption key and sensitive data should be different for each environment to ensure security and avoid accidental exposure of sensitive data. References:
https://docs.mulesoft.com/mule-runtime/4.3/secure-configuration-properties

Q19. 展示を参照。
A Mute Object Store is configured with an entry TTL of one second and an expiration interval of 30 seconds.
What is the result of the flow if processing between os’store and os:retrieve takes 10 seconds?

nullPayload

originalPayload

OS:KEY_NOT_FOUND

testPayload

説明
The result of the flow is nullPayload if processing between os:store and os:retrieve takes 10 seconds. This is because the entry TTL of the object store is one second, which means that any stored value expires after one second and is removed from the object store. The expiration interval of 30 seconds only determines how often the object store checks for expired values, but it does not affect the TTL. Therefore, when os:retrieve tries to get the value after 10 seconds, it returns nullPayload because the value has already expired and been removed.
References: https://docs.mulesoft.com/object-store/osv2-faq#how-does-the-time-to-live-work

Q20. Mule application A is deployed to CloudHub and is using Object Store v2. Mute application B is also deployed to CloudHub.
Which approach can Mule application B use to remove values from Mule application A’S Object Store?

Object Store v2 REST API

CloudHub Connector

Object Store Connector

CloudHub REST API

説明
To remove values from Mule application A’s Object Store v2, Mule application B can use Object Store v2 REST API. This API allows performing operations on Object Store v2 resources using HTTP methods, such as GET, POST, PUT, and DELETE. Mule application B can use the DELETE method to remove values from Mule application A’s Object Store v2 by specifying the object store ID and the key of the value to delete.
References: https://docs.mulesoft.com/object-store/osv2-apis

Q21. A system API that communicates to an underlying MySQL database is deploying to CloudHub. The DevOps team requires a readiness endpoint to monitor all system APIs.
Which strategy should be used to implement this endpoint?

Create a dedicated endpoint that responds with the API status and reachability of the underlying systems

Create a dedicated endpoint that responds with the API status and health of the server

Use an existing resource endpoint of the API

Create a dedicated endpoint that responds with the API status only

説明
To implement a readiness endpoint to monitor all system APIs, the developer should create a dedicated endpoint that responds with the API status and reachability of the underlying systems. This way, the DevOps team can check if the system API is ready to receive requests and if it can communicate with its backend systems without errors. References:
https://docs.mulesoft.com/mule-runtime/4.3/deployment-strategies#readiness-probes

Q22. 展示を参照。
What is the result if ”Insecure” selected as part of the HTTP Listener configuration?

The HTTP Listener will trust any certificate presented by the HTTP client

The HTTP Lister will accept any unauthenticated request

The HTTP listener will only accept HTTP requests

Mutual TLS authentication will be enabled between this HTTP Listener and an HTTP client

説明
Based on the exhibit below, if ‘Insecure’ is selected as part of the HTTP Listener configuration, the HTTP listener will only accept HTTP requests. This means that no TLS context will be configured for this listener and no encryption or authentication will be applied to incoming requests. The protocol attribute of this listener will be set to HTTP instead of HTTPS. References:
https://docs.mulesoft.com/http-connector/1.6/http-listener-ref#insecure

Q23. A developer deploys an API to CloudHub and applies an OAuth policy on API Manager. During testing, the API response is slow, so the developer reconfigures the API so that the out-of-the-box HTTP Caching policy is applied first, and the OAuth API policy is applied second.
What will happen when an HTTP request is received?

In case of a cache hit, both the OAuth and HTTP Caching policies are evaluated; then the cached response is returned to the caller

In case of a cache it, only the HTTP Caching policy is evaluating; then the cached response is returned to the caller

In case of a cache miss, only the HTTP Caching policy is evaluated; then the API retrieves the data from the API implementation, and the policy stores the data to be cached in Object Store

In case of a cache miss, both the OAuth and HTTP Caching policies are evaluated; then the API retrieves the data from the API implementation, and the policy does not store the data in Object Store

説明
When an HTTP request is received and the HTTP Caching policy is applied first, it checks if there is a cached response for that request in Object Store. If there is a cache hit, meaning that a valid cached response exists, then only the HTTP Caching policy is evaluated and the cached response is returned to the caller without invoking the OAuth policy or the API implementation. If there is a cache miss, meaning that no valid cached response exists, then both the HTTP Caching policy and the OAuth policy are evaluated before invoking the API implementation. References:
https://docs.mulesoft.com/api-manager/2.x/http-caching-policy#policy-ordering

Q24. A scatter-gather router is configured with four routes:Route A, B, C and D.
Route C false.

Error,errorMesage.payload.results [‘2’]

Payload failures[‘2’]

Error,errorMessage,payload.failures[‘2’]

Payload [‘2’]

説明
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

Q25. A company with MuleSoft Titanium develops a Salesforce System API using MuleSoft out-of-the-box Salesforce Connector and deploys the API to CloudHub.
Which steps provide the average number of requests and average response time of the Salesforce Connector?

Access Anypoint Monitoring’s built-in dashboard. Select a resource.
Locate the information under the Connectors tab.

Access Anypoint Monitoring’s built-in dashboard
Seclect a resource.
Create a custom dashboard to retrieve the information.

Access Anypoint Monitoring built-in dashboard.
Select a resource.
Locate the information under Log Manager < Raw Data.

Change the API Implementation to capture the information in the log.
Retrieve the information from the log file.

説明
To get the average number of requests and average response time of the Salesforce Connector, the developer should access Anypoint Monitoring’s built-in dashboard, select a resource (such as an application or an API), and locate the information under the Connectors tab. The Connectors tab shows metrics for each connector used by the resource, such as average requests per minute, average response time, and failures. References:
https://docs.mulesoft.com/monitoring/built-in-dashboard-reference

Q26. Which statement is true when using XML SDK for creating custom message processors?

Properties are fields defined by an end user of the XML SDK component and serve as a global configuration for the entire Mule project in which they are used

An XML SDK provides both inbound and outbound operations

Operations can be reused in recursive calls

All operations are public

説明
When using XML SDK for creating custom message processors, all operations are public by default and can be used by any Mule application that imports them. There is no way to make an operation private or protected in XML SDK. References: https://docs.mulesoft.com/mule-sdk/1.1/xml-sdk#operations

Q27. An API has been built to enable scheduling email provider. The front-end system does very little data entry validation, and problems have started to appear in the email that go to patients. A validate-customer” flow is added validate the data.
What is he expected behavior of the ‘validate-customer” flow?

If only the email address Is invalid a VALIDATION.INVALID_EMAIL error is raised

If the email address is invalid, processing continues to see if the appointment data and customer name are also invalid

If the appointment date and customer name are invalid, a
SCHEDULE:INVALID_APPOINTMENT_DATE error is raised

If all of the values are invalid the last validation error is
raised:SCHEDULE:INVALID_CUSTOMER_NAME

説明
The validate-customer flow uses an until-successful scope to validate each field of the customer data. The until-successful scope executes its processors until they succeed or exhausts the maximum number of retries.
If any processor fails, it raises an error and stops executing the remaining processors. Therefore, if only the email address is invalid, a VALIDATION.INVALID_EMAIL error is raised and the validation of appointment date and customer name is skipped. References:
https://docs.mulesoft.com/mule-runtime/4.3/until-successful-scope

Q28. 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?

#{secure::tiskeystore,keyPassowrd}

${secure::tiskeystore,keyPassowrd}

p{secure::tiskeystore,keyPassowrd}

説明
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

Q29. Multiple individual Mute application need to use the Mule Maven plugin to deploy to CloudHub.
The plugin configuration should .. reused where necessary and anything project, specific should be property-based.
Where should the Mule Maven details be configured?

A parent pom.xml

Settings, xml

Pom, xml

A Bill of Materials (BOM) parent pm

説明
To reuse Mule Maven plugin configuration across multiple individual Mule applications, the developer should use a parent pom.xml file. A parent pom.xml file defines common configuration for one or more child projects that inherit from it. The developer can specify common properties and dependencies for all child projects in the parent pom.xml file, such as Mule Maven plugin configuration, and then reference them in each child project’s pom.xml file using placeholders. References:
https://docs.mulesoft.com/mule-runtime/4.3/mmp-concept#parent-pom
https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance

Q30. 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?

The application needs to configure HTTPS TLS context information to encrypt the data

The application needs to both the private and public keys to encrypt the data

The application needs the public key from the backend service to encrypt the data

The application needs the private key from the backend service to encrypt the data

説明
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

Q31. A Mule application uses API autodiscovery to access and enforce policies for a RESTful implementation.

Northing because flowRef is an optional attribute which can be passed runtime

The name of the flow that has APlkit Console to receive all incoming RESTful operation requests.

Any of the APIkit generate implement flows

The name of the flow that has HTTP listener to receive all incoming RESTful operation requests

説明
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 and associate 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

Q32. Which properties are mandatory on the HTTP Connector configuration in order to use the OAuth 2.0 Authorization Code grant type for authentication?

External callback URL, access token URL, client ID response access token

Token URL, authorization URL, client ID, client secret local callback URL

External callback URL, access token URL, client ID, response refresh token

External callback URL, access token URL, local authorization URL, authorization URL, client ID, client secret

説明
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

ローディング …