Salesforce Certified MuleSoft Platform Architect I Practice Test - Questions Answers, Page 6

When a pragmatic approach with only limited isolation from thebackend 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

Workers are randomly distributed across available AZs within that region. >>Currently, we only have control to choose which AWS Region to choose but there is no control at all using any configurations or deployment options to decide what Availability Zone (AZ) to assign to what worker.>>There areNOfixed or implicit rules on platform too w.r.t assignment of AZ to workers based on environment or application.>>They are completely assigned inrandom. However, cloudhub definitely ensures that HA is achieved by assigning the workers to more than on AZ so that all workers are not assigned to same AZ for same application.Bottom of FormTop of Form

The test runs immediately after the Mule application has been compiled and packaged >> Integration tests are the last layer of tests we need to add to be fully covered.>> These tests actually run against Mule running with your full configuration in place and are tested from external source as they work in PROD.>> These tests exercise the application as a whole with actual transports enabled. So, external systems are affected when these tests run.So, these tests do NOT run immediately after the Mule application has been compiled and packaged.FYI... Unit Tests are the one that run immediately after the Mule application has been compiled and packaged.

When the API implementation changes the structure of the request or response messages >> RAML definition usually needs to be touched only when there are changes in the request/response schemas or in any traits on API.>> It need not be modified for any internal changes in API implementation like performance tuning, backend system migrations etc..

Option A >> Anypoint API Manager and API policies are applicable to all types of HTTP/1.x APIs.>> They are not applicable to WebSocket APIs, HTTP/2 APIs and gRPC APIs