Refer to the exhibit. An organization deploys multiple Mule applications to the same customer -hosted Mule runtime.Many of these Mule applications must expose an HTTPS endpoint on the same port using a serversidecertificate that rotates often.What is the most effective way to package the HTTP Listener and package or store the server-sidecertificate when deploying these Mule applications, so the disruption caused by certificate rotation isminimized?

Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Muleapplications that need to expose an HTTPS endpoint. Store the server-side certificate in a sharedfilesystem location in the Mule runtime's classpath, OUTSIDE the Mule DOMAIN or any MuleAPPLICATION

Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Muleapplications that need to expose an HTTPS endpoint Package the server-side certificate in ALL MuleAPPLICATIONS that need to expose an HTTPS endpoint

Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Muleapplications that need to expose an HTTPS endpoint. Store the server-side certificate in a sharedfilesystem location in the Mule runtime's classpath, OUTSIDE the Mule DOMAIN or any MuleAPPLICATION

Package an HTTPS Listener configuration In all Mule APPLICATIONS that need to expose an HTTPSendpoint Package the server-side certificate in a NEW Mule DOMAIN project

Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing It from all Muleapplications that need to expose an HTTPS endpoint. Package the server-side certificate in the SAMEMule DOMAIN project Go to Set

An API client is implemented as a Mule application that includes an HTTP Request operation using adefault configuration. The HTTP Request operation invokes an external API that follows standardHTTP status code conventions, which causes the HTTP Request operation to return a 4xx status code.What is a possible cause of this status code response?

The external API reported an error with the HTTP request that was received from the outboundHTTP Request operation of the Mule application

An error occurred inside the external API implementation when processing the HTTP request thatwas received from the outbound HTTP Request operation of the Mule application

The external API reported that the API implementation has moved to a different external endpoint

The HTTP response cannot be interpreted by the HTTP Request operation of the Mule applicationafter it was received from the external API

The external API reported an error with the HTTP request that was received from the outboundHTTP Request operation of the Mule application

An XA transaction Is being configured that involves a JMS connector listening for Incoming JMS messages. What is the meaning of the timeout attribute of the XA transaction, and what happens after the timeout expires?

The time that Is allowed to pass without the transaction being ended explicitly After the timeout, the transaction Is forcefully rolled-back

The time that is allowed to pass between committing the transaction and the completion of the Mule flow After the timeout, flow processing triggers an error

The time that Is allowed to pass between receiving JMS messages on the same JMS connection After the timeout, a new JMS connection Is established

The time that Is allowed to pass without the transaction being ended explicitly After the timeout, the transaction Is forcefully rolled-back

The time that Is allowed to pass for state JMS consumer threads to be destroyed After the timeout, a new JMS consumer thread is created

Refer to the exhibit. A Mule 4 application has a parent flow that breaks up a JSON array payload into 200 separate items, then sends each item one at a time inside an Async scope to a VM queue.A second flow to process orders has a VM Listener on the same VM queue. The rest of this flow processes each received item by writing the item to a database.This Mule application is deployed to four CloudHub workers with persistent queues enabled.What message processing guarantees are provided by the VM queue and the CloudHub workers, and how are VM messages routed among the CloudHub workers for each invocation of the parent flow under normal operating conditions where all the CloudHub workers remain online?

EACH item VM message is processed AT LEAST ONCE by ONE ARBITRARY CloudHub worker Each of the four CloudHub workers can be expected to process some item VM messages

EACH item VM message is processed AT MOST ONCE by ONE CloudHub worker, with workers chosen in a deterministic round-robin fashion Each of the four CloudHub workers can be expected to process 1/4 of the Item VM messages (about 50 items)

EACH item VM message is processed AT LEAST ONCE by ONE ARBITRARY CloudHub worker Each of the four CloudHub workers can be expected to process some item VM messages

ALL Item VM messages are processed AT LEAST ONCE by the SAME CloudHub worker where the parent flow was invoked This one CloudHub worker processes ALL 200 item VM messages

ALL item VM messages are processed AT MOST ONCE by ONE ARBITRARY CloudHub worker This one CloudHub worker processes ALL 200 item VM messages

Refer to the exhibit. An organization uses a 2-node Mute runtime cluster to host one stateless API implementation. The API is accessed over HTTPS through a load balancer that uses round-robin for load distribution.Two additional nodes have been added to the cluster and the load balancer has been configured to recognize the new nodes with no other change to the load balancer.What average performance change is guaranteed to happen, assuming all cluster nodes are fully operational?

50% reduction In the number of requests being received by each node

50% reduction in the response time of the API

100% increase in the throughput of the API

50% reduction In the JVM heap memory consumed by each node

50% reduction In the number of requests being received by each node

An integration Mule application is deployed to a customer-hosted multi-node Mule 4 runtime duster.The Mule application uses a Listener operation of a JMS connector to receive incoming messages from a JMS queue.How are the messages consumed by the Mule application?

Depending on the Listener operation configuration, either all messages are consumed by ONLY the primary cluster node or else EACH message is consumed by ANY ONE cluster node

Depending on the JMS provider's configuration, either all messages are consumed by ONLY the primary cluster node or else ALL messages are consumed by ALL cluster nodes

Regardless of the Listener operation configuration, all messages are consumed by ALL cluster nodes

Depending on the Listener operation configuration, either all messages are consumed by ONLY the primary cluster node or else EACH message is consumed by ANY ONE cluster node

Regardless of the Listener operation configuration, all messages are consumed by ONLY the primary cluster node

What is required before an API implemented using the components of Anypoint Platform can be managed and governed (by applying API policies) on Anypoint Platform?

The API must be published to Anypoint Exchange and a corresponding API instance ID must be obtained from API Manager to be used in the API implementation

The API implementation source code must be committed to a source control management system (such as GitHub)

A RAML definition of the API must be created in API designer so it can then be published to Anypoint Exchange

The API must be shared with the potential developers through an API portal so API consumers can interact with the API

Refer to the exhibit. One of the backend systems invoked by an API implementation enforces rate limits on the number of requests a particular client can make. Both the backend system and the API implementation are deployed to several non-production environments in addition to production.Rate limiting of the backend system applies to all non-production environments. The production environment, however, does NOT have any rate limiting.What is the most effective approach to conduct performance tests of the API implementation in a staging (non-production) environment?

Create a mocking service that replicates the backend system's production performance characteristics. Then configure the API implementation to use the mocking service and conduct the performance tests

Use MUnit to simulate standard responses from the backend system then conduct performance tests to identify other bottlenecks in the system

Include logic within the API implementation that bypasses invocations of the backend system in a performance test situation. Instead invoking local stubs that replicate typical backend system responses then conduct performance tests using this API Implementation

Conduct scaled-down performance tests in the staging environment against the rate limited backend system then upscale performance results to full production scale

An API has been unit tested and is ready for integration testing. The API is governed by a Client ID Enforcement policy in all environments.What must the testing team do before they can start integration testing the API in the Staging environment?

They must request access to the API instance in the Staging environment and obtain a Client ID and Client Secret to be used for testing the API

They must access the API portal and create an API notebook using the Client ID and Client Secret supplied by the API portal in the Staging environment

They must request access to the API instance in the Staging environment and obtain a Client ID and Client Secret to be used for testing the API

They must be assigned as an API version owner of the API in the Staging environment

They must request access to the Staging environment and obtain the Client ID and Client Secret for that environment to be used for testing the API

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

Support for TLS mutual (two-way) authentication with HTTP clients

Encryption of requests to both subdomains and API resource endpoints fhttPs://aDi.customer.com/ and https://customer.com/api)

Encryption of both HTTP request and HTTP response bodies for all HTTP clients

Encryption of both HTTP request header and HTTP request body for all HTTP clients

A retailer is designing a data exchange interface to be used by its suppliers. The interface must support secure communication over the public internet. The interface must also work with a wide variety of programming languages and IT systems used by suppliers.What are suitable interface technologies for this data exchange that are secure, cross-platform, and internet friendly, assuming that Anypoint Connectors exist for these interface technologies?

XML over ActiveMQ XML over SFTP XML/REST over HTTPS

EDJFACT XML over SFTP JSON/REST over HTTPS

SOAP over HTTPS HOP over TLS gRPC over HTTPS

XML over ActiveMQ XML over SFTP XML/REST over HTTPS

CSV over FTP YAML over TLS JSON over HTTPS

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?

Required redesign of Mule applications to follow microservice architecture principles

Required change to the URL endpoints used by clients to send requests to the Mule applications

Guaranteed consistency of execution environments across all deployments of a Mule application

Required redesign of Mule applications to follow microservice architecture principles

Required migration to the Docker and Kubernetes-based Anypoint Platform - Private Cloud Edition

Required change to the URL endpoints used by clients to send requests to the Mule applications

Guaranteed consistency of execution environments across all deployments of a Mule application

A team would like to create a project skeleton that developers can use as a starting point when creating API Implementations with Anypoint Studio. This skeleton should help drive consistent use of best practices within the team.What type of Anypoint Exchange artifact(s) should be added to Anypoint Exchange to publish the project skeleton?

a Mule application template with the key components and minimal integration logic

A custom asset with the default API implementation

A RAML archetype and reusable trait definitions to be reused across API implementations

An example of an API implementation following best practices

a Mule application template with the key components and minimal integration logic

What aspect of logging is only possible for Mule applications deployed to customer-hosted Mule runtimes, but NOT for Mule applications deployed to CloudHub?

To directly reference one shared and customized log4j2.xml file from multiple Mule applications

To send Mule application log entries to Splunk

To change tog4j2 tog levels in Anypoint Runtime Manager without having to restart the Mule application

To log certain messages to a custom log category

To directly reference one shared and customized log4j2.xml file from multiple Mule applications

What is true about the network connections when a Mule application uses a JMS connector to interact with a JMS provider (message broker)?

To complete sending a JMS message, the JMS connector must establish a network connection with the JMS message recipient

To receive messages into the Mule application, the JMS provider initiates a network connection to the JMS connector and pushes messages along this connection

The JMS connector supports both sending and receiving of JMS messages over the protocol determined by the JMS provider

The AMQP protocol can be used by the JMS connector to portably establish connections to various types of JMS providers

To complete sending a JMS message, the JMS connector must establish a network connection with the JMS message recipient

To receive messages into the Mule application, the JMS provider initiates a network connection to the JMS connector and pushes messages along this connection

The JMS connector supports both sending and receiving of JMS messages over the protocol determined by the JMS provider

The AMQP protocol can be used by the JMS connector to portably establish connections to various types of JMS providers

Refer to the exhibit. A business process involves the receipt of a file from an external vendor over SFTP. The file needs to be parsed and its content processed, validated, and ultimately persisted to a database. The delivery mechanism is expected to change in the future as more vendors send similar files using other mechanisms such as file transfer or HTTP POST.What is the most effective way to design for these requirements in order to minimize the impact of future change?

Create an API that receives the file and invokes a Process API with the data contained In the file, then have the Process API process the data using a MuleSoft Batch Job and other System APIs as needed

Use a MuleSoft Scatter-Gather and a MuleSoft Batch Job to handle the different files coming from different sources

Create a Process API to receive the file and process it using a MuleSoft Batch Job while delegating the data save process to a System API

Create an API that receives the file and invokes a Process API with the data contained In the file, then have the Process API process the data using a MuleSoft Batch Job and other System APIs as needed

Use a composite data source so files can be retrieved from various sources and delivered to a MuleSoft Batch Job for processing

Refer to the exhibit. A shopping cart checkout process consists of a web store backend sending a sequence of API invocations to an Experience API, which in turn invokes a Process API. All API invocations are over HTTPS POST. The Java web store backend executes in a Java EE application server, while all APIimplementations are Mule applications executing in a customer -hosted Mule runtime.End-to-end correlation of all HTTP requests and responses belonging to each individual checkoutInstance is required. This is to be done through a common correlation ID, so that all log entrieswritten by the web store backend, Experience API implementation, and Process API implementationinclude the same correlation ID for all requests and responses belonging to the same checkoutinstance.What is the most efficient way (using the least amount of custom coding or configuration) for the web store backend and the implementations of the Experience API and Process API to participate in end-to-end correlation of the API invocations for each checkout instance?

The web store backend generates a new correlation ID value at the start of checkout and sets it on the X-CORRELATlON-lt HTTP request header In each API invocation belonging to that checkout No special code or configuration is included in the Experience API and Process API implementations to generate and manage the correlation ID

The web store backend, being a Java EE application, automatically makes use of the thread-local correlation ID generated by the Java EE application server and automatically transmits that to the Experience API using HTTP-standard headers No special code or configuration is included in the web store backend, Experience API, and Process API implementations to generate and manage the correlation ID

The web store backend generates a new correlation ID value at the start of checkout and sets it on the X-CORRELATlON-lt HTTP request header In each API invocation belonging to that checkout No special code or configuration is included in the Experience API and Process API implementations to generate and manage the correlation ID

The Experience API implementation generates a correlation ID for each incoming HTTP request and passes it to the web store backend in the HTTP response, which includes it in all subsequent API invocations to the Experience API.The Experience API implementation must be coded to also propagate the correlation ID to the Process API in a suitable HTTP request header

The web store backend sends a correlation ID value in the HTTP request body In the way required by the Experience API The Experience API and Process API implementations must be coded to receive the custom correlation ID In theHTTP requests and propagate It in suitable HTTP request headers

What operation can be performed through a JMX agent enabled in a Mule application?

Set a particular tog4J2 log level to TRACE

Refer to the exhibit. A Mule application is deployed to a multi-node Mule runtime cluster. The Mule application uses the competing consumer pattern among its cluster replicas to receive JMS messages from a JMS queue.To process each received JMS message, the following steps are performed in a flow:Step l: The JMS Correlation ID header is read from the received JMS message.Step 2: The Mule application invokes an idempotent SOAP webservice over HTTPS, passing the JMSCorrelation ID as one parameter in the SOAP request.Step 3: The response from the SOAP webservice also returns the same JMS Correlation ID.Step 4: The JMS Correlation ID received from the SOAP webservice is validated to be identical to the JMS Correlation ID received in Step 1.Step 5: The Mule application creates a response JMS message, setting the JMS Correlation ID message header to the validated JMS Correlation ID and publishes that message to a response JMS queue.Where should the Mule application store the JMS Correlation ID values received in Step 1 and Step 3 so that the validation in Step 4 can be performed, while also making the overall Mule application highly available, fault-tolerant, performant, and maintainable?

The Correlation ID value in Step 1 should be stored in a persistent object store The Correlation ID value in step 3 should be stored as a Mule event variable/attribute

Both Correlation ID values should be stored in a persistent object store

Both Correlation ID values should be stored In a non-persistent object store

The Correlation ID value in Step 1 should be stored in a persistent object store The Correlation ID value in step 3 should be stored as a Mule event variable/attribute

Both Correlation ID values should be stored as Mule event variable/attribute

An integration Mute application is being designed to process orders by submitting them to a backend system for offline processing. Each order will be received by the Mute application through an HTTPS POST and must be acknowledged immediately. Once acknowledged, the order will be submitted to a backend system. Orders that cannot be successfully submitted due to rejections from the backend system will need to be processed manually (outside the backend system).The Mule application will be deployed to a customer-hosted runtime and is able to use an existing ActiveMQ broker if needed.The backend system has a track record of unreliability both due to minor network connectivity issues and longer outages.What idiomatic (used for their intended purposes) combination of Mule application components and ActiveMQ queues are required to ensure automatic submission of orders to the backend system, while minimizing manual order processing?

Until Successful component ActiveMQ long retry Queue ActiveMQ Dead Letter Queue for manual processing

An On Error scope Non-persistent VM ActiveMQ Dead Letter Queue for manual processing

An On Error scope MuleSoft Object Store ActiveMQ Dead Letter Queue for manual processing

Until Successful component MuleSoft Object Store ActiveMQ is NOT needed or used

Until Successful component ActiveMQ long retry Queue ActiveMQ Dead Letter Queue for manual processing

What comparison is true about a CloudHub Dedicated Load Balancer (DLB) vs. the CloudHub Shared Load Balancer (SLB)?

Only a DLB allows the configuration of a custom TLS server certificate

Only the SLB can forward HTTP traffic to the VPC-internal ports of the CloudHub workers

Both a DLB and the SLB allow the configuration of access control via IP whitelists

Both a DLB and the SLB implement load balancing by sending HTTP requests to workers with thelowest workloads

Additional nodes are being added to an existing customer-hosted Mule runtime cluster to improve performance. Mule applications deployed to this cluster are invoked by API clients through a load balancer.What is also required to carry out this change?

External monitoring tools or log aggregators must be configured to recognize the new nodes

A new load balancer must be provisioned to allow traffic to the new nodes in a round-robin fashion

External monitoring tools or log aggregators must be configured to recognize the new nodes

API implementations using an object store must be adjusted to recognize the new nodes and persist to them

New firewall rules must be configured to accommodate communication between API clients and the new nodes

An organization is creating a set of new services that are critical for their business. The project team prefers using REST for all services but is willing to use SOAP with common WS-" standards if a particular service requires it.What requirement would drive the team to use SOAP/WS-* for a particular service?

Must secure the service, requiring all consumers to submit a valid SAML token

Must use XML payloads for the service and ensure that it adheres to a specific schema

Must publish and share the service specification (including data formats) with the consumers of the service

Must support message acknowledgement and retry as part of the protocol

Must secure the service, requiring all consumers to submit a valid SAML token

Refer to the exhibit. A business process involves two APIs that interact with each other asynchronously over HTTP. EachAPI is implemented as a Mule application. API 1 receives the initial HTTP request and invokes API 2 (in a fire and forget fashion) while API 2, upon completion of the processing, calls back into API l to notify about completion of the asynchronous process.Each API Is deployed to multiple redundant Mule runtimes and a separate load balancer, and is deployed to a separate network zone.In the network architecture, how must the firewall rules be configured to enable the above Interaction between API 1 and API 2?

To enable communication from each API's Mule Runtimes and Network zone to the load balancer of the other API

To authorize the certificate to be used both APIs

To enable communication from each API's Mule Runtimes and Network zone to the load balancer of the other API

To open direct two-way communication between the Mule Runtimes of both API's

To allow communication between load balancers used by each API

An organization is designing the following two Mule applications that must share data via a common persistent object store instance:- Mule application P will be deployed within their on-premises datacenter.- Mule application C will run on CloudHub in an Anypoint VPC.The object store implementation used by CloudHub is the Anypoint Object Store v2 (OSv2). what type of object store(s) should be used, and what design gives both Mule applications access to the same object store instance?

Application C uses the Object Store connector to access a persistent object Application P accesses the persistent object store via the Object Store REST API

Application P uses the Object Store connector to access a persistent object store Application C accesses this persistent object store via the Object Store REST API through an IPsec tunnel

Application C and P both use the Object Store connector to access the Anypoint Object Store v2

Application C uses the Object Store connector to access a persistent object Application P accesses the persistent object store via the Object Store REST API

Application C and P both use the Object Store connector to access a persistent object store

What limits if a particular Anypoint Platform user can discover an asset in Anypoint Exchange?

The business groups to which the user belongs

Design Center and RAML were both used to create the asset

The existence of a public Anypoint Exchange portal to which the asset has been published

The type of the asset in Anypoint Exchange

The business groups to which the user belongs

Mule application A receives a request Anypoint MQ message REQU with a payload containing a variable-length list of request objects. Application A uses the For Each scope to split the list into individual objects and sends each object as a message to an Anypoint MQ queue.Service S listens on that queue, processes each message independently of all other messages, and sends a response message to a response queue.Application A listens on that response queue and must in turn create and publish a response Anypoint MQ message RESP with a payload containing the list of responses sent by service S in the same order as the request objects originally sent in REQU.Assume successful response messages are returned by service S for all request messages.What is required so that application A can ensure that the length and order of the list of objects in RESP and REQU match, while at the same time maximizing message throughput?

Keep track of the list length and all object indices in REQU, both in the For Each scope and in all communication involving service Use persistent storage when creating RESP

Use a Scatter-Gather within the For Each scope to ensure response message order Configure the Scatter-Gather with a persistent object store

Perform all communication involving service S synchronously from within the For Each scope, so objects in RESP are in the exact same order as request objects in REQU

Use an Async scope within the For Each scope and collect response messages in a second For Each scope in the order In which they arrive, then send RESP using this list of responses

Keep track of the list length and all object indices in REQU, both in the For Each scope and in all communication involving service Use persistent storage when creating RESP

An organization has various integrations implemented as Mule applications. Some of these Mule applications are deployed to custom hosted Mule runtimes (on-premises) while others execute in the MuleSoft-hosted runtime plane (CloudHub). To perform the Integra functionality, these Mule applications connect to various backend systems, with multiple applications typically needing to access the backend systems.How can the organization most effectively avoid creating duplicates in each Mule application of the credentials required to access the backend systems?

Configure or create a credentials service that returns the credentials for each backend system, and that is accessible from customer-hosted and MuleSoft-hosted Mule runtimes Have the Mule applications toad the properties at startup by invoking that credentials service

Create a Mule domain project that maintains the credentials as Mule domain-shared resources Deploy the Mule applications to the Mule domain, so the credentials are available to the Mule applications

Store the credentials in properties files in a shared folder within the organization's data center Have the Mule applications load properties files from this shared location at startup

Segregate the credentials for each backend system into environment-specific properties files Package these properties files in each Mule application, from where they are loaded at startup

Configure or create a credentials service that returns the credentials for each backend system, and that is accessible from customer-hosted and MuleSoft-hosted Mule runtimes Have the Mule applications toad the properties at startup by invoking that credentials service

Refer to the exhibit. A Mule application is deployed to a cluster of two customer-hosted Mute runtimes. The Mute application has a flow that polls a database and another flow with an HTTP Listener.HTTP clients send HTTP requests directly to individual cluster nodes.What happens to database polling and HTTP request handling in the time after the primary (master)node of the cluster has railed, but before that node is restarted?

Database polling continues Only HTTP requests sent to the remaining node continue to beaccepted

Database polling stops All HTTP requests continue to be accepted

Database polling continues All HTTP requests continue to be accepted, but requests to the failednode Incur increased latency

Database polling stops All HTTP requests are rejected

A global organization operates datacenters in many countries. There are private network links between these datacenters because all business data (but NOT metadata) must be exchanged over these private network connections.The organization does not currently use AWS in any way.The strategic decision has Just been made to rigorously minimize IT operations effort and investment going forward.What combination of deployment options of the Anypoint Platform control plane and runtime plane(s) best serves this organization at the start of this strategic journey?

MuleSoft-hosted Anypoint Platform control plane Customer-hosted runtime plane in each datacenter

MuleSoft-hosted Anypoint Platform control plane CloudHub Shared Worker Cloud in multiple AWS regions

Anypoint Platform - Private Cloud Edition Customer-hosted runtime plane in each datacenter

MuleSoft-hosted Anypoint Platform control plane Customer-hosted runtime plane in multiple AWS regions

MuleSoft-hosted Anypoint Platform control plane Customer-hosted runtime plane in each datacenter

A new Mule application under development must implement extensive data transformation logic.Some of the data transformation functionality is already available as external transformation services that are mature and widely used across the organization; the rest is highly specific to the new Mule application.The organization follows a rigorous testing approach, where every service and application must be extensively acceptance tested before it is allowed to go into production.What is the best way to implement the data transformation logic for this new Mule application while minimizing the overall testing effort?

Implement transformation logic in the new Mute application using DataWeave, invoking existing transformation services when possible

Implement and expose all transformation logic as mlaoservices using DataWeave, so it can be reused by any application component that needs it, including the new Mule application

Implement transformation logic in the new Mute application using DataWeave, replicating the transformation logic of existing transformation services

Extend the existing transformation services with new transformation logic and Invoke them from the new Mule application

Implement transformation logic in the new Mute application using DataWeave, invoking existing transformation services when possible

A Mule application uses the Database connector.What condition can the Mule application automatically adjust to or recover from without needing to restart or redeploy the Mule application?

The database server was unavailable for four hours due to a major outage but is now fully operational again

One of the stored procedures being called by the Mule application has been renamed

The database server was unavailable for four hours due to a major outage but is now fully operational again

The credentials for accessing the database have been updated and the previous credentials are no longer valid

The database server has been updated and hence the database driver library/JAR needs a minor version upgrade

Refer to the exhibit. Anypoint Platform supports role-based access control (RBAC) to features of the platform. An organization has configured an external Identity Provider for identity management with Anypoint Platform.What aspects of RBAC must ALWAYS be controlled from the Anypoint Platform control plane and CANNOT be controlled via the external Identity Provider?

Assigning Anypoint Platform permissions to a role

Controlling the business group within Anypoint Platform to which the user belongs

Assigning Anypoint Platform permissions to a role

Assigning Anypoint Platform role(s) to a user

Removing a user's access to Anypoint Platform when they no longer work for the organization

MuleSoft MCIA - Level 1 Practice Test 1 - Free Online Exam Prep & Questions

Question 1 / 40

Mule applications need to be deployed to CloudHub so they can access on-premises database systems. These systems store sensitive and hence tightly protected data, so are not accessible over the internet.

What network architecture supports this requirement?

An Anypoint VPC connected to the on-premises network using an IPsec tunnel or AWS DirectConnect, plus matching firewall rules in the VPC and on-premises network

Static IP addresses for the Mule applications deployed to the CloudHub Shared Worker Cloud, plus matching firewall rules and IP whitelisting in the on-premises network

An Anypoint VPC with one Dedicated Load Balancer fronting each on-premises database system, plus matching IP whitelisting in the load balancer and firewall rules in the VPC and on-premises network

Relocation of the database systems to a DMZ in the on-premises network, with Mule applications deployed to the CloudHub Shared Worker Cloud connecting only to the DMZ

Comment (0)

MuleSoft MCIA - Level 1 Practice Test 1

Question

MuleSoft MCIA - Level 1 Practice Tests

Practice Tests