ExamGecko
Search Search Login
Home Home / Salesforce / Certified MuleSoft Developer II
Question list
Search
Search

List of questions

Search
Open VPLUS File
Convert VPLUS to PDF

Related questions

A Mule implementation uses a HTTP Request within an Unit Successful scope to connect to an API. How should a permanent error response like HTTP:UNAUTHORIZED be handle inside Until Successful to reduce latency?
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 healthcare portal needs to validate the token that it sends to a Mule API. The developer plans to implement a custom policy using the HTTP Policy Transform Extension to match the token received in the header from the heathcare portal. Which files does the developer need to create in order to package the custom policy?
Refer to the exhibit. Based on the code snippet, schema,json file, and payload below, what is the outcome of the given code snippet when a request is sent with the payload?
An API has been developed and deployed to CloudHub Among the policies applied to this API is an allowlist of IP addresses. A developer wants to run a test in Anypoint Studio and does not want any policies applied because their workstation is not included in the allowlist. What must the developer do in order to run this test locally without the policies applied?
Which statement is true when working with correlation IDS?
Refer to the exhibit. 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?
Which type of cache invalidation does the Cache scope support without having to write any additional code?
When a client and server are exchanging messages during the mTLS handshake, what is being agreed on during the cipher suite exchange?
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?

Question 17 - Certified MuleSoft Developer II discussion

Report
Export

When implementing a synchronous API where the event source is an HTTP Listener, a developer needs to return the same correlation ID back to the caller in the HTTP response header.

How can this be achieved?

A.
Enable the auto-generate CorrelationID option when scaffolding the flow
Answers
A.
Enable the auto-generate CorrelationID option when scaffolding the flow
B.
Enable the CorrelationID checkbox in the HTTP Listener configuration
Answers
B.
Enable the CorrelationID checkbox in the HTTP Listener configuration
C.
Configure a custom correlation policy
Answers
C.
Configure a custom correlation policy
D.
NO action is needed as the correlation ID is returned to the caller in the response header by default
Answers
D.
NO action is needed as the correlation ID is returned to the caller in the response header by default
Suggested 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

Show Answer
asked 23/09/2024
Sandor Alayon
27 questions
PreviousPreviousNextNext
User
Your answer:
0 comments
Sorted by

Leave a comment first

ExamGecko

Copyright @2023 ExamGecko | All right reserved

Mail us: [email protected]
About us
Contact us
Twitter X
Facebook
Medium
Convert VPLUS to PDF
Open VPLUS files Easily and Quickly
Privacy Policy
Disclaimer
Terms