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

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

• Question 101:

  An API implementation is deployed to CloudHub.

  What conditions can be alerted on using the default Anypoint Platform functionality, where the alert conditions depend on the end-to-end request processing of the API implementation?

  A. When the API is invoked by an unrecognized API client
  B. When a particular API client invokes the API too often within a given time period
  C. When the response time of API invocations exceeds a threshold
  D. When the API receives a very high number of API invocations
  C. When the response time of API invocations exceeds a threshold

  ---

  Explanation

  Alerts can be setup for all the given options using the default Anypoint Platform functionality

  However, the question insists on an alert whose conditions depend on the end-to-end request processing of the API implementation.

  Alert w.r.t "Response Times" is the only one which requires end-to-end request processing of API implementation in order to determine if the threshold is exceeded or not.

• Question 102:

  Refer to the exhibit.

  

  Three business processes need to be implemented, and the implementations need to communicate with several different SaaS applications.

  These processes are owned by separate (siloed) LOBs and are mainly independent of each other, but do share a few business entities. Each LOB has one development team and their own budget

  In this organizational context, what is the most effective approach to choose the API data models for the APIs that will implement these business processes with minimal redundancy of the data models?

  

  

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

  ---

  Explanation

  The options w.r.t building API data models using XML schema/ Agile API-centric practices are irrelevant to the scenario given in the question. So these two are INVALID. Building EDM (Enterprise Data Model) is not feasible or right fit for this scenario as the teams and LOBs work in silo and they all have different initiatives, budget etc.. Building EDM needs intensive coordination among all the team which evidently seems not possible in this scenario.

  So, the right fit for this scenario is to build several Bounded Context Data Models that align with coherent parts of the business processes and the definitions of associated business entities.

• Question 103:

  Which of the below, when used together, makes the IT Operational Model effective?

  A. 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
  B. Create reusable assets, Make them discoverable so that LOB teams can self-serve and browse the APIs, Get active feedback and usage metrics
  C. Create resuable assets, make them discoverable so that LOB teams can self-serve and browse the APIs
  C. Create resuable assets, make them discoverable so that LOB teams can self-serve and browse the APIs

  ---

  Explanation

• Question 104:

  In which layer of API-led connectivity, does the business logic orchestration reside?

  A. System Layer
  B. Experience Layer
  C. Process Layer
  C. Process Layer

  ---

  Explanation

  Experience layer is dedicated for enrichment of end user experience. This layer is to meet the needs of different API clients/ consumers. System layer is dedicated to APIs which are modular in nature and implement/ expose various individual functionalities of backend systems Process layer is the place where simple or complex business orchestration logic is written by invoking one or many System layer modular APIs So, Process Layer is the right answer.

• Question 105:

  What Anypoint Platform Capabilities listed below fall under APIs and API Invocations/Consumers category? Select TWO.

  A. API Operations and Management
  B. API Runtime Execution and Hosting
  C. API Consumer Engagement
  D. API Design and Development
  D. API Design and Development

  ---

  Explanation

  API Design and Development - Anypoint Studio, Anypoint Design Center, Anypoint Connectors API Runtime Execution and Hosting - Mule Runtimes, CloudHub, Runtime Services API Operations and Management - Anypoint API Manager, Anypoint Exchange API Consumer Management - API Contracts, Public Portals, Anypoint Exchange, API Notebooks Correct Answers: API Operations and Management and API Consumer Engagement ***************************************** API Design and Development - Anypoint Studio, Anypoint Design Center, Anypoint Connectors API Runtime Execution and Hosting - Mule Runtimes, CloudHub, Runtime Services API Operations and Management - Anypoint API Manager, Anypoint Exchange API Consumer Management - API Contracts, Public Portals, Anypoint Exchange, API Notebooks

• Question 106:

  What is a key performance indicator (KPI) that measures the success of a typical C4E that is immediately apparent in responses from the Anypoint Platform APIs?

  A. The number of production outage incidents reported in the last 24 hours
  B. The number of API implementations that have a publicly accessible HTTP endpoint and are being managed by Anypoint Platform
  C. The fraction of API implementations deployed manually relative to those deployed using a CI/CD tool
  D. The number of API specifications in RAML or OAS format published to Anypoint Exchange
  D. The number of API specifications in RAML or OAS format published to Anypoint Exchange

  ---

  Explanation

  The success of C4E always depends on their contribution to the number of reusable assets that they have helped to build and publish to Anypoint Exchange.

  It is NOT due to any factors w.r.t # of outages, Manual vs CI/CD deployments or Publicly accessible HTTP endpoints

  Anypoint Platform APIs helps us to quickly run and get the number of published RAML/OAS assets to Anypoint Exchange. This clearly depicts how successful a C4E team is based on number of returned assets in the response.

• Question 107:

  4A developer for a transportation organization is implementing exactly one processing functionality in a Reservation Mule application to process and store passenger records.

  This Reservation application will be deployed to multiple CloudHub workers/replicas. It is possible that several external systems could send duplicate passenger records to the Reservation application.

  An appropriate storage mechanism must be selected to help the Reservation application process each passenger record exactly once as much as possible.

  The selected storage mechanism must be shared by all the CloudHub workers/replicas in order to synchronize the state information to assist attempting exactly once processing of each passenger record by the deployed Reservation Mule

  application.

  Which type of simple storage mechanism in Anypoint Platform allows the Reservation Mule application to update and share data between the CloudHub workers/replicas exactly once, with minimal development effort?

  A. Persistent Object Store
  B. Runtime Fabric Object Store
  C. Non-persistent Object Store
  D. In-memory Mule Object Store
  A. Persistent Object Store

  ---

  Explanation

• Question 108:

  What API policy would be LEAST LIKELY used when designing an Experience API that is intended to work with a consumer mobile phone or tablet application?

  A. OAuth 2. 0 access token enforcement
  B. Client ID enforcement
  C. JSON threat protection
  D. IPwhitellst
  D. IPwhitellst

  ---

  Explanation

  OAuth 2. 0 access token and Client ID enforcement policies are VERY common to apply on Experience APIs as API consumers need to register and access the APIs using one of these mechanisms

  JSON threat protection is also VERY common policy to apply on Experience APIs to prevent bad or suspicious payloads hitting the API implementations.

  IP whitelisting policy is usually very common in Process and System APIs to only whitelist the IP range inside the local VPC. But also applied occassionally on some experience APIs where the End User/ API Consumers are FIXED.

  When we know the API consumers upfront who are going to access certain Experience APIs, then we can request for static IPs from such consumers and whitelist them to prevent anyone else hitting the API.

  However, the experience API given in the question/ scenario is intended to work with a consumer mobile phone or tablet application. Which means, there is no way we can know all possible IPs that are to be whitelisted as mobile phones and

  tablets can so many in number and any device in the city/state/country/globe.

  So, It is very LEAST LIKELY to apply IP Whitelisting on such Experience APIs whose consumers are typically Mobile Phones or Tablets.

• Question 109:

  An API implementation is updated. When must the RAML definition of the API also be updated?

  A. When the API implementation changes the structure of the request or response messages
  B. When the API implementation changes from interacting with a legacy backend system deployed on-premises to a modern, cloud-based (SaaS) system
  C. When the API implementation is migrated from an older to a newer version of the Mule runtime
  D. When the API implementation is optimized to improve its average response time
  A. When the API implementation changes the structure of the request or response messages

  ---

  Explanation

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

• Question 110:

  The implementation of a Process API must change.

  What is a valid approach that minimizes the impact of this change on API clients?

  A. Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition
  B. Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version
  C. Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged
  D. Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 - Moved Permanently to inform API clients they should be calling the new API implementation
  C. Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged

  ---

  Explanation

  Key requirement in the question is:

  Approach that minimizes the impact of this change on API clients

  Based on above:

  Updating the RAML definition would possibly impact the API clients if the changes require any thing mandatory from client side. So, one should try to avoid doing that until really necessary.

  Implementing the changes as a completely different API and then redirectly the clients with 3xx status code is really upsetting design and heavily impacts the API clients.

  Organisations and IT cannot simply postpone the changes required until all API consumers acknowledge they are ready to migrate to a new Process API or API version. This is unrealistic and not possible.

  The best way to handle the changes always is to implement required changes to the API implementations so that, whenever possible, the API's RAML definition remains unchanged.