A Mule API receives a JSON payload and updates the target system with the payload. The developer uses JSON schemas to ensure the data is valid.
How can the data be validation before posting to the target system?

• A. Apply the JSON Schema policy in API Manager and reference the correct schema in the policy configuration
• B. Using the DataWeave if Else condition test the values of the payload against the examples included in the schema
• C. Add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema
• D. Use a DataWeave 2.09 transform operation, and at the log of the DataWeave script, add:
  %dw 2.0
  Import.json-moduls

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?

• A. nullPayload
• B. testPayload
• C. originalPayload
• D. OS:KEY_NOT_FOUND

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?

• A. If the appointment date and customer name are invalid, a
  SCHEDULE:INVALID_APPOINTMENT_DATE error is raised
• B. If the email address is invalid, processing continues to see if the appointment data and customer name are also invalid
• C. If only the email address Is invalid a VALIDATION.INVALID_EMAIL error is raised
• D. If all of the values are invalid the last validation error is raised:SCHEDULE:INVALID_CUSTOMER_NAME

Which configurations are required for HTTP Listener to enable mTLS authentication?

• A. Set an appropriate reconnection strategy and use persistent connections for the listener
• B. Set an appropriate keystore configuration and use persistent connections for the listener
• C. Set an appropriate keystore and truststore configuration for the listener
• D. Set an appropriate truststore configuration and reconnection strategy for the listener

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