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

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

• Question 141:

  What Is a recommended practice when designing an integration Mule 4 application that reads a large XML payload as a stream?

  A. The payload should be dealt with as a repeatable XML stream, which must only be traversed (iterated-over) once and CANNOT be accessed randomly from DataWeave expressions and scripts
  B. The payload should be dealt with as an XML stream, without converting it to a single Java object (POJO)
  C. The payload size should NOT exceed the maximum available heap memory of the Mute runtime on which the Mule application executes
  D. The payload must be cached using a Cache scope If It Is to be sent to multiple backend systems
  C. The payload size should NOT exceed the maximum available heap memory of the Mute runtime on which the Mule application executes

  ---

  Explanation/Reference:

  If the size of the stream exceeds the maximum, a STREAM_MAXIMUM_SIZE_EXCEEDED error is raised.

• Question 142:

  An organization currently uses a multi-node Mule runtime deployment model within their datacenter, so each Mule runtime hosts several Mule applications. The organization is planning to transition to a deployment model based on Docker containers in a Kubernetes cluster. The organization has already created a standard Docker image containing a Mule runtime and all required dependencies (including a JVM), but excluding the Mule application itself.

  What is an expected outcome of this transition to container-based Mule application deployments?

  A. Required redesign of Mule applications to follow microservice architecture principles
  B. Required migration to the Docker and Kubernetes-based Anypoint Platform -Private Cloud Edition
  C. Required change to the URL endpoints used by clients to send requests to the Mule applications
  D. Guaranteed consistency of execution environments across all deployments of a Mule application
  A. Required redesign of Mule applications to follow microservice architecture principles

  ---

  Explanation/Reference:

  *

  Organization can continue using existing load balancer even if backend application changes are there. So option A is ruled out.

  *

  As Mule runtime is within their datacenter, this model is RTF and not PCE. So option C is ruled out. Mule runtime deployment model within their datacenter, so each Mule runtime hosts several Mule applications --This mean PCE or Hybird not RTF -Also mentioned in Question is that -Mule runtime is hosting several Mule Application, so that also rules out RTF and as for hosting multiple Application it will have Domain project which need redesign to make it microservice architecture ---------------------------------------------------------------------------------------------------------------

  Correct Answer: Required redesign of Mule applications to follow microservice architecture principles

• Question 143:

  What is a key difference between synchronous and asynchronous logging from Mule applications?

  A. Synchronous logging writes log messages in a single logging thread but does not block the Mule event being processed by the next event processor
  B. Asynchronous logging can improve Mule event processing throughput while also reducing the processing time for each Mule event
  C. Asynchronous logging produces more reliable audit trails with more accurate timestamps
  D. Synchronous logging within an ongoing transaction writes log messages in the same thread that processes the current Mule event
  B. Asynchronous logging can improve Mule event processing throughput while also reducing the processing time for each Mule event

  ---

  Explanation/Reference:

  Types of logging:

  A) Synchronous: The execution of thread that is processing messages is interrupted to wait for the log message to be fully handled before it can continue. The execution of the thread that is processing your message is interrupted to wait for

  the log message to be fully output before it can continue

  Performance degrades because of synchronous logging

  Used when the log is used as an audit trail or when logging ERROR/CRITICAL messages If the logger fails to write to disk, the exception would raise on the same thread that's currently processing the Mule event. If logging is critical for you,

  then you can rollback the transaction.

  

  B) Asynchronous:

  The logging operation occurs in a separate thread, so the actual processing of your message won't be delayed to wait for the logging to complete Substantial improvement in throughput and latency of message processing Mule runtime

  engine (Mule) 4 uses Log4j 2 asynchronous logging by default The disadvantage of asynchronous logging is error handling. If the logger fails to write to disk, the thread doing the processing won't be aware of any issues writing to the disk, so

  you won't be able to rollback anything. Because the actual writing of the log gets differed, there's a chance that log messages might never make it to disk and get lost, if Mule were to crash before the buffers are flushed.

• Question 144:

  In preparation for a digital transformation initiative, an organization is reviewing related IT integration projects that failed for various for reason.

  According to MuleSoft's surveys of global IT leaders, what is a common cause of IT project failure that this organization may likely discover in its assessment?

  A. Following an Agile delivery methodology
  B. Reliance on an Integration-Platform-as-a-Service (iPaaS)
  C. Spending too much time on enablement
  D. Lack of alignment around business outcomes
  D. Lack of alignment around business outcomes

  ---

  Explanation/Reference:

  According to MuleSoft's surveys of global IT leaders, a common cause of IT project failure is a lack of alignment around business outcomes. When IT projects do not have clear business objectives or fail to align with the strategic goals of the organization, they are more likely to face challenges and fail to deliver value. Ensuring that IT initiatives are closely tied to business goals and have stakeholder buy-in is crucial for their success. References: Why IT Projects Fail Aligning IT and Business Strategies

• Question 145:

  A travel company wants to publish a well-defined booking service API to be shared with its business partners. These business partners have agreed to ONLY consume SOAP services and they want to get the service contracts in an easily consumable way before they start any development. The travel company will publish the initial design documents to Anypoint Exchange, then share those documents with the business partners.

  When using an API-led approach, what is the first design document the travel company should deliver to its business partners?

  A. Create a WSDL specification using any XML editor
  B. Create a RAML API specification using any text editor
  C. Create an OAS API specification in Design Center
  D. Create a SOAP API specification in Design Center
  A. Create a WSDL specification using any XML editor

  ---

  Explanation/Reference:

  SOAP API specifications are provided as WSDL. Design center doesn't provide the functionality to create WSDL file. Hence WSDL needs to be created using XML editor

• Question 146:

  An organization is designing an integration Mule application to process orders by submitting them to a back-end system for offline processing. Each order will be received by the Mule application through an HTTPS POST and must be acknowledged immediately. Once acknowledged, the order will be submitted to a back-end system. Orders that cannot be successfully submitted due to rejections from the back-end system will need to be processed manually (outside the back-end system).

  The Mule application will be deployed to a customer-hosted runtime and is able to use an existing ActiveMQ broker if needed. The ActiveMQ broker is located inside the organization's firewall. The back-end system has a track record of unreliability due to both minor network connectivity issues and longer outages.

  What idiomatic (used for their intended purposes) combination of Mule application components and ActiveMQ queues are required to ensure automatic submission of orders to the back-end system while supporting but minimizing manual order processing?

  A. An Until Successful scope to call the back-end system One or more ActiveMQ long-retry queues One or more ActiveMQ dead-letter queues for manual processing
  B. One or more On Error scopes to assist calling the back-end system An Until Successful scope containing VM components for long retries A persistent dead-letter VM queue configured in CloudHub
  C. One or more On Error scopes to assist calling the back-end system One or more ActiveMQ long-retry queues A persistent dead-letter object store configured in the CloudHub Object Store service
  D. A Batch Job scope to call the back-end system An Until Successful scope containing Object Store components for long retries A dead-letter object store configured in the Mule application
  A. An Until Successful scope to call the back-end system One or more ActiveMQ long-retry queues One or more ActiveMQ dead-letter queues for manual processing

• Question 147:

  A Mule application currently writes to two separate SQL Server database instances across the internet using a single XA transaction. It is 58. proposed to split this one transaction into two separate non-XA transactions with no other changes to the Mule application.

  What non-functional requirement can be expected to be negatively affected when implementing this change?

  A. Throughput
  B. Consistency
  C. Response time
  D. Availability
  B. Consistency

  ---

  Explanation/Reference:

  Correct answer is Consistency as XA transactions are implemented to achieve this. XA transactions are added in the implementation to achieve goal of ACID properties. In the context of transaction processing, the acronym ACID refers to the four key properties of a transaction: atomicity, consistency, isolation, and durability. Atomicity : All changes to data are performed as if they are a single operation. That is, all the changes are performed, or none of them are. For example, in an application that transfers funds from one account to another, the atomicity property ensures that, if a debit is made successfully from one account, the corresponding credit is made to the other account. Consistency : Data is in a consistent state when a transaction starts and when it ends.For example, in an application that transfers funds from one account to another, the consistency property ensures that the total value of funds in both the accounts is the same at the start and end of each transaction. Isolation : The intermediate state of a transaction is invisible to other transactions. As a result, transactions that run concurrently appear to be serialized. For example, in an application that transfers funds from one account to another, the isolation property ensures that another transaction sees the transferred funds in one account or the other, but not in both, nor in neither. Durability : After a transaction successfully completes, changes to data persist and are not undone, even in the event of a system failure. For example, in an application that transfers funds from one account to another, the durability property ensures that the changes made to each account will not be reversed. MuleSoft reference: https://docs.mulesoft.com/mule-runtime/4.3/xa-transactions

• Question 148:

  In Anypoint Platform, a company wants to configure multiple identity providers(Idps) for various lines of business (LOBs) Multiple business groups and environments have been defined for the these LOBs. What Anypoint Platform feature can use multiple Idps access the company's business groups and environment?

  A. User management
  B. Roles and permissions
  C. Dedicated load balancers
  D. Client Management
  D. Client Management

  ---

  Explanation/Reference:

  Correct answer is Client Management

  *

  Anypoint Platform acts as a client provider by default, but you can also configure external client providers to authorize client applications.

  *

  As an API owner, you can apply an OAuth 2.0 policy to authorize client applications that try to access your API. You need an OAuth 2.0 provider to use an OAuth 2.0 policy.

  *

  You can configure more than one client provider and associate the client providers with different environments. If you configure multiple client providers after you have already created environments, you can associate the new client

  providers with the environment.

  *

  You should review the existing client configuration before reassigning client providers to avoid any downtime with existing assets or APIs.

  *

  When you delete a client provider from your master organization, the client provider is no longer available in environments that used it.

  *

  Also, assets or APIs that used the client provider can no longer authorize users who want to access them.

  MuleSoft Reference: https://docs.mulesoft.com/access-management/managing-api-clients https://www.folkstalk.com/2019/11/mulesoft-integration-and-platform.html

• Question 149:

  According to MuleSoft, which deployment characteristic applies to a microservices application architecture?

  A. Services exist as independent deployment artifacts and can be scaled -independently of other services
  B. All services of an application can be deployed together as single Java WAR file
  C. A deployment to enhance one capability requires a redeployment of all capabilities
  D. Core business capabilities are encapsulated in a single, deployable application
  A. Services exist as independent deployment artifacts and can be scaled -independently of other services

  ---

  Explanation/Reference:

  In a microservices application architecture, each service is designed to be an independent deployment artifact. This means that services can be deployed, updated, and scaled independently of one another. This characteristic allows for greater flexibility and agility in managing applications, as individual services can be scaled up or down based on demand without impacting other services. It also enhances fault isolation, as issues in one service do not necessarily affect the entire application. This is in contrast to monolithic architectures, where all components are packaged and deployed together, often resulting in a single point of failure and difficulties in scaling and updating specific parts of the application. References: MuleSoft Documentation on Microservices Architecture Principles of Microservices Design

• Question 150:

  An organization is designing Mule application which connects to a legacy backend. It has been reported that backend services are not highly available and experience downtime quite often. As an integration architect which of the below approach you would propose to achieve high reliability goals?

  A. Alerts can be configured in Mule runtime so that backend team can be communicated when services are down
  B. Until Successful scope can be implemented while calling backend API's
  C. On Error Continue scope to be used to call in case of error again
  D. Create a batch job with all requests being sent to backend using that job as per the availability of backend API's
  B. Until Successful scope can be implemented while calling backend API's

  ---

  Explanation/Reference:

  Correct answer is Untill Successful scope can be implemented while calling backend API's The Until Successful scope repeatedly triggers the scope's components (including flow References: ) until they all succeed or until a maximum number of retries is exceeded The scope provides option to control the max number of retries and the interval between retries The scope can execute any sequence of processors that may fail for whatever reason and may succeed upon retry