Free MCPA-Level-1-Maintenance – MuleSoft Certified Platform ArchitectLevel 1 MAINTENANCE Practice Test Question

Select an option, then click Submit answer.

• ○

  Anypoint Runtime Manager initiates a network connection to a Mule runtime in order to deploy Mule applications

• ○

  The MuleSoft-hosted Shared Load Balancer can be used to load balance API invocations to the Mule runtimes

• ○

  API implementations can run successfully in customer-hosted Mule runtimes, even when they are unable to communicate with the control plane

• ○

  Anypoint Runtime Manager automatically ensures HA in the control plane by creating a new Mule runtime instance in case of a node failure
  

Select an option, then click Submit answer.

• ○

  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 client creates an API consumer, which receives API invocations from an API such that they are processed for an API implementation

• ○

  The ApI consumer creates an API client, which sends API invocations to an API such that they are processed by an API implementation

• ○

  The ApI client creates an API consumer, which sends API invocations to an API such that they are processed by an API implementation
  

Select an option, then click Submit answer.

• ○

  When there are a large number of existing common assets shared by development teams

• ○

  When various teams responsible for creating APIs are new to integration and hence need extensive training

• ○

  When development is already organized into several independent initiatives or groups

• ○

  When the majority of the applications in the application network are cloud based

Select an option, then click Submit answer.

• ○

  At the experience and process tiers

• ○

  At the experience and system tiers

• ○

  At the process and system tiers

• ○

  At the experience, process, and system tiers

Select an option, then click Submit answer.

• ○

  Create a bounded-context model for every layer and overlap them when the boundary contexts overlap, letting API developers know about the differences between upstream and downstream data models

• ○

  Create a canonical model that combines the backend and API-led models to simplify and unify data models, and minimize data transformations.

• ○

  Create a bounded-context model for the system layer to closely match the backend data model, and add an anti-corruption layer to let the different bounded contexts cooperate across the system and process layers

• ○

  Create an anti-corruption layer for every API to perform transformation for every data model to match each other, and let data simply travel between APIs to avoid the complexity and overhead of building canonical models

Select an option, then click Submit answer.

• ○

  3.0.2

• ○

  4.0.0

• ○

  3.1.0

• ○

  3.0.1

Select an option, then click Submit answer.

• ○

  Implement (or generate) an API proxy Mule application for each of the APIs, then deploy the API proxies to the Mule runtimes

• ○

  Redeploy the API implementations to the same servers running the Mule runtimes

• ○

  Add an additional endpoint to each API for partner-enablement consumption

• ○

  Duplicate the APIs as Mule applications, then deploy them to the Mule runtimes
  

Select an option, then click Submit answer.

• ○

  Create reusable assets, Do marketing on the created assets across organization, Arrange time to time LOB reviews to ensure assets are being consumed or not

• ○

  Create reusable assets, Make them discoverable so that LOB teams can self-serve and browse the APIs, Get active feedback and usage metrics

• ○

  Create resuable assets, make them discoverable so that LOB teams can self-serve and browse the APIs

Select an option, then click Submit answer.

• ○

  Web Service Definition Language(WSDL)
  

• ○

  OpenAPI Specification (OAS)
  

• ○

  YAML
  

• ○

  AsyncAPI Specification
  

Select an option, then click Submit answer.

• ○

  Convince the development team of the Product API to adopt the API data model of the Order API such that the integration logic of the Order API can work with one consistent internal data model

• ○

  Work with the API data types of the Product API directly when implementing the integration logic of the Order API such that the Order API uses the same (unchanged) data types as the Product API

• ○

  Implement an anti-corruption layer in the Order API that transforms the Product API data model into internal data types of the Order API

• ○

  Start an organization-wide data modeling initiative that will result in an Enterprise Data Model that will then be used in both the Product API and the Order API