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

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

• Question 151:

  Mule applications that implement a number of REST APIs are deployed to their own subnet that is inaccessible from outside the organization.

  External business-partners need to access these APIs, which are only allowed to be invoked from a separate subnet dedicated to partners - called Partner-subnet. This subnet is accessible from the public internet, which allows these external

  partners to reach it.

  Anypoint Platform and Mule runtimes are already deployed in Partner-subnet. These Mule runtimes can already access the APIs.

  What is the most resource-efficient solution to comply with these requirements, while having the least impact on other applications that are currently using the APIs?

  A. Implement (or generate) an API proxy Mule application for each of the APIs, then deploy the API proxies to the Mule runtimes
  B. Redeploy the API implementations to the same servers running the Mule runtimes
  C. Add an additional endpoint to each API for partner-enablement consumption
  D. Duplicate the APIs as Mule applications, then deploy them to the Mule runtimes
  A. Implement (or generate) an API proxy Mule application for each of the APIs, then deploy the API proxies to the Mule runtimes

  ---

  Explanation

• Question 152:

  What is a best practice when building System APIs?

  A. Document the API using an easily consumable asset like a RAML definition
  B. Model all API resources and methods to closely mimic the operations of the backend system
  C. Build an Enterprise Data Model (Canonical Data Model) for each backend system and apply it to System APIs
  D. Expose to API clients all technical details of the API implementation's interaction wifch the backend system
  B. Model all API resources and methods to closely mimic the operations of the backend system

  ---

  Explanation

  There are NO fixed and straight best practices while opting data models for APIs. They are completly contextual and depends on number of factors. Based upon those factors, an enterprise can choose if they have to go with Enterprise

  Canonical Data Model or Bounded Context Model etc.

  One should NEVER expose the technical details of API implementation to their API clients. Only the API interface/ RAML is exposed to API clients.

  It is true that the RAML definitions of APIs should be as detailed as possible and should reflect most of the documentation. However, just that is NOT enough to call your API as best documented API. There should be even more

  documentation on Anypoint Exchange with API Notebooks etc. to make and create a developer friendly API and repository..

  The best practice always when creating System APIs is to create their API interfaces by modeling their resources and methods to closely reflect the operations and functionalities of that backend system.

• Question 153:

  A Mule 4 API has been deployed to CloudHub and a Basic Authentication - Simple policy has been applied to all API methods and resources. However, the API is still accessible by clients without using authentication.

  How is this possible?

  A. The APE Router component is pointing to the incorrect Exchange version of the APT
  B. The Autodiscovery element is not present, in the deployed Mule application
  C. No... for client applications have been created of this API
  D. One of the application's CloudHub workers restarted
  B. The Autodiscovery element is not present, in the deployed Mule application

  ---

  Explanation

• Question 154:

  Version 3. 0.1 of a REST API implementation represents time values in PST time using ISO 8601 hh:mm:ss format. The API implementation needs to be changed to instead represent time values in CEST time using ISO 8601 hh:mm:ss format. When following the semver.org semantic versioning specification, what version should be assigned to the updated API implementation?

  A. 3. 0.2
  B. 4. 0.0
  C. 3. 1.0
  D. 3. 0.1
  B. 4. 0.0

  ---

  Explanation

  As per semver.org semantic versioning specification:

  Given a version number MAJOR.MINOR.PATCH, increment the:

  -MAJOR version when you make incompatible API changes.

  - MINOR version when you add functionality in a backwards compatible manner.

  -PATCH version when you make backwards compatible bug fixes.

  As per the scenario given in the question, the API implementation is completely changing its behavior. Although the format of the time is still being maintained as hh:mm:ss and there is no change in schema w.r.t format, the API will start

  functioning different after this change as the times are going to come completely different.

  Example: Before the change, say, time is going as 09:00:00 representing the PST. Now on, after the change, the same time will go as 18:00:00 as Central European Summer Time is 9 hours ahead of Pacific Time.

  This may lead to some uncertain behavior on API clients depending on how they are handling the times in the API response. All the API clients need to be informed that the API functionality is going to change and will return in CEST format.

  So, this considered as a MAJOR change and the version of API for this new change would be 4. 0.0