MCIA - Level 1

MCIA - Level 1 practice questions, page 3 of 4, with answer review and explanations.

Question 11

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?

  1. Assigning Anypoint Platform permissions to a role
  2. Assigning Anypoint Platform role(s) to a user
  3. Controlling the business group within Anypoint Platform to which the user belongs
  4. Removing a user's access to Anypoint Platform when they no longer work for the organization

Question 12

An integration Mule application is deployed to a customer-hosted multi-node Mule 4 runtime cluster. The Mule application uses a Listener operation of a JMS connector to receive incoming messages from a JMS queue. How are the messages consumed by the Mule application?

  1. Regardless of the Listener operation configuration, all messages are consumed by ONLY the primary cluster node
  2. Depending on the JMS provider's configuration, either all messages are consumed by ONLY the primary cluster node or else ALL messages are consumed by ALL cluster nodes
  3. Regardless of the Listener operation configuration, all messages are consumed by ALL cluster nodes
  4. Depending on the Listener operation configuration, either all messages are consumed by ONLY the primary cluster node or else EACH message is consumed by ANY ONE cluster node

Question 13

Additional nodes are being added to an existing customer-hosted Mule runtime cluster to improve performance. Mule applications deployed to this cluster are invoked by API clients through a load balancer. What is also required to carry out this change?

  1. API implementations using an object store must be adjusted to recognize the new nodes and persist to them
  2. A new load balancer must be provisioned to allow traffic to the new nodes in a round-robin fashion
  3. External monitoring tools or log aggregators must be configured to recognize the new nodes
  4. New firewall rules must be configured to accommodate communication between API clients and the new nodes

Question 14

Refer to the exhibit. One of the backend systems invoked by an API implementation enforces rate limits on the number of requests a particular client can make. Both the backend system and the API implementation are deployed to several non-production environments in addition to production. Rate limiting of the backend system applies to all non-production environments. The production environment, however, does NOT have any rate limiting. What is the most effective approach to conduct performance tests of the API implementation in a staging (non-production) environment?

  1. Use MUnit to simulate standard responses from the backend system Then conduct performance tests to identify other bottlenecks in the system
  2. Create a mocking service that replicates the backend system's production performance characteristics Then configure the API implementation to use the mocking service and conduct the performance tests
  3. Conduct scaled-down performance tests in the staging environment against the rate limited backend system Then upscale performance results to full production scale
  4. Include logic within the API implementation that bypasses invocations of the backend system in a performance test situation, instead invoking local stubs that replicate typical backend system responses Then conduct performance tests using this API implementation

Question 15

An integration Mule application is being designed to process orders by submitting them to a backend 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 backend system. Orders that cannot be successfully submitted due to rejections from the backend system will need to be processed manually (outside the backend system). The Mule application will be deployed to a customer-hosted runtime and is able to use an existing ActiveMQ broker if needed. The backend system has a track record of unreliability both due to 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 backend system, while minimizing manual order processing?

  1. An On Error scope MuleSoft Object Store ActiveMQ Dead Letter Queue for manual processing
  2. Until Successful component ActiveMQ long retry Queue ActiveMQ Dead Letter Queue for manual processing
  3. Until Successful component MuleSoft Object Store ActiveMQ is NOT needed or used
  4. An On Error scope Non-persistent VM ActiveMQ Dead Letter Queue for manual processing