What requires configuration of both a key store and a trust store for an HTTP Listener?

• A.Encryption of both HTTP request and HTTP response bodies for all HTTP clients
• B.Encryption of both HTTP request header and HTTP request body for all HTTP clients
• C.Encryption of requests to both subdomains and API resource endpoints fhttPs://aDi.customer.com/ and https://customer.com/api)
• D.Support for TLS mutual (two-way) authentication with HTTP clients

Comment: *

Name: *

Email: *

Verification: *

A Mule application is being designed to do the following:
Step 1: Read a SalesOrder message from a JMS queue, where each SalesOrder consists of a header and a list of SalesOrderLineltems.
Step 2: Insert the SalesOrder header and each SalesOrderLineltem into different tables in an RDBMS.
Step 3: Insert the SalesOrder header and the sum of the prices of all its SalesOrderLineltems into a table In a different RDBMS.
No SalesOrder message can be lost and the consistency of all SalesOrder-related information in both RDBMSs must be ensured at all times.
What design choice (including choice of transactions) and order of steps addresses these requirements?

• A.1. Read the JMS message (NOT in an XA transaction)
  2. Perform BOTH DB inserts in ONE DB transaction
  3. Acknowledge the JMS message
• B.1- Read the JMS message (NOT in an XA transaction)
  2. Perform EACH DB insert in a SEPARATE DB transaction
  3. Acknowledge the JMS message
• C.1. Read the JMS message in an XA transaction
  2. In the SAME XA transaction, perform BOTH DB inserts but do NOT acknowledge the JMS message
• D.1. Read and acknowledge the JMS message (NOT in an XA transaction)
  2. In a NEW XA transaction, perform BOTH DB inserts

Comment: *

Name: *

Email: *

Verification: *

An organization currently uses a multi-node Mule runtime deployment model within their datacenter, so each Mule runtime hosts several Mule applications. The organization is planning to transition to a deployment model based on Docker containers in a Kubernetes cluster. The organization has already created a standard Docker image containing a Mule runtime and all required dependencies (including a JVM), but excluding the Mule application itself.
What is an expected outcome of this transition to container-based Mule application deployments?

• A.Required redesign of Mule applications to follow microservice architecture principles
• B.Required migration to the Docker and Kubernetes-based Anypoint Platform - Private Cloud Edition
• C.Required change to the URL endpoints used by clients to send requests to the Mule applications
• D.Guaranteed consistency of execution environments across all deployments of a Mule application

Comment: *

Name: *

Email: *

Verification: *

An organization has defined a common object model in Java to mediate the communication between different Mule applications in a consistent way. A Mule application is being built to use this common object model to process responses from a SOAP API and a REST API and then write the processed results to an order management system.
The developers want Anypoint Studio to utilize these common objects to assist in creating mappings for various transformation steps in the Mule application.
What is the most idiomatic (used for its intended purpose) and performant way to utilize these common objects to map between the inbound and outbound systems in the Mule application?

• A.Use the Transform Message component
• B.Use JAXB (XML) and Jackson (JSON) data bindings
• C.Use the Java module
• D.Use the WSS module

Comment: *

Name: *

Email: *

Verification: *

The implementation of a Process API must change. What is a valid approach that minimizes the impact of this change on API clients?

• A.Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged
• B.Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition
• C.Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version
• D.Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 - Moved Permanently to inform API clients they should be calling the new API implementation

Comment: *

Name: *

Email: *

Verification: *