A mule application uses an HTTP request operation to involve an external API.The external API follows the HTTP specification for proper status code usage.What is possible cause when a 3xx status code is returned to the HTTP Request operation from the external API?

The request was Redirected to a different URL by the external API

The request was not accepted by the external API

The request was Redirected to a different URL by the external API

The request was NOT RECEIVED by the external API

The request was ACCEPTED by the external API

An organization is migrating all its Mule applications to Runtime Fabric (RTF). None of the Mule applications use Mule domain projects.Currently, all the Mule applications have been manually deployed to a server group among several customer hosted Mule runtimes.Port conflicts between these Mule application deployments are currently managed by the DevOps team who carefully manage Mule application properties files.When the Mule applications are migrated from the current customer-hosted server group to Runtime Fabric (RTF), fo the Mule applications need to be rewritten and what DevOps port configuration responsibilities change or stay the same?

NO, The Mule applications do NOT need to be rewritten DevOps MUST STILL manage port conflicts

Yes, the Mule applications Must be rewritten DevOps No Longer needs to manage port conflicts between the Mule applications

Yes, the Mule applications Must be rewritten DevOps Must Still Manage port conflicts.

NO, The Mule applications do NOT need to be rewritten DevOps MUST STILL manage port conflicts

NO, the Mule applications do NO need to be rewritten DevOps NO LONGER needs to manage port conflicts between the Mule applications.

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 deplpoyed Mule applications, including MuleSoft-provided, customer-provided, or Mule application-provided certificates.What type of restrictions exist on the types of certificates that can be exposed by the CloudHub Shared Load Balancer (SLB) to external web clients over the public internet?

Only MuleSoft-provided certificates are exposed.

Only customer-provided wildcard certificates are exposed.

Only customer-provided self-signed certificates are exposed.

Only underlying Mule application certificates are exposed (pass-through)

A Mule application is being designed To receive nightly a CSV file containing millions of records from an external vendor over SFTP, The records from the file need to be validated, transformed. And then written to a database. Records can be inserted into the database in any order.In this use case, what combination of Mule components provides the most effective and performant way to write these records to the database?

Use a Batch job scope to bulk insert records into the database.

Use a Parallel for Each scope to Insert records one by one into the database

Use a Scatter-Gather to bulk insert records into the database

Use a Batch job scope to bulk insert records into the database.

Use a DataWeave map operation and an Async scope to insert records one by one into the database.

An automation engineer needs to write scripts to automate the steps of the API lifecycle, including steps to create, publish, deploy and manage APIs and their implementations in Anypoint Platform.What Anypoint Platform feature can be used to automate the execution of all these actions in scripts in the easiest way without needing to directly invoke the Anypoint Platform REST APIs?

Automated Policies in API Manager

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 API whenever the Order API is unavailable

Set an option in the HTTP Requester component that invokes the order API to instead invoke a fallback 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 platform API'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, customer-provided, 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 Load Balancer (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 publicly available and are associated with several mobile applications and web applications. The organization does 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 the applications or servers running the API implementations. What out-of-the-box Anypoint Platform policy 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 does NOT 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

An auto mobile company want to share inventory updates with dealers Dl and D2 asynchronously and concurrently via queues Q1 and Q2. Dealer Dl must consume the message from the queue Q1 and dealer D2 to must consume a message from the queue Q2.Dealer D1 has implemented a retry mechanism to reprocess the transaction in case of any errors while processing the inventers updates. Dealer D2 has not implemented any retry mechanism.How should the dealers acknowledge the message to avoid message loss and minimize impact on the current implementation?

Dealer D1 can use AUTO acknowledgement and dealer D2 must use manual acknowledgement and acknowledge the message after successful processing

Dealer D1 must use auto acknowledgement and dealer D2 can use manual acknowledgement and acknowledge the message after successful processing

Dealer D1 can use auto acknowledgement and dealer D2 can use IMMEDIATE acknowledgement and acknowledge the message of successful processing

Dealer D1 and dealer D2 must use AUTO acknowledgement and acknowledge the message after successful processing

Dealer D1 can use AUTO acknowledgement and dealer D2 must use manual acknowledgement and acknowledge the message after successful processing

A company is using Mulesoft to develop API's and deploy them to Cloudhub and on premises targets. Recently it has decided to enable Runtime Fabric deployment option as well and infrastructure is set up for this option.What can be used to deploy Runtime Fabric?

Directly uploading ajar file from the Runtime manager

As an enterprise architect, what are the two reasons for which you would use a canonical data model in the new integration project using Mulesoft Anypoint platform ( choose two answers )

To have consistent data structure aligned in processes

To isolate areas within a bounded context

To have consistent data structure aligned in processes

To isolate areas within a bounded context

To incorporate industry standard data formats

There are multiple canonical definitions of each data type

Because the model isolates the back and systems and support mule applications from change

A company is planning to migrate its deployment environment from on-premises cluster to a Runtime Fabric (RTF) cluster. It also has a requirement to enable Mule applications deployed to a Mule runtime instance to store and share data across application replicas and restarts.How can these requirements be met?

Configure Persistent Gateway at the RTF

Anypoint object store V2 to share data between replicas in the RTF cluster

Install the object store pod on one of the cluster nodes

Configure Persistence Gateway in any of the servers using Mule Object Store

Configure Persistent Gateway at the RTF

An organization designing a hybrid, load balanced, single cluster production environment. Due to performance service level agreement goals, it is looking into running the Mule applications in an active-active multi node cluster configuration.What should be considered when running its Mule applications in this type of environment?

A Mule application deployed to multiple nodes runs in an isolation from the other nodes in the cluster

All event sources, regardless of time , can be configured as the target source by the primary node in the cluster

An external load balancer is required to distribute incoming requests throughout the cluster nodes

A Mule application deployed to multiple nodes runs in an isolation from the other nodes in the cluster

Although the cluster environment is fully installed configured and running, it will not process any requests until an outage condition is detected by the primary node in the cluster.

An organization has decided on a cloud migration strategy to minimize the organization's own IT resources. Currently the organization has all of its new applications running on its own premises and uses an on-premises load balancer that exposes all APIs under the base URL (https://api.rutujar.com).As part of migration strategy, the organization is planning to migrate all of its new applications and load balancer CloudHub.What is the most straightforward and cost-effective approach to Mule application deployment and load balancing that preserves the public URL's?

Deploy the Mule application to Cloudhub Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the Cloudhub dedicated load balancer Apply mapping rules in DLB to map URLto their corresponding Mule applications

Deploy the Mule application to Cloudhub Create a CNAME record for base URL( httpsr://api.rutujar.com) in the Cloudhub shared load balancer that points to the A record of theon-premises load balancer Apply mapping rules in SLB to map URLto their corresponding Mule applications

Deploy the Mule application to Cloudhub Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the Cloudhub dedicated load balancer Apply mapping rules in DLB to map URLto their corresponding Mule applications

Deploy the Mule application to Cloudhub Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the CloudHub shared load balancer Apply mapping rules in SLB to map URLto their corresponding Mule applications

For each migrated Mule application, deploy an API proxy application to Cloudhub with all traffic to the mule applications routed through a Cloud Hub Dedicated load balancer (DLB) Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the CloudHub dedicated load balancer Apply mapping rules in DLB to map each API proxy application who is responding new application

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 architect who follows API led approach , what is the the below step you will perform so that you can share document 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.

Salesforce Certified MuleSoft Integration Architect I Practice Test 3

An organization is designing a mule application to support an all or nothing transaction between serval database operations and some other connectors so that they all roll back if there is a problem with any of the connectors

Besides the database connector , what other connector can be used in the transaction.

Become a Premium Member for full access

Unlock Premium Member

Salesforce Certified MuleSoft Integration Architect I Practice Test 3

Question

Salesforce Certified MuleSoft Integration Architect I Practice Tests

Practice Tests