Last Attempt MCIA-Level-1 Questions

Page: 19 / 20

Question 76

When a Mule application using VM queues is deployed to a customer-hosted cluster or multiple CloudHub v1.0 workers/replicas, how are messages consumed across the nodes?

Options:

Sequentially, from a dedicated Anypoint MQ queue

Sequentially, only from the primary node

In a non-deterministic way

Round-robin, within an XA transaction

Question 77

A project team uses RAML specifications to document API functional requirements and deliver API definitions. As per the current legal requirement, all designed API definitions to be augmented with an additional non-functional requirement to protect the services from a high rate of requests according to define service level agreements.

Assuming that the project is following Mulesoft API governance and policies, how should the project team convey the necessary non-functional requirement to stakeholders?

Options:

Create proxies in API manager for the non functional requirement and publish to exchange

Add all non functional requirements as comments to RAML specification and publish to exchange

Create various SLA's in API manager for the non functional requirement and publish to exchange

Update API definitions with the fragment for the appropriate policy and publish to exchange

Question 78

An organization has deployed both Mule and non-Mule API implementations to integrate its customer and order management systems. All the APIs are available to REST clients on the public internet.

The organization wants to monitor these APIs by running health checks: for example, to determine if an API can properly accept and process requests. The organization does not have subscriptions to any external monitoring tools and also does not want to extend its IT footprint.

What Anypoint Platform feature provides the most idiomatic (used for its intended purpose) way to monitor the availability of both the Mule and the non-Mule API implementations?

Options:

API Functional Monitoring

Runtime Manager

API Manager

Anypoint Visualizer

Question 79

An organization has decided on a cloudhub migration strategy that aims to minimize the organizations own IT resources. Currently, the organizational has all of its Mule applications running on its own premises and uses an premises load balancer that exposes all APIs under the base URL

As part of the migration strategy, the organization plans to migrate all of its Mule applications and load balancer to cloudhub

What is the most straight-forward and cost effective approach to the Mule applications deployment and load balancing that preserves the public URLs?

Options:

Deploy the Mule applications to Cloudhub

Update the CNAME record for an api.acme.com in the organizations DNS server pointing to the A record of a cloudhub dedicated load balancer(DLB)

Apply mapping rules in the DLB to map URLs to their corresponding Mule applications

For each migrated Mule application, deploy an API proxy Mule application to Cloudhub with all applications under the control of a dedicated load balancer(CLB)

Update the CNAME record for api.acme.com in the organization DNS server pointing to the A record of a cloudhub dedicated load balancer(DLB)

Apply mapping rules in the DLB to map each API proxy application to its corresponding Mule applications

Deploy the Mule applications to Cloudhub

Create CNAME record for api.acme.com in the Cloudhub Shared load balancer (SLB) pointing to the A record of the on-premise load balancer

Apply mapping rules in the SLB to map URLs to their corresponding Mule applications

Deploy the Mule applications to Cloudhub

Update the CNAME record for api.acme.com in the organization DNS server pointing to the A record of the cloudhub shared load balancer(SLB)

Apply mapping rules in the SLB to map URLs to their corresponding Mule applications.