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

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

• Question 81:

  Which three tools automate the deployment of Mule applications? Choose 3 answers

  A. Runtime Manager
  B. Anypoint Platform CLI
  C. Platform APIs
  D. Anypoint Studio
  E. Mule Mayen plugin
  F. API Community Manager
  A. Runtime Manager
  B. Anypoint Platform CLI
  C. Platform APIs

  ---

  Explanation

• Question 82:

  Refer to the exhibit.

  

  A RAML definition has been proposed for a new Promotions Process API, and has been published to Anypoint Exchange.

  The Marketing Department, who will be an important consumer of the Promotions API, has important requirements and expectations that must be met.

  What is the most effective way to use Anypoint Platform features to involve the Marketing Department in this early API design phase?

  

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

  ---

  Explanation

  As per MuleSoft's IT Operating Model:

  API consumers need NOT wait until the full API implementation is ready.

  NO technical test-suites needs to be shared with end users to interact with APIs.

  Anypoint Platform offers a mocking capability on all the published API specifications to Anypoint Exchange which also will be rich in documentation covering all details of API functionalities and working nature.

  No needs of arranging days of workshops with end users for feedback.

  API consumers can use Anypoint Exchange features on the platform and interact with the API using its mocking feature. The feedback can be shared quickly on the same to incorporate any changes.

• Question 83:

  What best explains the use of auto-discovery in API implementations?

  A. It makes API Manager aware of API implementations and hence enables it to enforce policies
  B. It enables Anypoint Studio to discover API definitions configured in Anypoint Platform
  C. It enables Anypoint Exchange to discover assets and makes them available for reuse
  D. It enables Anypoint Analytics to gain insight into the usage of APIs
  A. It makes API Manager aware of API implementations and hence enables it to enforce policies

  ---

  Explanation

  API Autodiscovery is a mechanism that manages an API from API Manager by pairing the deployed application to an API created on the platform.

  API Management includes tracking, enforcing policies if you apply any, and reporting API analytics.

  Critical to the Autodiscovery process is identifying the API by providing the API name and version.

  References: https://docs.mulesoft.com/api-manager/2. x/api-auto-discovery-new-concept https://docs.mulesoft.com/api-manager/1.x/api-auto-discovery https://docs.mulesoft.com/api-manager/2. x/api-auto-discovery-new-concept

• Question 84:

  Which statement is true about Spike Control policy and Rate Limiting policy?

  A. All requests are rejected after the limit is reached in Rate Limiting policy, whereas the requests are queued in Spike Control policy after the limit is reached
  B. In a clustered environment, the Rate Limiting.and Spike Control policies are applied to each node in the cluster
  C. To protect Experience APIs by limiting resource consumption, Rate Limiting policy must be applied D. In order to apply Rate Limiting and Spike Control policies, a contract to bind client application and API is needed for both
  B. In a clustered environment, the Rate Limiting.and Spike Control policies are applied to each node in the cluster

  ---

  Explanation

• Question 85:

  Which component monitors APIs and endpoints at scheduled intervals, receives reports about whether tests pass or fail, and displays statistics about API and endpoint performance?

  A. API Analytics
  B. Anypoint Monitoring dashboards
  C. APT Functional Monitoring
  D. Anypoint Runtime Manager alerts
  C. APT Functional Monitoring

  ---

  Explanation

• Question 86:

  A system API has a guaranteed SLA of 100 ms per request. The system API is deployed to a primary environment as well as to a disaster recovery (DR) environment, with different DNS names in each environment. An upstream process API invokes the system API and the main goal of this process API is to respond to client requests in the least possible time. In what order should the system APIs be invoked, and what changes should be made in order to speed up the response time for requests from the process API?

  A. In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment, and ONLY use the first response
  B. In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment using a scatter-gather configured with a timeout, and then merge the responses
  C. Invoke the system API deployed to the primary environment, and if it fails, invoke the system API deployed to the DR environment
  D. Invoke ONLY the system API deployed to the primary environment, and add timeout and retry logic to avoid intermittent failures
  A. In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment, and ONLY use the first response

  ---

  Explanation

  The API requirement in the given scenario is to respond in least possible time.

  The option that is suggesting to first try the API in primary environment and then fallback to API in DR environment would result in successful response but NOT in least possible time. So, this is NOT a right choice of implementation for given requirement. Another option that is suggesting to ONLY invoke API in primary environment and to add timeout and retries may also result in successful response upon retries but NOT in least possible time. So, this is also NOT a right choice of

  implementation for given requirement.

  One more option that is suggesting to invoke API in primary environment and API in DR environment in parallel using Scatter-Gather would result in wrong API response as it would return merged results and moreover, Scatter-Gather does things in parallel which is true but still completes its scope only on finishing all routes inside it. So again, NOT a right choice of implementation for given requirement The Correct choice is to invoke the API in primary environment and the API in DR environment parallelly, and using ONLY the first response received from one of them.

• Question 87:

  A system API is deployed to a primary environment as well as to a disaster recovery (DR) environment, with different DNS names in each environment. A process API is a client to the system API and is being rate limited by the system API, with different limits in each of the environments. The system API's DR environment provides only 20% of the rate limiting offered by the primary environment. What is the best API fault-tolerant invocation strategy to reduce overall errors in the process API, given these conditions and constraints?

  A. Invoke the system API deployed to the primary environment; add timeout and retry logic to the process API to avoid intermittent failures; if it still fails, invoke the system API deployed to the DR environment
  B. Invoke the system API deployed to the primary environment; add retry logic to the process API to handle intermittent failures by invoking the system API deployed to the DR environment
  C. In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment; add timeout and retry logic to the process API to avoid intermittent failures; add logic to the process API to combine the results
  D. Invoke the system API deployed to the primary environment; add timeout and retry logic to the process API to avoid intermittent failures; if it still fails, invoke a copy of the process API deployed to the DR environment
  A. Invoke the system API deployed to the primary environment; add timeout and retry logic to the process API to avoid intermittent failures; if it still fails, invoke the system API deployed to the DR environment

  ---

  Explanation

  There is one important consideration to be noted in the question which is - System API in DR environment provides only 20% of the rate limiting offered by the primary environment. So, comparitively, very less calls will be allowed into the DR environment API opposed to its primary environment. With this in mind, lets analyse what is the right and best fault-tolerant invocation strategy.

  1. Invoking both the system APIs in parallel is definitely NOT a feasible approach because of the 20% limitation we have on DR environment. Calling in parallel every time would easily and quickly exhaust the rate limits on DR environment and may not give chance to genuine intermittent error scenarios to let in during the time of need.

  2. Another option given is suggesting to add timeout and retry logic to process API while invoking primary environment's system API. This is good so far. However, when all retries failed, the option is suggesting to invoke the copy of process API on DR environment which is not right or recommended. Only system API is the one to be considered for fallback and not the whole process API. Process APIs usually have lot of heavy orchestration calling many other APIs which we do not want to repeat again by calling DR's process API. So this option is NOT right.

  3. One more option given is suggesting to add the retry (no timeout) logic to process API to directly retry on DR environment's system API instead of retrying the primary environment system API first. This is not at all a proper fallback. A proper fallback should occur only after all retries are performed and exhausted on Primary environment first. But here, the option is suggesting to directly retry fallback API on first failure itself without trying main API. So, this option is NOT right too.

  This leaves us one option which is right and best fit.

  -Invoke the system API deployed to the primary environment

  -Add Timeout and Retry logic on it in process API

  - If it fails even after all retries, then invoke the system API deployed to the DR environment.

• Question 88:

  An organization is implementing a Quote of the Day API that caches today's quote.

  What scenario can use the GoudHub Object Store via the Object Store connector to persist the cache's state?

  A. When there are three CloudHub deployments of the API implementation to three separate CloudHub regions that must share the cache state
  B. When there are two CloudHub deployments of the API implementation by two Anypoint Platform business groups to the same CloudHub region that must share the cache state
  C. When there is one deployment of the API implementation to CloudHub and anottV deployment to a customer-hosted Mule runtime that must share the cache state
  D. When there is one CloudHub deployment of the API implementation to three CloudHub workers that must share the cache state
  D. When there is one CloudHub deployment of the API implementation to three CloudHub workers that must share the cache state

  ---

  Explanation

  Key details in the scenario:

  Use the CloudHub Object Store via the Object Store connector

  Considering above details:

  CloudHub Object Stores have one-to-one relationship with CloudHub Mule Applications.

  We CANNOT use an application's CloudHub Object Store to be shared among multiple Mule applications running in different Regions or Business Groups or Customer-hosted Mule Runtimes by using Object Store connector.

  If it is really necessary and very badly needed, then Anypoint Platform supports a way by allowing access to CloudHub Object Store of another application using Object Store REST API. But NOT using Object Store connector.

  So, the only scenario where we can use the CloudHub Object Store via the Object Store connector to persist the cache's state is when there is one CloudHub deployment of the API implementation to multiple CloudHub workers that must

  share the cache state.

• Question 89:

  An organization wants to create a Center for Enablement (C4E). The IT director schedules a series of meetings with IT senior managers.

  What should be on the agenda of the first meeting?

  A. Define C4E objectives, mission statement, guiding principles, a
  B. Explore API monetization options based on identified use cases through MuleSoft
  C. A walk through of common-services best practices for logging, auditing, exception handling, caching, security via policy, and rate limiting/throttling via policy
  D. Specify operating model for the MuleSoft Integrations division
  A. Define C4E objectives, mission statement, guiding principles, a

  ---

  Explanation

• Question 90:

  An organization makes a strategic decision to move towards an IT operating model that emphasizes consumption of reusable IT assets using modern APIs (as defined by MuleSoft). What best describes each modern API in relation to this new IT operating model?

  A. Each modern API has its own software development lifecycle, which reduces the need for documentation and automation
  B. Each modem API must be treated like a product and designed for a particular target audience (for instance, mobile app developers)
  C. Each modern API must be easy to consume, so should avoid complex authentication mechanisms such as SAML or JWT D
  D. Each modern API must be REST and HTTP based
  B. Each modem API must be treated like a product and designed for a particular target audience (for instance, mobile app developers)

  ---

  Explanation