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

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

• Question 101:

  Refer to the exhibit.

  

  A business process involves two APIs that interact with each other asynchronously over HTTP. Each API is implemented as a Mule application. API 1 receives the initial HTTP request and invokes API 2 (in a fire and forget fashion) while API 2, upon completion of the processing, calls back into API l to notify about completion of the asynchronous process.

  Each API Is deployed to multiple redundant Mule runtimes and a separate load balancer, and is deployed to a separate network zone.

  In the network architecture, how must the firewall rules be configured to enable the above Interaction between API 1 and API 2?

  A. To authorize the certificate to be used both APIs
  B. To enable communication from each API's Mule Runtimes and Network zone to the load balancer of the other API
  C. To open direct two-way communication between the Mule Runtimes of both API's
  D. To allow communication between load balancers used by each API
  B. To enable communication from each API's Mule Runtimes and Network zone to the load balancer of the other API

  ---

  Explanation/Reference:

  *

  If your API implementation involves putting a load balancer in front of your APIkit application, configure the load balancer to redirect URLs that reference the baseUri of the application directly. If the load balancer does not redirect URLs, any calls that reach the load balancer looking for the application do not reach their destination.

  *

  When you receive incoming traffic through the load balancer, the responses will go out the same way. However, traffic that is originating from your instance will not pass through the load balancer. Instead, it is sent directly from the public IP address of your instance out to the Internet. The ELB is not involved in that scenario.

  *

  The question says "each API is deployed to multiple redundant Mule runtimes", that seems to be a hint for self hosted Mule runtime cluster. Set Inbound allowed for the LB, outbound allowed for runtime to request out.

  *

  Hence correct way is to enable communication from each API's Mule Runtimes and Network zone to the load balancer of the other API. Because communication is asynchronous one Reference: https://docs.mulesoft.com/apikit/4.x/ configure-load-balancer-task

• Question 102:

  An organization has just developed a Mule application that implements a REST API. The mule application will be deployed to a cluster of customer hosted Mule runtimes.

  What additional infrastructure component must the customer provide in order to distribute inbound API requests across the Mule runtimes of the cluster?

  A. A message broker
  B. An HTTP Load Balancer
  C. A database
  D. An Object Store
  B. An HTTP Load Balancer

  ---

  Explanation/Reference:

  Correct answer is An HTTP Load Balancer.

  Key thing to note here is that we are deploying application to customer hosted Mule runtime. This means we will need load balancer to route the requests to different instances of the cluster.

  Rest all options are distractors and their requirement depends on project use case.

• Question 103:

  Which productivity advantage does Anypoint Platform have to both implement and manage an AP?

  A. Automatic API proxy generation
  B. Automatic API specification generation
  C. Automatic API semantic versioning
  D. Automatic API governance
  A. Automatic API proxy generation

• Question 104:

  A rale limiting policy has been applied to a soap VI.2 API published in Clondhub. The API implementation catches errors in a global error handler on error propagate in the main flow for HTTP: RETRY_EXHAUSTED with HTTP status set to 429 and any with the HTTP status set to 500.

  What is the expected H1TP status when the client exceeds the quota of the API calls?

  A. HTTP status 429 as defined in the HTTP:RETRY EXHAUSTED error handler in the API
  B. HTTP status 500 as defined in the ANY error handler in the API since an API:RETRY_EXHAUSTED will be generated
  C. HTTP status 401 unauthorized for policy violation
  D. HTTP status 400 from the rate-limiting policy violation since the call does not reach the back-end
  A. HTTP status 429 as defined in the HTTP:RETRY EXHAUSTED error handler in the API

  ---

  Explanation/Reference:

  In the given scenario, a rate limiting policy has been applied to the SOAP API and a global error handler is configured to handle HTTP:RETRY_EXHAUSTED errors with a 429 status code. The rate limiting policy will trigger when the client exceeds the allowed quota of API calls. Since the HTTP:RETRY_EXHAUSTED error specifically catches quota exhaustion errors and the error handler is configured to return a 429 status code, the expected HTTP status returned to the client when the quota is exceeded will be 429. This error code indicates that the user has sent too many requests in a given amount of time ("rate limiting"). References: MuleSoft Documentation on Error Handling HTTP Status Codes

• Question 105:

  An API has been updated in Anypoint Exchange by its API producer from version 3.1.1 to 3.2.0 following accepted semantic versioning practices and the changes have been communicated via the API's public portal. The API endpoint does NOT change in the new version. How should the developer of an API client respond to this change?

  A. The update should be identified as a project risk and full regression testing of the functionality that uses this API should be run.
  B. The API producer should be contacted to understand the change to existing functionality.
  C. The API producer should be requested to run the old version in parallel with the new one.
  D. The API client code ONLY needs to be changed if it needs to take advantage of new features.
  D. The API client code ONLY needs to be changed if it needs to take advantage of new features.

  ---

  Explanation/Reference:

  * Semantic Versioning is a 3-component number in the format of X.Y.Z, where :

  X stands for a major version.

  Y stands for a minor version:

  Z stands for a patch.

  So, SemVer is of the form Major.Minor.Patch Coming to our question , minor version of the API has been changed which is backward compatible. Hence there is no change required on API client end. If they want to make use of new featured

  that have been added as a part of minor version change they may need to change code at their end. Hence correct answer is The API client code ONLY needs to be changed if it needs to take advantage of new features.

  

• Question 106:

  A company wants its users to log in to Anypoint Platform using the company's own internal user credentials. To achieve this, the company needs to integrate an external identity provider (IdP) with the company's Anypoint Platform master organization, but SAML 2.0 CANNOT be used. Besides SAML 2.0, what single-sign-on standard can the company use to integrate the IdP with their Anypoint Platform master organization?

  A. SAML 1.0
  B. OAuth 2.0
  C. Basic Authentication
  D. OpenID Connect
  D. OpenID Connect

  ---

  Explanation/Reference:

  As the Anypoint Platform organization administrator, you can configure identity management in Anypoint Platform to set up users for single sign-on (SSO). Configure identity management using one of the following single sign-on standards: 1) OpenID Connect: End user identity verification by an authorization server including SSO 2) SAML 2.0: Web-based authorization including cross-domain SSO

• Question 107:

  A new Mule application under development must implement extensive data transformation logic. Some of the data transformation functionality is already available as external transformation services that are mature and widely used across the organization; the rest is highly specific to the new Mule application.

  The organization follows a rigorous testing approach, where every service and application must be extensively acceptance tested before it is allowed to go into production.

  What is the best way to implement the data transformation logic for this new Mule application while minimizing the overall testing effort?

  A. Implement and expose all transformation logic as mlaoservices using DataWeave, so it can be reused by any application component that needs it, including the new Mule application
  B. Implement transformation logic in the new Mute application using DataWeave, replicating the transformation logic of existing transformation services
  C. Extend the existing transformation services with new transformation logic and Invoke them from the new Mule application
  D. Implement transformation logic in the new Mute application using DataWeave, invoking existing transformation services when possible
  D. Implement transformation logic in the new Mute application using DataWeave, invoking existing transformation services when possible

  ---

  Explanation/Reference:

  Correct answer is Implement transformation logic in the new Mule application using DataWeave, invoking existing transformation services when possible. * The key here minimal testing effort, "Extend existing transformation logic" is not a feasible option because additional functionality is highly specific to the new Mule application so it should not be a part of commonly used functionality. So this option is ruled out. * "Implement transformation logic in the new Mule application using DataWeave, replicating the transformation logic of existing transformation services" Replicating the transformation logic of existing transformation services will cause duplicity of code. So this option is ruled out. * "Implement and expose all transformation logic as microservices using DataWeave, so it can be reused by any application component that needs it, including the new Mule application" as question specifies that the transformation is app specific and wont be used outside

• Question 108:

  A MuteSoft developer must implement an API as a Mule application, run the application locally, and execute unit tests against the Running application.

  Which Anypoint Platform component can the developer use to full all of these requirements?

  A. API Manager
  B. API Designer
  C. Anypoint CLI
  D. Anypoint Studio
  D. Anypoint Studio

  ---

  Explanation/Reference:

  A MuleSoft developer can use Anypoint Studio to implement an API as a Mule application, run the application locally, and execute unit tests against the running application. Anypoint Studio is an integrated development environment (IDE) for designing, building, testing, and deploying Mule applications. It provides tools for local development and testing, including MUnit for creating and running unit tests, making it a comprehensive solution for developing MuleSoft applications. References: Anypoint Studio Overview Using MUnit for Unit Testing

• Question 109:

  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 invocation of the fallback API provides the best resilience?

  A. Redirect client requests through an HTTP 303 temporary redirect status code to the fallback API whenever the Order API is unavailable
  B. 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 received from Order API
  C. 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
  D. Search Anypoint Exchange for a suitable existing fallback API and them implement invocations to their fallback API in addition to the Order API
  A. Redirect client requests through an HTTP 303 temporary redirect status code to the fallback API whenever the Order API is unavailable

  ---

  Explanation/Reference:

  *

  Resilience testing is a type of software testing that observes how applications act under stress. It's meant to ensure the product's ability to perform in chaotic conditions without a loss of core functions or data; it ensures a quick recovery after

  unforeseen, uncontrollable events.

  *

  In case an API invocation fails --even after a certain number of retries --it might be adequate to invoke a different API as a fallback. A fallback API, by definition, will never be ideal for the purpose of the API client, otherwise it would be the

  primary API.

  *

  Here are some examples for fallback APIs:

  -An old, deprecated version of the same API.

  -An alternative endpoint of the same API and version (e.g. API in another CloudHub region).

  -An API doing more than required, and therefore not as performant as the primary API.

  -An API doing less than required and therefore forcing the API Client to offer a degraded service, which is still better than no service at all.

  *

  API clients implemented as Mule applications offer the `Until Successful Scope and Exception' strategies at their disposal, which together allow configuring fallback actions such as a fallback API invocation.

  *

  All HTTP response status codes within the 3xx category are considered redirection messages. These codes indicate to the user agent (i.e. your web browser) that an additional action is required in order to complete the request and access

  the desired resource

  

  Hence correct answer is Redirect client requests through an HTTP 303 temporary redirect status code to the fallback API whenever the Order API is unavailable

• Question 110:

  An organization has implemented a continuous integration (CI) lifecycle that promotes Mule applications through code, build, and test stages. To standardize the organization's CI journey, a new dependency control approach is being designed to store artifacts that include information such as dependencies, versioning, and build promotions. To implement these process improvements, the organization will now require developers to maintain all dependencies related to Mule application code in a shared location.

  What is the most idiomatic (used for its intended purpose) type of system the organization should use in a shared location to standardize all dependencies related to Mule application code?

  A. A MuleSoft-managed repository at repository.mulesoft.org
  B. A binary artifact repository
  C. API Community Manager
  D. The Anypoint Object Store service at cloudhub.io
  C. API Community Manager