Mulesoft MuleSoft Certified Architect MCIA-LEVEL-1-MAINTENANCE Questions & Answers

• Question 181:

  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?

  A. Automated Policies in API Manager

  B. Runtime Manager agent

  C. The Mule Maven Plugin

  D. Anypoint CLI

  Correct Answer: D

  Anypoint Platform provides a scripting and command-line tool for both Anypoint Platform and Anypoint Platform Private Cloud Edition (Anypoint Platform PCE). The command-line interface (CLI) supports both the interactive shell and standard CLI modes and works with: Anypoint Exchange Access management Anypoint Runtime Manager

• Question 182:

  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. Option A

  B. Option B

  C. Option C

  D. Option D

  Correct Answer: B

  Correct answer is "The web store backend generates a new correlation ID value at the start of checkout and sets it on the XORRELATION-ID 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" : By design, Correlation Ids cannot be changed within a flow in Mule 4 applications and can be set only at source. This ID is part of the Event Context and is generated as soon as the message is received by the application. When a HTTP Request is received, the request is inspected for "X-Correlation-Id" header. If "X-Correlation-Id" header is present, HTTP connector uses this as the Correlation Id. If "X-Correlation-Id" header is NOT present, a Correlation Id is randomly generated. For Incoming HTTP Requests: In order to set a custom Correlation Id, the client invoking the HTTP request must set "X-Correlation-Id" header. This will ensure that the Mule Flow uses this Correlation Id. For Outgoing HTTP Requests: You can also propagate the existing Correlation Id to downstream APIs. By default, all outgoing HTTP Requests send "X- Correlation-Id" header. However, you can choose to set a different value to "X-Correlation- Id" header or set "Send Correlation Id" to NEVER. Mulesoft Reference: https://help.mulesoft.com/s/article/How-to-Set-Custom-Correlation-Id- for-Flows-with-HTTP-Endpoint-in-Mule-4

  

• Question 183:

  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?

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

  B. An SLA for the upstream API CANNOT be provided.

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

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

  Correct Answer: B

  An SLA for the upstream API CANNOT be provided.

• Question 184:

  An integration architect is designing an API that must accept requests from API clients for both XML and JSON content over HTTP/1.1 by default.

  Which API architectural style, when used for its intended and typical purposes, should the architect choose to meet these requirements?

  A. SOAP

  B. GraphQL

  C. REST

  D. grRPC

  Correct Answer: C

• Question 185:

  What metrics about API invocations are available for visualization in custom charts using Anypoint Analytics?

  A. Request size, request HTTP verbs, response time

  B. Request size, number of requests, JDBC Select operation result set size

  C. Request size, number of requests, response size, response time

  D. Request size, number of requests, JDBC Select operation response time

  Correct Answer: C

  Correct answer is Request size, number of requests, response size, response time Analytics API Analytics can provide insight into how your APIs are being used and how they are performing. From API Manager, you can access the Analytics dashboard, create a custom dashboard, create and manage charts, and create reports. From API Manager, you can get following types of analytics: - API viewing analytics - API events analytics - Charted metrics in API Manager It can be accessed using: http://anypoint.mulesoft.com/analytics API Analytics provides a summary in chart form of requests, top apps, and latency for a particular duration. The custom dashboard in Anypoint Analytics contains a set of charts for a single API or for all APIs Each chart displays various API characteristics ?Requests size: Line chart representing size of requests in KBs ?Requests : Line chart representing number of requests over a period ?Response size : Line chart representing size of response in KBs ?Response time :Line chart representing response time in ms

  * To check this, You can go to API Manager > Analytics > Custom Dashboard > Edit Dashboard > Create Chart > Metric

  Reference: https://docs.mulesoft.com/monitoring/api-analytics-dashboard

  Additional Information:

  The default dashboard contains a set of charts Requests by date: Line chart representing number of requests Requests by location: Map chart showing the number of requests for each country of origin Requests by application: Bar chart showing the number of requests from each of the top five registered applications Requests by platform: Ring chart showing the number of requests broken down by platform

• Question 186:

  According to MuleSoft, which system integration term describes the method, format, and protocol used for communication between two system?

  A. Component

  B. interaction

  C. Message

  D. Interface

  Correct Answer: D

• Question 187:

  A system API EmployeeSAPI is used to fetch employee's data from an underlying SQL database.

  The architect must design a caching strategy to query the database only when there is an update to the employees stable or else return a cached response in order to minimize the number of redundant transactions being handled by the

  database.

  What must the architect do to achieve the caching objective?

  A. Use an On Table Row on employees table and call invalidate cache Use an object store caching strategy and expiration interval to empty

  B. Use a Scheduler with a fixed frequency every hour triggering an invalidate cache flow Use an object store caching strategy and expiration interval to empty

  C. Use a Scheduler with a fixed frequency every hour triggering an invalidate cache flow Use an object store caching strategy and set expiration interval to 1-hour

  D. Use an on table rule on employees table call invalidate cache and said new employees data to cache Use an object store caching strategy and set expiration interval to 1-hour

  Correct Answer: A

• Question 188:

  An ABC Farms project team is planning to build a new API that is required to work with data from different domains across the organization.

  The organization has a policy that all project teams should leverage existing investments by reusing existing APIs and related resources and documentation that other project teams have already developed and deployed.

  To support reuse, where on Anypoint Platform should the project team go to discover and read existing APIs, discover related resources and documentation, and interact with mocked versions of those APIs?

  A. Design Center

  B. API Manager

  C. Runtime Manager

  D. Anypoint Exchange

  Correct Answer: D

  The mocking service is a feature of Anypoint Platform and runs continuously. You can run the mocking service from the text editor, the visual editor, and from Anypoint Exchange. You can simulate calls to the API in API Designer before publishing the API specification to Exchange or in Exchange after publishing the API specification.

  Reference: https://docs.mulesoft.com/design-center/design-mocking-service

• Question 189:

  An organization has just developed a Mule application that implements a REST API. The mule application will be deployed to a cluster of customer hosted Mule runtimes. What additional infrastructure component must the customer provide in order to distribute inbound API requests across the Mule runtimes of the cluster?

  A. A message broker

  B. An HTTP Load Balancer

  C. A database

  D. An Object Store

  Correct Answer: B

  Correct answer is An HTTP Load Balancer.

  Key thing to note here is that we are deploying application to customer hosted Mule runtime. This means we will need load balancer to route the requests to different instances of the cluster.

  Rest all options are distractors and their requirement depends on project use case.

• Question 190:

  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 the PRIMARY CloudHub worker in the PRIMARY Availability Zone (AZ)

  B. Each request is routed to ONE ARBiTRARY CloudHub worker in the PRIMARY Availability Zone (AZ)

  C. Each request Is routed to ONE ARBiTRARY CloudHub worker out of ALL three CloudHub workers

  D. Each request is routed (scattered) to ALL three CloudHub workers at the same time

  Correct Answer: C

  Correct behavior is Each request is routed to ONE ARBITRARY CloudHub worker out of ALL three CloudHub workers