A travel company wants to publish a well-defined booking service API to be shared with its business partners. These business partners have agreed to ONLY consume SOAP services and they want to get the service contracts in an easily consumable way before they start any development. The travel company will publish the initial design documents to Anypoint Exchange, then share those documents with the business partners. When using an API-led approach, what is the first design document the travel company should deliver to its business partners?

Create a WSDL specification using any XML editor

Create a RAML API specification using any text editor

Create an OAS API specification in Design Center

Create a SOAP API specification in Design Center

What is not true about Mule Domain Project?

Only available Anypoint Runtime Fabric

This allows Mule applications to share resources

Expose multiple services within the Mule domain on the same port

Only available Anypoint Runtime Fabric

Send events (messages) to other Mule applications using VM queues

An API implementation is being designed that must invoke an Order API which is known to repeatedly experience downtime. For this reason a fallback API is to be called when the Order API is unavailable. What approach to designing invocation of the fallback API provides the best resilience?

Redirect client requests through an HTTP 303 temporary redirect status code to the fallback APIwhenever the Order API is unavailable

Set an option in the HTTP Requester component that invokes the order API to instead invoke afallback API whenever an HTTP 4XX or 5XX response status code is received from Order API

Create a separate entry for the order API in API manager and then invoke this API as a fallback API if the primary Order API is unavailable

Search Anypoint Exchange for a suitable existing fallback API and them implement invocations to their fallback API in addition to the Order API

How are the API implementation , API client, and API consumer combined to invoke and process an API ?

An API client creates an API consumer, which receives API invocation from an API such that they are processed for an API implementation

The API consumer creates an API implementation , which receives API invocations from an API such that they are processed for an API client

The API consumer creates an API client which sends API invocations to an API such that they are processed by an API implementation

An API client creates an API consumer, which receives API invocation from an API such that they are processed for an API implementation

The API client creates an API consumer which sends API invocations to an API such that they are processed by API implementation

What Mule application can have API policies applied by Anypoint Platform to the endpoint exposed by that Mule application?

A Mule application that accepts requests over HTTP/1x

A Mule application that accepts JSON requests over TCP but is NOT required to provide a response.

A Mule application that accepts JSON requests over WebSocket

A Mule application that accepts gRPC requests over HTTP/2

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

Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged

Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition

Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version

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

Organization wants to achieve high availability goal for Mule applications in customer hosted runtime plane. Due to the complexity involved, data cannot be shared among of different instances of same Mule application. What option best suits to this requirement considering high availability is very much critical to the organization?

Use third party product to implement load balancer

High availability can be achieved only in CloudHub

An organization needs to enable access to their customer data from both a mobile app and a web application, which each need access to common fields as well as certain unique fields. The data is available partially in a database and partially in a 3rd-party CRM system. What APIs should be created to best fit these design requirements?

Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system

A Process API that contains the data required by both the web and mobile apps, allowing these applications to invoke it directly and access the data they need thereby providing the flexibility to add more fields in the future without needing API changes.

One set of APIs (Experience API, Process API, and System API) for the web app, and another set for the mobile app.

Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system

A common Experience API used by both the web and mobile apps, but separate Process APIs for the web and mobile apps that interact with the database and the CRM System.

What is true about automating interactions with Anypoint Platform using tools such as Anypoint Platform REST API's, Anypoint CLI or the Mule Maven plugin?

By default, the Anypoint CLI and Mule Maven plugin are not included in the Mule runtime

Access to Anypoint Platform API;s and Anypoint CLI can be controlled separately thruough the roles and permissions in Anypoint platform, so that specific users can get access to Anypoint CLI while others get access to the platformAPI's

Anypoint Platform API's can only automate interactions with CloudHub while the Mule maven plugin is required for deployment to customer hosted Mule runtimes

API policies can be applied to the Anypoint platform API's so that only certain LOS's has access to specific functions

An organization uses one specific CloudHub (AWS) region for all CloudHub deployments. How are CloudHub workers assigned to availability zones (AZs) when the organization's Mule applications are deployed to CloudHub in that region?

Workers are randomly distributed across available AZs within that region.

Workers belonging to a given environment are assigned to the same AZ within that region.

AZs are selected as part of the Mule application's deployment configuration.

Workers are randomly distributed across available AZs within that region.

An AZ is randomly selected for a Mule application, and all the Mule application's CloudHub workers are assigned to that one AZ

What best describes the Fully Qualified Domain Names (FQDNs), also known as DNS entries, created when a Mule application is deployed to the CloudHub Shared Worker Cloud?

The FQDNs are determined by both the application name and the region

A fixed number of FQDNs are created, IRRESPECTIVE of the environment and VPC design

The FQDNs are determined by the application name chosen, IRRESPECTIVE of the region

The FQDNs are determined by the application name, but can be modified by an administrator after deployment

The FQDNs are determined by both the application name and the region

What is a key difference between synchronous and asynchronous logging from Mule applications?

Asynchronous logging can improve Mule event processing throughput while also reducing the processing time for each Mule event

Synchronous logging writes log messages in a single logging thread but does not block the Mule event being processed by the next event processor

Asynchronous logging can improve Mule event processing throughput while also reducing the processing time for each Mule event

Asynchronous logging produces more reliable audit trails with more accurate timestamps

Synchronous logging within an ongoing transaction writes log messages in the same thread that processes the current Mule event

A global, high-volume shopping Mule application is being built and will be deployed to CloudHub. To improve performance, the Mule application uses a Cache scope that maintains cache state in a CloudHub object store. Web clients will access the Mule application over HTTP from all around the world, with peak volume coinciding with business hours in the web client's geographic location. To achieve optimal performance, what Anypoint Platform region should be chosen for the CloudHub object store?

Choose the same region as to where the Mule application is deployed

Choose the US-West region, the only supported region for CloudHub object stores

Choose the geographically closest available region for each web client

Choose a region that is the traffic-weighted geographic center of all web clients

An organization is evaluating using the CloudHub shared Load Balancer (SLB) vs creating a CloudHub dedicated load balancer (DLB). They are evaluating how this choice affects the various types of certificates used by CloudHub deployed Mule applications, including MuleSoft-provided, customerprovided, or Mule application-provided certificates. What type of restrictions exist on the types of certificates for the service that can be exposed by the CloudHub Shared LoadBalancer (SLB) to external web clients over the public internet?

Only MuleSoft provided certificates can be used for server side certificate

Underlying Mule applications need to implement own certificates

Only MuleSoft provided certificates can be used for server side certificate

Only self signed certificates can be used

All certificates which can be used in shared load balancer need to get approved by raising support ticket

An organization is implementing a Quote of the Day API that caches today's quote. What scenario can use the CloudHub Object Store connector to persist the cache's state?

When there is one CloudHub deployment of the API implementation to three workers that must share the cache state.

When there is one deployment of the API implementation to CloudHub and another one to customer hosted mule runtime that must share the cache state.

When there are two CloudHub deployments of the API implementation by two Anypoint Platform business groups to the same CloudHub region that must share the cache state.

When there is one CloudHub deployment of the API implementation to three workers that must share the cache state.

When there are three CloudHub deployments of the API implementation to three separate CloudHub regions that must share the cache state.

An organization has several APIs that accept JSON data over HTTP POST. The APIs are all publiclyavailable and are associated with several mobile applications and web applications. The organizationdoes NOT want to use any authentication or compliance policies for these APIs, but at the same time,is worried that some bad actor could send payloads that could somehow compromise theapplications or servers running the API implementations. What out-of-the-box Anypoint Platformpolicy can address exposure to this threat?

Apply a JSON threat protection policy to all APIs to detect potential threat vectors

Apply a Header injection and removal policy that detects the malicious data before it is used

Apply an IP blacklist policy to all APIs; the blacklist will Include all bad actors

Shut out bad actors by using HTTPS mutual authentication for all API invocations

Apply a JSON threat protection policy to all APIs to detect potential threat vectors

A new upstream API Is being designed to offer an SLA of 500 ms median and 800 ms maximum (99th percentile) response time. The corresponding API implementation needs to sequentially invoke 3 downstream APIs of very similar complexity. The first of these downstream APIs offers the following SLA for its response time: median: 100 ms, 80th percentile: 500 ms, 95th percentile: 1000 ms. If possible, how can a timeout be set in the upstream API for the invocation of the first downstream API to meet the new upstream API's desired SLA?

No timeout is possible to meet the upstream API's desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API

Set a timeout of 100 ms; that leaves 400 ms for the other two downstream APIs to complete

Do not set a timeout; the Invocation of this API Is mandatory and so we must wait until it responds

Set a timeout of 50 ms; this times out more invocations of that API but gives additional room for retries

No timeout is possible to meet the upstream API's desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API

An API has been updated in Anypoint Exchange by its API producer from version 3.1.1 to 3.2.0 following accepted semantic versioning practices and the changes have been communicated via the API's public portal. The API endpoint doesNOT change in the new version. How should the developer of an API client respond to this change?

The API client code ONLY needs to be changed if it needs to take advantage of new features.

The update should be identified as a project risk and full regression testing of the functionality that uses this API should be run.

The API producer should be contacted to understand the change to existing functionality.

The API producer should be requested to run the old version in parallel with the new one.

The API client code ONLY needs to be changed if it needs to take advantage of new features.

When designing an upstream API and its implementation, the development team has been advised to not set timeouts when invoking downstream API. Because the downstream API has no SLA that can be relied upon. This is the only donwstream API dependency of that upstream API. Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?

An SLA for the upstream API CANNOT be provided.

The invocation of the downstream API will run to completion without timing out.

An SLA for the upstream API CANNOT be provided.

A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes.

A load-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes.

What aspects of a CI/CD pipeline for Mule applications can be automated using MuleSoft-provided Maven plugins?

Compile, package, unit test, validate unit test coverage, deploy

Compile, package, unit test, deploy, integration test (Incorrect)

Compile, package, unit test, deploy, create associated API instances in API Manager

Import from API designer, compile, package, unit test, deploy, publish to Anypoint Exchange

What condition requires using a CloudHub Dedicated Load Balancer?

When server-side load-balanced TLS mutual authentication is required between API implementations and API clients

When cross-region load balancing is required between separate deployments of the same Mule application

When custom DNS names are required for API implementations deployed to customer-hosted Mule runtimes

When API invocations across multiple CloudHub workers must be load balanced

When server-side load-balanced TLS mutual authentication is required between API implementations and API clients

Mule application is deployed to Customer Hosted Runtime. Asynchronous logging was implemented to improved throughput of the system. But it was observed over the period of time that few of the important exception log messages which were used to rollback transactions are not working as expected causing huge loss to the Organization. Organization wants to avoid these losses. Application also has constraints due to which they cant compromise on throughput much.What is the possible option in this case?

Mixed configuration of asynchronous or synchronous loggers should be used to log exceptions via synchronous way

Logging needs to be changed from asynchronous to synchronous

External log appender needs to be used in this case

Persistent memory storage should be used in such scenarios

Mixed configuration of asynchronous or synchronous loggers should be used to log exceptions via synchronous way

As a part of business requirement , old CRM system needs to be integrated using Mule application.CRM system is capable of exchanging data only via SOAP/HTTP protocol. As an integration architectwho follows API led approach , what is the the below step you will perform so that you can sharedocument with CRM team?

Create WSDL specification using text editor

Create RAML specification using Design Center

Create SOAP API specification using Design Center

Create WSDL specification using text editor

Create WSDL specification using Design Center

Insurance organization is planning to deploy Mule application in MuleSoft Hosted runtime plane. As a part of requirement , application should be scalable . highly available. It also has regulatory requirement which demands logs to be retained for at least 2 years. As an Integration Architect what step you will recommend in order to achieve this?

It is not possible to store logs for 2 years in CloudHub deployment. External log management system is required.

When deploying an application to CloudHub , logs retention period should be selected as 2 years

When deploying an application to CloudHub, worker size should be sufficient to store 2 years data

Logging strategy should be configured accordingly in log4j file deployed with the application.

An organization is designing Mule application which connects to a legacy backend. It has been reported that backend services are not highly available and experience downtime quite often. As an integration architect which of the below approach you would propose to achieve high reliability goals?

Until Successful scope can be implemented while calling backend API's

Alerts can be configured in Mule runtime so that backend team can be communicated when services are down

Until Successful scope can be implemented while calling backend API's

On Error Continue scope to be used to call in case of error again

Create a batch job with all requests being sent to backend using that job as per the availability of backend API's

A Mule application contains a Batch Job scope with several Batch Step scopes. The Batch Job scope is configured with a batch block size of 25.A payload with 4,000 records is received by the Batch Job scope.When there are no errors, how does the Batch Job scope process records within and between the Batch Step scopes?

The Batch Job scope processes multiple record blocks in parallel, and a block of 25 records can jump ahead to the next Batch Step scope over an earlier block of records Each Batch Step scope is invoked with one record in the payload of the received Mule event For each Batch Step scope, all 25 records within a block are processed in parallel All the records in a block must be completed before the block of 25 records is available to the next Batch Step scope

The Batch Job scope processes each record block sequentially, one at a time Each Batch Step scope is invoked with one record in the payload of the received Mule event For each Batch Step scope, all 25 records within a block are processed sequentially, one at a time All 4000 records must be completed before the blocks of records are available to the next Batch Step scope

The Batch Job scope processes multiple record blocks in parallel, and a block of 25 records can jump ahead to the next Batch Step scope over an earlier block of records Each Batch Step scope is invoked with one record in the payload of the received Mule event For each Batch Step scope, all 25 records within a block are processed sequentially, one record at a time All the records in a block must be completed before the block of 25 records is available to the nextBatch Step scope

The Batch Job scope processes multiple record blocks in parallel Each Batch Step scope is invoked with a batch of 25 records in the payload of the received Mule event For each Batch Step scope, all 4000 records are processed in parallel Individual records can jump ahead to the next Batch Step scope before the rest of the records finish processing in the current Batch Step scope

To implement predictive maintenance on its machinery equipment, ACME Tractors has installed thousands of IoT sensors that will send data for each machinery asset as sequences of JMS messages, in near real-time, to a JMS queue named SENSOR_DATA on a JMS server. The Mule application contains a JMS Listener operation configured to receive incoming messages from the JMS servers SENSOR_DATA JMS queue. The Mule application persists each receivedJMS message, then sends a transformed version of the corresponding Mule event to the machinery equipment back-end systems.The Mule application will be deployed to a multi-node, customer-hosted Mule runtime cluster.Under normal conditions, each JMS message should be processed exactly once.How should the JMS Listener be configured to maximize performance and concurrent message processing of the JMS queue?

Set numberOfConsumers to a value greater than oneSet primaryNodeOnly = false

Set numberOfConsumers = 1Set primaryNodeOnly = false

Set numberOfConsumers = 1Set primaryNodeOnly = true

Set numberOfConsumers to a value greater than oneSet primaryNodeOnly = true

Set numberOfConsumers to a value greater than oneSet primaryNodeOnly = false

A Mule application is synchronizing customer data between two different database systems.What is the main benefit of using eXtended Architecture (XA) transactions over local transactions to synchronize these two different database systems?

An XA transaction handles the largest number of requests in the shortest time

An XA transaction synchronizes the database systems with the least amount of Mule configuration or coding

An XA transaction handles the largest number of requests in the shortest time

An XA transaction automatically rolls back operations against both database systems if any operation falls

An XA transaction writes to both database systems as fast as possible

An organization has implemented a continuous integration (CI) lifecycle that promotes Mule applications through code, build, and test stages. To standardize the organization's CI journey, a new dependency control approach is being designed to store artifacts that include information such as dependencies, versioning, and build promotions.To implement these process improvements, the organization will now require developers to maintain all dependencies related to Mule application code in a shared location.What is the most idiomatic (used for its intended purpose) type of system the organization should use in a shared location to standardize all dependencies related to Mule application code?

A MuleSoft-managed repository at repository.mulesoft.org

The Anypoint Object Store service at cloudhub.io

The ABC company has an Anypoint Runtime Fabric on VMs/Bare Metal (RTF-VM) appliance installed on its own customer-hosted AWS infrastructure.Mule applications are deployed to this RTF-VM appliance. As part of the company standards, the Mule application logs must be forwarded to an external log management tool (LMT).Given the company's current setup and requirements, what is the most idiomatic (used for its intended purpose) way to send Mule application logs to the external LMT?

In RTF-VM, install and configure the external LTM's log-forwarding agent

In RTF-VM, edit the pod configuration to automatically install and configure an Anypoint Monitoring agent

In each Mule application, configure custom Log4j settings

In RTF-VM. configure the out-of-the-box external log forwarder

An organization is designing an integration Mule application to process orders by submitting them to a back-end system for offline processing. Each order will be received by the Mule application through an HTTPS POST and must be acknowledged immediately. Once acknowledged, the order will be submitted to a back-end system. Orders that cannot be successfully submitted due to rejections from the back-end system will need to be processed manually (outside the back-end system).The Mule application will be deployed to a customer-hosted runtime and is able to use an existing ActiveMQ broker if needed. The ActiveMQ broker is located inside the organization's firewall. The back-end system has a track record of unreliability due to both 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 back-end system while supporting but minimizing manual order processing?

An Until Successful scope to call the back-end systemOne or more ActiveMQ long-retry queuesOne or more ActiveMQ dead-letter queues for manual processing

One or more On Error scopes to assist calling the back-end systemAn Until Successful scope containing VM components for long retriesA persistent dead-letter VM queue configured in CloudHub

One or more On Error scopes to assist calling the back-end systemOne or more ActiveMQ long-retry queuesA persistent dead-letter object store configured in the CloudHub Object Store service

A Batch Job scope to call the back-end systemAn Until Successful scope containing Object Store components for long retries A dead-letter object store configured in the Mule application

A Mule application uses APIkit for SOAP to implement a SOAP web service. The Mule application has been deployed to a CloudHub worker in a testing environment.The integration testing team wants to use a SOAP client to perform Integration testing. To carry out the integration tests, the integration team must obtain the interface definition for the SOAP web service.What is the most idiomatic (used for its intended purpose) way for the integration testing team to obtain the interface definition for the deployed SOAP web service in order to perform integration testing with the SOAP client?

Retrieve the XML file(s) from Runtime Manager

Retrieve the OpenAPI Specification file(s) from API Manager

Retrieve the WSDL file(s) from the deployed Mule application

Retrieve the RAML file(s) from the deployed Mule application

Retrieve the XML file(s) from Runtime Manager

In Anypoint Platform, a company wants to configure multiple identity providers (IdPs) for multiple lines of business (LOBs). Multiple business groups, teams, and environments have been defined for these LOBs.What Anypoint Platform feature can use multiple IdPs across the company's business groups, teams, and environments?

MuleSoft-hosted (CloudHub) dedicated load balancers

Client (application) management

An external web UI application currently accepts occasional HTTP requests from client web browsersto change (insert, update, or delete) inventory pricing information in an inventory system's database.Each inventory pricing change must be transformed and then synchronized with multiple customer experience systems in near real-time (in under 10 seconds). New customer experience systems are expected to be added in the future.The database is used heavily and limits the number of SELECT queries that can be made to the database to 10 requests per hour per user.What is the most scalable, idiomatic (used for its intended purpose), decoupled. reusable, and maintainable integration mechanism available to synchronize each inventory pricing change with the various customer experience systems in near real-time?

Add a trigger to the inventory-pricing database table so that for each change to the inventory pricing database, a stored procedure is called that makes a REST call to a Mule application Write the Mule application to publish each Mule event as a message to an Anypoint MQ exchange Write other Mule applications to subscribe to the Anypoint MQ exchange, transform each received message, and then update the Mule application's corresponding customer experience system(s)

Write a Mule application with a Database On Table Row event source configured for the inventory pricing database, with the watermark attribute set to an appropriate database column In the same now, use a Scatter-Gather to call each customer experience system's REST API with transformed inventory-pricing records

Add a trigger to the inventory-pricing database table so that for each change to the inventory pricing database, a stored procedure is called that makes a REST call to a Mule application Write the Mule application to publish each Mule event as a message to an Anypoint MQ exchange Write other Mule applications to subscribe to the Anypoint MQ exchange, transform each received message, and then update the Mule application's corresponding customer experience system(s)

Replace the external web UI application with a Mule application to accept HTTP requests fromclient web browsersIn the same Mule application, use a Batch Job scope to test if the database request will succeed,aggregate pricing changes within a short time window, and then update both the inventory pricingdatabase and each customer experience system using a Parallel For Each scope

Write a Mule application with a Database On Table Row event source configured for the inventory pricing database, with the ID attribute set to an appropriate database column In the same flow, use a Batch Job scope to publish transformed Inventory-pricing records to an Anypoint MQ queue Write other Mule applications to subscribe to the Anypoint MQ queue, transform each received message, and then update the Mule application's corresponding customer experience system(s)

MuleSoft MCIA - Level 1 Practice Test 3 - Free Online Exam Questions 81-120

An API implementation is being developed to expose data from a production database via HTTPrequests. The API implementation executes a database SELECT statement that is dynamically createdbased upon data received from each incoming HTTP request. The developers are planning to usevarious types of testing to make sure the Mule application works as expected, can handle specificworkloads, and behaves correctly from an API consumer perspective. What type of testing wouldtypically mock the results from each SELECT statement rather than actually execute it in theproduction database?

Become a Premium Member for full access

Unlock Premium Member

MuleSoft MCIA - Level 1 Practice Test 3

Question

MuleSoft MCIA - Level 1 Practice Tests

Practice Tests