Salesforce MULESOFT-PLATFORM-ARCHITECT-I Online Practice Questions and Exam Preparation

Salesforce MULESOFT-PLATFORM-ARCHITECT-I Online Questions & Answers

• Question 71:

  A business process is being implemented within an organization's application network. The architecture group proposes using a more coarse-grained application network design with relatively fewer APIs deployed to the application network compared to a more fine-grained design.

  Overall, which factor typically increases with a more coarse-grained design for this business process implementation and deployment compared with using a more fine-grained design?

  A. The complexity of each API implementation
  B. The number of discoverable assets related to APIs deployed in the application network
  C. The number of possible connections between API implementations in the application network
  D. The usage of network infrastructure resources by the application network
  A. The complexity of each API implementation

  ---

  Explanation

• Question 72:

  The Line of Business (LoB) of an eCommerce company is requesting a process that sends automated notifications via email every time a new order is processed through the customer's mobile application or through the internal company's web application. In the future, multiple notification channels may be added: for example, text messages and push notifications.

  What is the most effective API-led connectivity approach for the scenario described above?

  

  A. Create one Experience API for the web application and one for the mobile application. Create a Process API to orchestrate and retrieve the email template from = database. Create a System API that sends the email using the Anypoint Connector for Email.
  B. Create one Experience API for the web application and one for the mobile application. Create a Process API to orchestrate, retrieve the email template from a database, and send the email using the Anypoint Connector for Email.
  C. Create Experience APIs for both the web application and mobile application. Create a Process API ta orchestrate, retrieve the email template from e database, and send the email using the Anypoint Connector for Email.
  D. Create Experience APIs for both the web application and mobile application. (Create 3 Process API to orchestrate and retrieve the email template from 2 databese. Create a System API that sends the email using the Anypoint Connector for Email.
  A. Create one Experience API for the web application and one for the mobile application. Create a Process API to orchestrate and retrieve the email template from = database. Create a System API that sends the email using the Anypoint Connector for Email.

  ---

  Explanation

• Question 73:

  An organization uses various cloud-based SaaS systems and multiple on-premises systems. The on-premises systems are an important part of the organization's application network and can only be accessed from within the organization's intranet.

  What is the best way to configure and use Anypoint Platform to support integrations with both the cloud-based SaaS systems and on-premises systems?

  

  A. Option A
  B. Option B
  C. Option C
  D. Option D
  B. Option B

  ---

  Explanation

  Key details to be taken from the given scenario: Organization uses BOTH cloud-based and on-premises systems On-premises systems can only be accessed from within the organization's intranet Let us evaluate the given choices based on above key details: CloudHub-deployed Mule runtimes can ONLY be controlled using MuleSoft-hosted control plane. We CANNOT use Private Cloud Edition's control plane to control CloudHub Mule Runtimes. So, option suggesting this is INVALID

  Using CloudHub-deployed Mule runtimes in the shared worker cloud managed by the MuleSoft-hosted Anypoint Platform is completely IRRELEVANT to given scenario and silly choice. So, option suggesting this is INVALID

  Using an on-premises installation of Mule runtimes that are completely isolated with NO external network access, managed by the Anypoint Platform Private Cloud Edition control plane would work for On-premises integrations. However, with NO external access, integrations cannot be done to SaaS-based apps. Moreover CloudHub-hosted apps are best-fit for integrating with SaaS-based applications. So, option suggesting this is BEST WAY. The best way to configure and use Anypoint Platform to support these mixed/hybrid integrations is to use a combination of CloudHub-deployed and manually provisioned on-premises Mule runtimes managed by the MuleSoft-hosted Platform

  control plane.

• Question 74:

  A TemperatureSensors API instance is defined in API Manager in the PROD environment of the CAR_FACTORY business group. An AcmelemperatureSensors Mule application implements this API instance and is deployed from Runtime

  Manager to the PROD environment of the CAR_FACTORY business group.

  A policy that requires a valid client ID and client secret is applied in API Manager to the API instance.

  Where can an API consumer obtain a valid client ID and client secret to call the AcmeTemperatureSensors Mule application?

  A. In secrets manager, request access to the Shared Secret static username/password
  B. In API Manager, from the PROD environment of the CAR_FACTORY business group
  C. In access management, from the PROD environment of the CAR_FACTORY business group
  D. In Anypoint Exchange, from an API client application that has been approved for the TemperatureSensors API instance
  D. In Anypoint Exchange, from an API client application that has been approved for the TemperatureSensors API instance

  ---

  Explanation

• Question 75:

  When can CloudHub Object Store v2 be used?

  A. To store an unlimited number of key-value pairs
  B. To store payloads with an average size greater than 15MB
  C. To store information in Mule 4 Object Store v1
  D. To store key-value pairs with keys up to 300 characters
  D. To store key-value pairs with keys up to 300 characters

  ---

  Explanation

• Question 76:

  An API implementation is deployed on a single worker on CloudHub and invoked by external API clients (outside of CloudHub). How can an alert be set up that is guaranteed to trigger AS SOON AS that API implementation stops responding to API invocations?

  A. Implement a heartbeat/health check within the API and invoke it from outside the Anypoint Platform and alert when the heartbeat does not respond
  B. Configure a "worker not responding" alert in Anypoint Runtime Manager
  C. Handle API invocation exceptions within the calling API client and raise an alert from that API client when the API Is unavailable
  D. Create an alert for when the API receives no requests within a specified time period
  B. Configure a "worker not responding" alert in Anypoint Runtime Manager

  ---

  Explanation

  All the options eventually helps to generate the alert required when the application stops responding. However, handling exceptions within calling API and then raising alert from API client is inappropriate and silly. There could be many API clients invoking the API implementation and it is not ideal to have this setup consistently in all of them. Not a realistic way to do.

  Implementing a health check/ heartbeat with in the API and calling from outside to detmine the health sounds OK but needs extra setup for it and same time there are very good chances of generating false alarms when there are any intermittent network issues between external tool calling the health check API on API implementation. The API implementation itself may not have any issues but due to some other factors some false alarms may go out.

  Creating an alert in API Manager when the API receives no requests within a specified time period would actually generate realistic alerts but even here some false alarms may go out when there are genuinely no requests from API clients.

  The best and right way to achieve this requirement is to setup an alert on Runtime Manager with a condition "Worker not responding". This would generate an alert AS SOON AS the workers become unresponsive.

• Question 77:

  How are an API implementation, API client, and API consumer combined to invoke and process an API?

  A. The API consumer creates an API implementation, which receives API invocations from an API such that they are processed for an API client
  B. The API client creates an API consumer, which receives API invocations from an API such that they are processed for an API implementation
  C. The ApI consumer creates an API client, which sends API invocations to an API such that they are processed by an API implementation
  D. The ApI client creates an API consumer, which sends API invocations to an API such that they are processed by an API implementation
  C. The ApI consumer creates an API client, which sends API invocations to an API such that they are processed by an API implementation

  ---

  Explanation

  Terminology:

  API Client - It is a piece of code or program the is written to invoke an API

  API Consumer - An owner/entity who owns the API Client. API Consumers write API clients.

  API - The provider of the API functionality. Typically an API Instance on API Manager where they are managed and operated.

  API Implementation - The actual piece of code written by API provider where the functionality of the API is implemented. Typically, these are Mule Applications running on Runtime Manager.

• Question 78:

  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
  B. TRUE

  ---

  Explanation

  As per MuleSoft proposed IT Operating Model, designing APIs and making sure that they are discoverable and self-servable is VERY VERY IMPORTANT and decides the success of an API and its application network.

• Question 79:

  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
  C. When a pragmatic approach with only limited isolation from the backend system is deemed appropriate

  ---

  Explanation

  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 80:

  A code-centric API documentation environment should allow API consumers to investigate and execute API client source code that demonstrates invoking one or more APIs as part of representative scenarios. What is the most effective way to provide this type of code-centric API documentation environment using Anypoint Platform?

  A. Enable mocking services for each of the relevant APIs and expose them via their Anypoint Exchange entry
  B. Ensure the APIs are well documented through their Anypoint Exchange entries and API Consoles and share these pages with all API consumers
  C. Create API Notebooks and include them in the relevant Anypoint Exchange entries
  D. Make relevant APIs discoverable via an Anypoint Exchange entry
  C. Create API Notebooks and include them in the relevant Anypoint Exchange entries

  ---

  Explanation

  API Notebooks are the one on Anypoint Platform that enable us to provide code-centric API documentation