Get 100% Passing Success With True MCIA-Level-1 Exam! [Sep-2021]
MuleSoft MCIA-Level-1 PDF Questions - Exceptional Practice To MuleSoft Certified Integration Architect - Level 1
NEW QUESTION 29
An Order microservice and a Fulfillment microservice are being designed to communicate with their dients through message-based integration (and NOT through API invocations).
The Order microservice publishes an Order message (a kind of command message) containing the details of an order to be fulfilled. The intention is that Order messages are only consumed by one Mute application, the Fulfillment microservice.
The Fulfilment microservice consumes Order messages, fulfills the order described therein, and then publishes an OrderFulfilted message (a kind of event message). Each OrderFulfilted message can be consumed by any interested Mule application, and the Order microservice is one such Mute application.
What is the most appropriate choice of message broker(s) and message destination(s) in this scenario?
- A. Order messages are sent to a JMS queueOrderFulfilled messages are sent to a JMS topicBoth microservices Interact with the same JMS provider (message broker) Instance, which must therefore scale to support the load of both microservices
- B. O Order messages are sent to an Anypoint MQ exchange
OrderFulfilted messages are sent to an Anypoint MQ queue
Both microservices interact with Anypoint MQ as the message broker, which must therefore scale to support the toad of both microservices - C. Older messages are sent directly to the Fulfillment microservices
OrderFulfilled messages are sent directly to the Order microservice
The Order microserviceInteracts with one AMQP-compatible message broker and the Fulfillment microservice Interactswith a different AMQP-compatible message broker, so that both message brokers can be chosen and scaled to best support the toad each microservice - D. Order messages are sent to a JMS queueOrderFulfilled messages are sent to a JMS topic The Order microservice Interacts with one JMS provider (message broker) and the Fulfillment microservice interacts with a different JMS provider, so that both message brokers can be chosen and scaled to best support the load of each microservice
Answer: A
NEW QUESTION 30
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?
- A. Use a Scatter-Gather within the For Each scope to ensure response message order Configure the Scatter-Gather with a persistent object store
- B. 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
- C. 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
- D. 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
Answer: A
NEW QUESTION 31
A Mule application is synchronizing customer data between two different database systems.
What is the main benefit of using XA transactions over local transactions to synchronize these two database systems?
- A. Simplifies communication
- B. Increases throughput
- C. Ensures consistency
- D. Reduces latency
Answer: D
Explanation:
Explanation
NEW QUESTION 32
Refer to the exhibit.
A Mule application is being designed to be deployed to several CIoudHub workers. The Mule application's integration logic is to replicate changed Accounts from Satesforce to a backend system every 5 minutes.
A watermark will be used to only retrieve those Satesforce Accounts that have been modified since the last time the integration logic ran.
What is the most appropriate way to implement persistence for the watermark in order to support the required data replication integration logic?
- A. Persistent Anypoint MQ Queue
- B. Persistent Cache Scope
- C. Persistent VM Queue
- D. Persistent Object Store
Answer: D
NEW QUESTION 33
An external REST client periodically sends an array of records in a single POST request to a Mule application API endpoint.
The Mule application must validate each record of the request against a JSON schema before sending it to a downstream system in the same order that it was received in the array Record processing will take place inside a router or scope that calls a child flow. The child flow has its own error handling defined. Any validation or communication failures should not prevent further processing of the remaining records.
To best address these requirements what is the most idiomatic(used for it intended purpose) router or scope to used in the parent flow, and what type of error handler should be used in the child flow?
- A. Until Successful router in the parent flow
On Error Propagate error handler in the child flow - B. First Successful router in the parent flow
On Error Continue error handler in the child flow - C. Parallel For Each scope in the parent flow
On Error Propagate error handler in the child flow - D. For Each scope in the parent flow
On Error Continue error handler in the child flow
Answer: B
NEW QUESTION 34
49 of A popular retailer is designing a public API for its numerous business partners. Each business partner will invoke the API at the URL 58. https://api.acme.com/partnefs/vl. The API implementation is estimated to require deployment to 5 CloudHub workers.
The retailer has obtained a public X.509 certificate for the name apl.acme.com, signed by a reputable CA, to be used as the server certificate.
Where and how should the X.509 certificate and Mule applications be used to configure load balancing among the 5 CloudHub workers, and what DNS entries should be configured in order for the retailer to support its numerous business partners?
- A. Add the X.509 certificate to a CloudHub Dedicated Load Balancer (DLB), not to the Mule application Create a CNAME for api.acme.com pointing to the DLB's A record
- B. Add the X.509 certificate to the Mule application's deployable archive, then configure a CloudHub Dedicated Load Balancer (DLB) for each of the Mule application's CloudHub workers Create a CNAME for api.acme.com pointing to the DLB's A record
- C. Add the X.509 certificate to the CloudHub Shared Load Balancer (SLB), not to the Mule application Create a CNAME for api.acme.com pointing to the SLB's A record
- D. Add the x.509 certificate to the Mule application's deployable archive, then configure the CloudHub Shared Load Balancer (SLB) for each of the Mule application's CloudHub workers Create a CNAME for api.acme.com pointing to the SLB's A record
Answer: A
NEW QUESTION 35
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?
- A. Must support message acknowledgement and retry as part of the protocol
- B. Must use XML payloads for the service and ensure that it adheres to a specific schema
- C. Must secure the service, requiring all consumers to submit a valid SAML token
- D. Must publish and share the service specification (including data formats) with the consumers of the service
Answer: A
NEW QUESTION 36
Anypoint Exchange is required to maintain the source code of some of the assets committed to it, such as Connectors, Templates, and API specifications.
What is the best way to use an organization's source-code management (SCM) system in this context?
- A. Organizations need to use Anypoint Exchange as the main SCM system to centralize versioning and avoid code duplication
- B. Organizations can continue to use an SCM system of their choice for branching and merging, as long as they follow the branching and merging strategy enforced by Anypoint Exchange
- C. Organizations should continue to use an SCM system of their choice, in addition to keeping source code for these asset types in Anypoint Exchange, thereby enabling parallel development, branching, and merging
- D. Organizations need to point Anypoint Exchange to their SCM system so Anypoint Exchange can pull source code when requested by developers and provide it to Anypoint Studio
Answer: A
NEW QUESTION 37
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?
- A. Database polling continues Only HTTP requests sent to the remaining node continue to be accepted
- B. Database polling stops All HTTP requests are rejected
- C. Database polling continues All HTTP requests continue to be accepted, but requests to the failed node Incur increased latency
- D. Database polling stops All HTTP requests continue to be accepted
Answer: A
NEW QUESTION 38
A Mule application is being designed to perform product orchestration. The Mule application needs to join together the responses from an Inventory API and a Product Sales History API with the least latency.
To minimize the overall latency, what is the most idiomatic (used for its intended purpose) design to call each API request in the Mule application?
- A. Call each API request in a separate Async scope
- B. Call each API request in a separate route of a Scatter-Gather
- C. Call each API request in a separate lookup call from a DataWeave reduce operator
- D. Call each API request in a separate route of a Parallel For Each scope
Answer: B
NEW QUESTION 39
An Order microservice and a Fulfillment microservice are being designed to communicate with their dients through message-based integration (and NOT through API invocations).
The Order microservice publishes an Order message (a kind of command message) containing the details of an order to be fulfilled. The intention is that Order messages are only consumed by one Mute application, the Fulfillment microservice.
The Fulfilment microservice consumes Order messages, fulfills the order described therein, and then publishes an OrderFulfilted message (a kind of event message). Each OrderFulfilted message can be consumed by any interested Mule application, and the Order microservice is one such Mute application.
What is the most appropriate choice of message broker(s) and message destination(s) in this scenario?
- A. Older messages are sent directly to the Fulfillment microservices
OrderFulfilled messages are sent directly to the Order microservice
The Order microservice Interacts with one AMQP-compatible message broker and the Fulfillment microservice Interacts with a different AMQP-compatible message broker, so that both message brokers can be chosen and scaled to best support the toad each microservice - B. Order messages are sent to a JMS queue OrderFulfilled messages are sent to a JMS topic The Order microservice Interacts with one JMS provider (message broker) and the Fulfillment microservice interacts with a different JMS provider, so that both message brokers can be chosen and scaled to best support the load of each microservice
- C. Order messages are sent to a JMS queue OrderFulfilled messages are sent to a JMS topic Both microservices Interact with the same JMS provider (message broker) Instance, which must therefore scale to support the load of both microservices
- D. O Order messages are sent to an Anypoint MQ exchange
OrderFulfilted messages are sent to an Anypoint MQ queue
Both microservices interact with Anypoint MQ as the message broker, which must therefore scale to support the toad of both microservices
Answer: C
NEW QUESTION 40
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 API implementations are Mule applications executing in a customer -hosted Mule runtime.
End-to-end correlation of all HTTP requests and responses belonging to each individual checkout Instance is required. This is to be done through a common correlation ID, so that all log entries written by the web store backend, Experience API implementation, and Process API implementation include the same correlation ID for all requests and responses belonging to the same checkout instance.
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?
- A. 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
- B. 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 the HTTP requests and propagate It in suitable HTTP request headers
- C. 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
- D. 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
Answer: A
NEW QUESTION 41
Refer to the exhibit.
A business process involves two APIs that interact with each other asynchronously over HTTP. Each API 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?
- A. To open direct two-way communication between the Mule runtimes of both APIs
- B. To allow communication between the load balancers used by each API
- C. To authorize the certificates used by both the apis
- D. To enable communication from each API's Mule runtimes and network zone to the toad balancer of the other API
Answer: D
NEW QUESTION 42
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?
- A. Assigning Anypoint Platform permissions to a role
- B. Removing a user's access to Anypoint Platform when they no longer work for the organization
- C. Assigning Anypoint Platform role(s) to a user
- D. Controlling the business group within Anypoint Platform to which the user belongs
Answer: A
NEW QUESTION 43
Refer to the exhibit.
A Mule application has an HTTP Listener that accepts HTTP DELETE requests. This Mule application Is deployed to three CloudHub workers under the control of the CloudHub Shared Load Balancer.
A web client makes a sequence of requests to the Mule application's public URL.
How is this sequence of web client requests distributed among the HTTP Listeners running in the three CloudHub workers?
- A. Each request is routed to ONE ARBiTRARY CloudHub worker in the PRIMARY Availability Zone (AZ)
- B. Each request Is routed to ONE ARBiTRARY CloudHub worker out of ALL three CloudHub workers
- C. Each request is routed to the PRIMARY CloudHub worker in the PRIMARY Availability Zone (AZ)
- D. Each request is routed (scattered) to ALL three CloudHub workers at the same time
Answer: B
NEW QUESTION 44
What aspects of a CI/CD pipeline for Mule applications can be automated using MuleSoft-provided Maven plugins?
- A. Compile, package, unit test, deploy, create associated API instances in API Manager
- B. Import from API designer, compile, package, unit test, deploy, publish to Anypoint Exchange
- C. Compile, package, unit test, validate unit test coverage, deploy
- D. Compile, package, unit test, deploy, integration test
Answer: D
Explanation:
Explanation/Reference: http://workshop.tools.mulesoft.com/modules/module7_lab4#step-2-configure-the-mule-maven- plugin
NEW QUESTION 45
An organization is sizing an Anypoint VPC to extend their internal network to Cloudhub.
For this sizing calculation, the organization assumes 150 Mule applications will be deployed among three(3) production environments and will use Cloudhub's default zero-downtime feature. Each Mule application is expected to be configured with two(2) Cloudhub workers.This is expected to result in several Mule application deployments per hour.
- A. 10.0.0.0/24(256 IPs)
- B. 10.0.0.0/22(1024IPs)
- C. 10.0.0.0/21(2048 IPs)
- D. 10.0.0.0/23(512 IPs)
Answer: C
NEW QUESTION 46
An organization will deploy Mule applications to Cloudhub, Business requirements mandate that all application logs be stored ONLY in an external splunk consolidated logging service and NOT in Cloudhub.
In order to most easily store Mule application logs ONLY in Splunk, how must Mule application logging be configured in Runtime Manager, and where should the log4j2 splunk appender be defined?
- A. Disable Cloudhub logging in Runtime Manager
Define the splunk appender in EACH Mule application's log4j2.xml file - B. Keep the default logging configuration in Runtime Manager
Define the Splunk appender in EACH Mule application log4j2.xml file - C. Disable Cloudhub logging in Runtime Manager
Define the splunk appender in ONE global log4j.xml file that is uploaded once to Runtime Manger to support at Mule application deployments. - D. Keep the default logging configuration in RuntimeManager
Define the splunk appender in ONE global log4j.xml file that is uploaded once to Runtime Manager to support at Mule application deployments.
Answer: A
NEW QUESTION 47
......
MCIA-Level-1 dumps - TestValid - 100% Passing Guarantee: https://www.testvalid.com/MCIA-Level-1-exam-collection.html