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

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

• Question 161:

  A trading company handles millions of requests a day. Due to nature of its business, it requires excellent performance and reliability within its application.

  For this purpose, company uses a number of event-based API's hosted on various mule clusters that communicate across a shared message queue sitting within its network.

  Which method should be used to meet the company's requirement for its system?

  A. XA transactions and XA connected components
  B. JMS transactions
  C. JMS manual acknowledgements with a reliability pattern
  D. VM queues with reliability pattern
  B. JMS transactions

  ---

  Explanation/Reference:

  For handling millions of requests per day with high performance and reliability, JMS (Java Message Service) transactions are the most suitable method. JMS transactions ensure that messages are processed reliably and can be rolled back in

  case of failures, providing transactional integrity. This is crucial for a trading company where reliable message processing is critical. Using JMS transactions within Mule clusters allows for the decoupling of message producers and consumers,

  improving scalability and fault tolerance. JMS provides built-in mechanisms for handling transactional messaging, ensuring that messages are processed once and only once, even in the event of system failures.

  References:

  MuleSoft Documentation on JMS

• Question 162:

  An organization's governance process requires project teams to get formal approval from all key stakeholders for all new Integration design specifications. An integration Mule application Is being designed that interacts with various backend systems. The Mule application will be created using Anypoint Design Center or Anypoint Studio and will then be deployed to a customer-hosted runtime.

  What key elements should be included in the integration design specification when requesting approval for this Mule application?

  A. SLAs and non-functional requirements to access the backend systems
  B. Snapshots of the Mule application's flows, including their error handling
  C. A list of current and future consumers of the Mule application and their contact details
  D. The credentials to access the backend systems and contact details for the administrator of each system
  A. SLAs and non-functional requirements to access the backend systems

  ---

  Explanation/Reference:

  SLAs and non-functional requirements to access the backend systems. Only this option actually speaks to design parameters and reqs. * Below two are technical implementations and not the part of design: -Snapshots of the Mule application's flows, including their error handling -The credentials to access the backend systems and contact details for the administrator of each system * List of consumers is not relevant to the design

• Question 163:

  An integration architect is designing an API that must accept requests from API clients for both XML and JSON content over HTTP/1.1 by default.

  Which API architectural style, when used for its intended and typical purposes, should the architect choose to meet these requirements?

  A. SOAP
  B. GraphQL
  C. REST
  D. grRPC
  C. REST

  ---

  Explanation/Reference:

  REST (Representational State Transfer) is an architectural style for designing networked applications. It supports multiple content types, including XML and JSON, making it suitable for APIs that need to handle requests from clients in both formats. RESTful APIs use standard HTTP methods (GET, POST, PUT, DELETE) and are designed to be stateless and scalable. REST's flexibility and wide adoption make it an appropriate choice for the integration architect's requirements. References: REST API Design Understanding RESTful API Design

• Question 164:

  What Mule application can have API policies applied by Anypoint Platform to the endpoint exposed by that Mule application?

  A. A Mule application that accepts requests over HTTP/1x
  B. A Mule application that accepts JSON requests over TCP but is NOT required to provide a response.
  C. A Mule application that accepts JSON requests over WebSocket
  D. A Mule application that accepts gRPC requests over HTTP/2
  A. A Mule application that accepts requests over HTTP/1x

  ---

  Explanation/Reference:

  *

  HTTP/1.1 keeps all requests and responses in plain text format.

  *

  HTTP/2 uses the binary framing layer to encapsulate all messages in binary format, while still maintaining HTTP semantics, such as verbs, methods, and headers. It came into use in 2015, and offers several methods to decrease latency, especially when dealing with mobile platforms and server-intensive graphics and videos

  *

  Currently, Mule application can have API policies only for Mule application that accepts requests over HTTP/1x

• Question 165:

  What is true about automating interactions with Anypoint Platform using tools such as Anypoint Platform REST API's, Anypoint CLI or the Mule Maven plugin?

  A. By default, the Anypoint CLI and Mule Maven plugin are not included in the Mule runtime
  B. Access to Anypoint Platform API;s and Anypoint CLI can be controlled separately thruough the roles and permissions in Anypoint platform, so that specific users can get access to Anypoint CLI while others get access to the platform API's
  C. Anypoint Platform API's can only automate interactions with CloudHub while the Mule maven plugin is required for deployment to customer hosted Mule runtimes
  D. API policies can be applied to the Anypoint platform API's so that only certain LOS's has access to specific functions
  A. By default, the Anypoint CLI and Mule Maven plugin are not included in the Mule runtime

  ---

  Explanation/Reference:

  Correct answer is By default, the Anypoint CLI and Mule Maven plugin are not included in the Mule runtime Maven is not part of runtime though it is part of studio. You do not need it to deploy in order to deploy your app. Same is the case with

  CLI.

• Question 166:

  What requirement prevents using Anypoint MQ as the messaging broker for a Mule application?

  A. When the payload sent through the message broker must use XML format
  B. When the payload sent through the message broker must be encrypted
  C. When the messaging broker must support point-to-point messaging
  D. When the messaging broker must be deployed on-premises
  D. When the messaging broker must be deployed on-premises

  ---

  Explanation/Reference:

  Anypoint MQ is a cloud-based messaging service provided by MuleSoft, and it cannot be deployed on-premises. If there is a requirement for the messaging broker to be deployed on-premises, Anypoint MQ would not be suitable. Other considerations such as payload format (XML), encryption, and point-to-point messaging are supported by Anypoint MQ, but the deployment environment requirement is a critical constraint. References: MuleSoft Anypoint MQ Documentation Cloud vs. On-Premises Messaging Solutions

• Question 167:

  Refer to the exhibit.

  A Mule application is being designed to expose a SOAP web service to its clients.

  What language is typically used inside the web service's interface definition to define the data structures that the web service Is expected to exchange with its clients?

  

  A. WSDL
  B. XSD
  C. JSON Schema
  D. RAMI
  B. XSD

  ---

  Explanation/Reference:

  XSD In this approach to developing a web service, you begin with an XML schema (XSD file) that defines XML data structures to be used as parameters and return types in the web service operations. Reference: https://www.w3schools.com/xml/schema_intro.asp

• Question 168:

  An organization is building out a test suite for their application using MUnit.

  The Integration Architect has recommended using Test Recorder in Anypoint Studio to record the processing flows and then configure unit tests based on the captured events.

  What Is a core consideration that must be kept In mind while using Test Recorder?

  A. The Recorder supports loops where the structure of the data being tested changes inside the Iteration
  B. Mocking values resulting from parallel processes are possible and will not affect theexecution of the processors that follow in the test
  C. The Recorder supports mocking a message before or inside a Foreach processor
  D. Tests for flows cannot be created if Mule errors are raised Inside the flows, even if the errors are handled by On-Error Continue error handlers
  D. Tests for flows cannot be created if Mule errors are raised Inside the flows, even if the errors are handled by On-Error Continue error handlers

  ---

  Explanation/Reference:

  MUnit and Test Recorder:

  Core Consideration:

  Error Handling in MUnit:

  References:

  MuleSoft Documentation on MUnit: MUnit Documentation

  MuleSoft Blog on MUnit Test Recorder: MUnit Test Recorder

• Question 169:

  A leading e-commerce giant will use Mulesoft API's on runtime fabric (RTF) to process customer orders. Some customer's sensitive information such as credit card information is also there as a part of a API payload.

  What approach minimizes the risk of matching sensitive data to the original and can convert back to the original value whenever and wherever required?

  A. Apply masking to hide the sensitive information and then use API
  B. manager to detokenize the masking format to return the original value
  C. create a tokenization format and apply a tokenization policy to the API Gateway
  D. Used both masking and tokenization
  E. Apply a field level encryption policy in the API Gateway
  C. create a tokenization format and apply a tokenization policy to the API Gateway

  ---

  Explanation/Reference:

  To minimize the risk of exposing sensitive data such as credit card information while still allowing it to be converted back to its original value when necessary, tokenization is the most effective approach. Tokenization replaces sensitive data

  with a non-sensitive equivalent, called a token, which has no exploitable value. This method ensures that the original sensitive data is stored securely and only accessible through a secure tokenization system. In this scenario, applying a

  tokenization policy at the API Gateway ensures that sensitive information is replaced with tokens before the data leaves the trusted boundary. This minimizes the risk of matching sensitive data to the original. When the original data is needed,

  the tokenization system can detokenize the token back to its original value securely.

  References:

  MuleSoft Documentation on Tokenization

• Question 170:

  A company is planning to extend its Mule APIs to the Europe region. Currently all new applications are deployed to Cloudhub in the US region following this naming convention {API name}-{environment}. for example, Orders-SAPI-dev, Orders-SAPI-prod etc.

  Considering there is no network restriction to block communications between API's, what strategy should be implemented in order to apply the same new API's running in the EU region of CloudHub as well to minimize latency between API's and target users and systems in Europe?

  A. Set region property to Europe (eu-de) in API manager for all the mule application No need to change the naming convention
  B. Set region property to Europe (eu-de) in API manager for all the mule application Change the naming convention to {API name}-{environment}-{region} and communicate this change to the consuming applications and users
  C. Set region property to Europe (eu-de) in runtime manager for all the mule application No need to change the naming convention
  D. Set region property to Europe (eu-de) in runtime manager for all the mule application Change the naming convention to {API name}-{environment}-{region} and communicate this change to the consuming applications and users
  D. Set region property to Europe (eu-de) in runtime manager for all the mule application Change the naming convention to {API name}-{environment}-{region} and communicate this change to the consuming applications and users

  ---

  Explanation/Reference:

  To extend Mule APIs to the Europe region and ensure minimal latency between APIs and target users and systems in Europe, it is important to set the region property correctly and update the naming convention. Here's the detailed approach:

  Setting the Region Property:

  Updating Naming Convention:

  Communicating the Change:

  Benefits:

  References:

  MuleSoft Documentation on Deploying to CloudHub

  MuleSoft Documentation on Managing Applications in Runtime Manager