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

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

• Question 41:

  An application updates an inventory running only one process at any given time to keep the inventory consistent. This process takes 200 milliseconds (.2 seconds) to execute; therefore, the scalability threshold of the application is five requests per second. What is the impact on the application if horizontal scaling is applied, thereby increasing the number of Mule workers?

  A. The application scalability threshold is five requests per second regardless of the horizontal scaling
  B. The total process execution time is now 100 milliseconds (.1 seconds)
  C. The application scalability threshold is now 10 requests per second D. Horizontal scaling cannot be applied to an already-running application
  A. The application scalability threshold is five requests per second regardless of the horizontal scaling

  ---

  Explanation

• Question 42:

  Refer to the exhibit.

  

  What is the best way to decompose one end-to-end business process into a collaboration of Experience, Process, and System APIs?

  

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

  ---

  Explanation

  All customizations for the end-user application should be handled in "Experience API" only. Not in Process API

  We should use tiered approach but NOT always by creating exactly one API for each of the 3 layers. Experience APIs might be one but Process APIs and System APIs are often more than one. System APIs for sure will be more than one all the time as they are the smallest modular APIs built in front of end systems.

  Process APIs can call System APIs as well as other Process APIs. There is no such anti-design pattern in API-Led connectivity saying Process APIs should not call other Process APIs. So, the right answer in the given set of options that makes sense as per API-Led connectivity principles is to allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs. This way, some future Process APIs can make use of that data from System APIs and we need NOT touch the System layer APIs again and again.

• Question 43:

  A Platform Architect inherits a legacy monolithic SOAP-based web service that performs a number of tasks, including showing all policies belonging to a client.

  The service connects to two back-end systems -- a life-insurance administration system and a general-insurance administration system -- and then queries for insurance policy information within each system, aggregates the results, and

  presents a SOAP-based response to a user interface (UI).

  The architect wants to break up the monolithic web service to follow API-led conventions.

  Which part of the service should be put into the process layer?

  A. Combining the insurance policy information from the administration systems
  B. Presenting the SOAP-based response to the UI
  C. Authenticating and maintaining connections to each of the back-end administration systems
  D. Querying the data from the administration systems
  A. Combining the insurance policy information from the administration systems

  ---

  Explanation

• Question 44:

  What Anypoint Connectors support transactions?

  A. Database, JMS, VM
  B. Database, 3MS, HTTP
  C. Database, JMS, VM, SFTP
  D. Database, VM, File
  A. Database, JMS, VM

  ---

  Explanation

• Question 45:

  An organization has implemented a Customer Address API to retrieve customer address information. This API has been deployed to multiple environments and has been configured to enforce client IDs everywhere.

  A developer is writing a client application to allow a user to update their address. The developer has found the Customer Address API in Anypoint Exchange and wants to use it in their client application.

  What step of gaining access to the API can be performed automatically by Anypoint Platform?

  A. Approve the client application request for the chosen SLA tier
  B. Request access to the appropriate API Instances deployed to multiple environments using the client application's credentials
  C. Modify the client application to call the API using the client application's credentials
  E. Create a new application in Anypoint Exchange for requesting access to the API
  A. Approve the client application request for the chosen SLA tier

  ---

  Explanation

  Only approving the client application request for the chosen SLA tier can be automated Rest of the provided options are not valid

• Question 46:

  What is a key requirement when using an external Identity Provider for Client Management in Anypoint Platform?

  A. Single sign-on is required to sign in to Anypoint Platform
  B. The application network must include System APIs that interact with the Identity Provider
  C. To invoke OAuth 2. 0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider
  D. APIs managed by Anypoint Platform must be protected by SAML 2. 0 policies
  C. To invoke OAuth 2. 0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider

  ---

  Explanation

  It is NOT necessary that single sign-on is required to sign in to Anypoint Platform because we are using an external Identity Provider for Client Management It is NOT necessary that all APIs managed by Anypoint Platform must be protected by SAML 2. 0 policies because we are using an external Identity Provider for Client Management Not TRUE that the application network must include System APIs that interact with the Identity Provider because we are using an external Identity Provider for Client Management Only TRUE statement in the given options is - "To invoke OAuth 2. 0-protected APIs managed by Anypoint Platform, API clients must submit access tokens issued by that same Identity Provider" References:

  https://docs.mulesoft.com/api-manager/2. x/external-oauth-2. 0-token-validation-policy https://blogs.mulesoft.com/dev/api-dev/api-security-ways-to-authenticate-and-authorize/

• Question 47:

  A retail company with thousands of stores has an API to receive data about purchases and insert it into a single database. Each individual store sends a batch of purchase data to the API about every 30 minutes. The API implementation uses a database bulk insert command to submit all the purchase data to a database using a custom JDBC driver provided by a data analytics solution provider. The API implementation is deployed to a single CloudHub worker. The JDBC driver processes the data into a set of several temporary disk files on the CloudHub worker, and then the data is sent to an analytics engine using a proprietary protocol. This process usually takes less than a few minutes. Sometimes a request fails. In this case, the logs show a message from the JDBC driver indicating an out-of-file-space message. When the request is resubmitted, it is successful. What is the best way to try to resolve this throughput issue?

  A. se a CloudHub autoscaling policy to add CloudHub workers
  B. Use a CloudHub autoscaling policy to increase the size of the CloudHub worker
  C. Increase the size of the CloudHub worker(s)
  D. Increase the number of CloudHub workers
  D. Increase the number of CloudHub workers

  ---

  Explanation

  The key details that we can take out from the given scenario are:

  API implementation uses a database bulk insert command to submit all the purchase data to a database

  JDBC driver processes the data into a set of several temporary disk files on the CloudHub worker

  Sometimes a request fails and the logs show a message indicating an out-of-file-space message

  Based on above details:

  Both auto-scaling options does NOT help because we cannot set auto-scaling rules based on error messages. Auto-scaling rules are kicked-off based on CPU/Memory usages and not due to some given error or disk space issues.

  Increasing the number of CloudHub workers also does NOT help here because the reason for the failure is not due to performance aspects w.r.t CPU or Memory. It is due to disk-space.

  Moreover, the API is doing bulk insert to submit the received batch data. Which means, all data is handled by ONE worker only at a time. So, the disk space issue should be tackled on "per worker" basis. Having multiple workers does not

  help as the batch may still fail on any worker when disk is out of space on that particular worker.

  Therefore, the right way to deal this issue and resolve this is to increase the vCore size of the worker so that a new worker with more disk space will be provisioned.

• Question 48:

  An API implementation is being designed that must invoke an Order API, which is known to repeatedly experience downtime.

  For this reason, a fallback API is to be called when the Order API is unavailable.

  What approach to designing the invocation of the fallback API provides the best resilience?

  A. Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the Order API
  B. Create a separate entry for the Order API in API Manager, and then invoke this API as a fallback API if the primary Order API is unavailable
  C. Redirect client requests through an HTTP 307 Temporary Redirect status code to the fallback API whenever the Order API is unavailable
  D. Set an option in the HTTP Requester component that invokes the Order API to instead invoke a fallback API whenever an HTTP 4xx or 5xx response status code is returned from the Order API
  A. Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the Order API

  ---

  Explanation

  It is not ideal and good approach, until unless there is a pre-approved agreement with the API clients that they will receive a HTTP 3xx temporary redirect status code and they have to implement fallback logic their side to call another API.

  Creating separate entry of same Order API in API manager would just create an another instance of it on top of same API implementation. So, it does NO GOOD by using clone od same API as a fallback API. Fallback API should be ideally a

  different API implementation that is not same as primary one. There is NO option currently provided by Anypoint HTTP Connector that allows us to invoke a fallback API when we receive certain HTTP status codes in response.

  The only statement TRUE in the given options is to Search Anypoint exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the order API.

• Question 49:

  A System API is designed to retrieve data from a backend system that has scalability challenges. What API policy can best safeguard the backend system?

  A. IPwhitelist
  B. SLA-based rate limiting
  C. Auth 2 token enforcement
  D. Client ID enforcement
  B. SLA-based rate limiting

  ---

  Explanation

  Client Id enforement policy is a "Compliance" related NFR and does not help in maintaining the "Quality of Service (QoS)". It CANNOT and NOT meant for protecting the backend systems from scalability challenges.

  IP Whitelisting and OAuth 2. 0 token enforcement are "Security" related NFRs and again does not help in maintaining the "Quality of Service (QoS)". They CANNOT and are NOT meant for protecting the backend systems from scalability

  challenges.

  Rate Limiting, Rate Limiting-SLA, Throttling, Spike Control are the policies that are "Quality of Service (QOS)" related NFRs and are meant to help in protecting the backend systems from getting overloaded.

  https://dzone.com/articles/how-to-secure-apis

• Question 50:

  Which layer in the API-led connectivity focuses on unlocking key systems, legacy systems, data sources etc and exposes the functionality?

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

  ---

  Explanation

  The APIs used in an API-led approach to connectivity fall into three categories:

  System APIs ?these usually access the core systems of record and provide a means of insulating the user from the complexity or any changes to the underlying systems. Once built, many users, can access data without any need to learn the underlying systems and can reuse these APIs in multiple projects.

  Process APIs ?These APIs interact with and shape data within a single system or across systems (breaking down data silos) and are created here without a dependence on the source systems from which that data originates, as well as the target channels through which that data is delivered.

  Experience APIs ?Experience APIs are the means by which data can be reconfigured so that it is most easily consumed by its intended audience, all from a common data source, rather than setting up separate point-to-point integrations for each channel. An Experience API is usually created with API-first design principles where the API is designed for the specific user experience in mind.