Instant Access MuleSoft.MCPA-Level-1-Maintenance.v2023-06-14.q28 Actual Practice Test Engine for Free (Page 5)

Question 16

True or False. We should always make sure that the APIs being designed and developed are self-servable even if it needs more man-day effort and resources.

A.FALSE
B.TRUE

Question 17

A company wants to move its Mule API implementations into production as quickly as possible. To protect access to all Mule application data and metadata, the company requires that all Mule applications be deployed to the company's customer-hosted infrastructure within the corporate firewall. What combination of runtime plane and control plane options meets these project lifecycle goals?

A.Manually provisioned customer-hosted runtime plane and customer-hosted control plane
B.MuleSoft-hosted runtime plane and customer-hosted control plane
C.Manually provisioned customer-hosted runtime plane and MuleSoft-hosted control plane
D.iPaaS provisioned customer-hosted runtime plane and MuleSoft-hosted control plane

Question 18

An API has been updated in Anypoint exchange by its API producer from version 3.1.1 to 3.2.0 following accepted semantic versioning practices and the changes have been communicated via the APIs public portal.
The API endpoint does NOT change in the new version. How should the developer of an API client respond to this change?

A.The API producer should be requested to run the old version in parallel with the new one
B.The API clients need to update the code on their side and need to do full regression
C.The API client code only needs to be changed if it needs to take advantage of the new features
D.The API producer should be contacted to understand the change to existing functionality

Question 19

Mule applications that implement a number of REST APIs are deployed to their own subnet that is inaccessible from outside the organization.
External business-partners need to access these APIs, which are only allowed to be invoked from a separate subnet dedicated to partners - called Partner-subnet. This subnet is accessible from the public internet, which allows these external partners to reach it.
Anypoint Platform and Mule runtimes are already deployed in Partner-subnet. These Mule runtimes can already access the APIs.
What is the most resource-efficient solution to comply with these requirements, while having the least impact on other applications that are currently using the APIs?

A.Redeploy the API implementations to the same servers running the Mule runtimes
B.Add an additional endpoint to each API for partner-enablement consumption
C.Implement (or generate) an API proxy Mule application for each of the APIs, then deploy the API proxies to the Mule runtimes
D.Duplicate the APIs as Mule applications, then deploy them to the Mule runtimes

Question 20

When could the API data model of a System API reasonably mimic the data model exposed by the corresponding backend system, with minimal improvements over the backend system's data model?

A.When there is an existing Enterprise Data Model widely used across the organization
B.When the System API can be assigned to a bounded context with a corresponding data model
C.When a pragmatic approach with only limited isolation from the backend system is deemed appropriate
D.When the corresponding backend system is expected to be replaced in the near future

Correct Answer: C

When a pragmatic approach with only limited isolation from the backend system is deemed appropriate.
*****************************************
General guidance w.r.t choosing Data Models:
>> If an Enterprise Data Model is in use then the API data model of System APIs should make use of data types from that Enterprise Data Model and the corresponding API implementation should translate between these data types from the Enterprise Data Model and the native data model of the backend system.
>> If no Enterprise Data Model is in use then each System API should be assigned to a Bounded Context, the API data model of System APIs should make use of data types from the corresponding Bounded Context Data Model and the corresponding API implementation should translate between these data types from the Bounded Context Data Model and the native data model of the backend system. In this scenario, the data types in the Bounded Context Data Model are defined purely in terms of their business characteristics and are typically not related to the native data model of the backend system. In other words, the translation effort may be significant.
>> If no Enterprise Data Model is in use, and the definition of a clean Bounded Context Data Model is considered too much effort, then the API data model of System APIs should make use of data types that approximately mirror those from the backend system, same semantics and naming as backend system, lightly sanitized, expose all fields needed for the given System API's functionality, but not significantly more and making good use of REST conventions.
The latter approach, i.e., exposing in System APIs an API data model that basically mirrors that of the backend system, does not provide satisfactory isolation from backend systems through the System API tier on its own.
In particular, it will typically not be possible to "swap out" a backend system without significantly changing all System APIs in front of that backend system and therefore the API implementations of all Process APIs that depend on those System APIs! This is so because it is not desirable to prolong the life of a previous backend system's data model in the form of the API data model of System APIs that now front a new backend system.
The API data models of System APIs following this approach must therefore change when the backend system is replaced.
On the other hand:
>> It is a very pragmatic approach that adds comparatively little overhead over accessing the backend system directly
>> Isolates API clients from intricacies of the backend system outside the data model (protocol, authentication, connection pooling, network address, ...)
>> Allows the usual API policies to be applied to System APIs
>> Makes the API data model for interacting with the backend system explicit and visible, by exposing it in the RAML definitions of the System APIs
>> Further isolation from the backend system data model does occur in the API implementations of the Process API tier

Question 16

Question 17

Question 18

Question 19

Question 20

Download PDF File