MCD Level 2 Demo 11
MCD Level 2 Demo 11
MuleSoft
MCD-LEVEL-2 Exam
MuleSoft Certified Developer - Level 2 (Mule 4)
https://www.braindumpsstore.com/MCD-LEVEL-2.html
https://www.braindumpsstore.com
Questions & Answers PDF Page 2
Version: 4.0
Question: 1
The flow is invoicing a target API. The API’s protocol is HTTPS. The TLS configuration in the HTTP Request
Configuration global element is set to None. A web client submits a request to
http:localhost:8081/vehicles.
https://www.braindumpsstore.com
Questions & Answers PDF Page 3
https://www.braindumpsstore.com
Questions & Answers PDF Page 4
If the certificate of the target API is signed by a certificate authority (CA), what is true about the HTTP
Request operation when the flow executes?
A. The HTTP Request operation will succeed if the CA’S certificate is present in the JRE’s default keystore
B. The HTTP Request operation will succeed if the CA’s certificate is present in the JRE’s default
truststore.
C. The HTTP Request operation will always succeed regardless of the CA
D. The HTTP Request operation will always fail regardless of the CA
Answer: B
Explanation:
The HTTP Request operation will use the default truststore of the JRE to validate the certificate of the
target API. If the CA’s certificate is present in the truststore, the operation will succeed. Otherwise, it will
fail with a handshake exception. Reference: https://docs.mulesoft.com/mule-runtime/4.3/tls-
configuration#tls-default
Question: 2
When a client and server are exchanging messages during the mTLS handshake, what is being agreed on
during the cipher suite exchange?
A. A protocol
B. The TLS version
C. An encryption algorithm
D. The Public key format
Answer: C
Explanation:
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. Reference: https://docs.mulesoft.com/mule-runtime/4.3/tls-
configuration#cipher-suites
Question: 3
A custom policy needs to be developed to intercept all cutbound HTTP requests made by Mule
applications.
Which XML element must be used to intercept outbound HTTP requests?
https://www.braindumpsstore.com
Questions & Answers PDF Page 5
D. http-policy:processor
Answer: D
Explanation:
The http-policy:processor element is used to intercept outbound HTTP requests made by Mule
applications. It allows customizing the request before it is sent to the target API and modifying the
response after it is received from the target API. Reference: https://docs.mulesoft.com/api-
manager/2.x/policy-mule4-custom-policy#policy-xml-file
Question: 4
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?
Answer: A
Explanation:
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. Reference:
https://docs.mulesoft.com/mule-runtime/4.3/until-successful-scope
Question: 5
When implementing a synchronous API where the event source is an HTTP Listener, a developer needs
https://www.braindumpsstore.com
Questions & Answers PDF Page 6
to return the same correlation ID back to the caller in the HTTP response header.
How can this be achieved?
Answer: D
Explanation:
When implementing a synchronous API where the event source is an HTTP Listener, Mule automatically
propagates some message attributes between flows via outbound and inbound properties. One of these
attributes is correlation ID, which is returned to the caller in the response header by default as
MULE_CORRELATION_ID. Reference: https://docs.mulesoft.com/mule-runtime/4.3/about-mule-
message#message-attributes
https://www.braindumpsstore.com
Questions & Answers PDF Page 7
https://www.braindumpsstore.com/MCD-LEVEL-2.html
https://www.braindumpsstore.com