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

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

• Question 151:

  An organization will deploy Mule applications to Cloudhub, Business requirements mandate that all application logs be stored ONLY in an external splunk consolidated logging service and NOT in Cloudhub.

  In order to most easily store Mule application logs ONLY in Splunk, how must Mule application logging be configured in Runtime Manager, and where should the log4j2 splunk appender be defined?

  A. Keep the default logging configuration in RuntimeManager Define the splunk appender in ONE global log4j.xml file that is uploaded once to Runtime Manager to support at Mule application deployments.
  B. Disable Cloudhub logging in Runtime Manager Define the splunk appender in EACH Mule application's log4j2.xml file
  C. Disable Cloudhub logging in Runtime Manager Define the splunk appender in ONE global log4j.xml file that is uploaded once to Runtime Manger to support at Mule application deployments.
  D. Keep the default logging configuration in Runtime Manager Define the Splunk appender in EACH Mule application log4j2.xml file
  B. Disable Cloudhub logging in Runtime Manager Define the splunk appender in EACH Mule application's log4j2.xml file

  ---

  Explanation/Reference:

  By default, CloudHub replaces a Mule application's log4j2.xml file with a CloudHub log4j2.xml file. In CloudHub, you can disable the CloudHub provided Mule application log4j2 file. This allows integrating Mule application logs with custom or third-party log management systems

• Question 152:

  How are the API implementation , API client, and API consumer combined to invoke and process an API ?

  A. The API consumer creates an API implementation , which receives API invocations from an API such that they are processed for an API client
  B. The API consumer creates an API client which sends API invocations to an API such that they are processed by an API implementation
  C. An API client creates an API consumer, which receives API invocation from an API such that they are processed for an API implementation
  D. The API client creates an API consumer which sends API invocations to an API such that they are processed by API implementation
  C. An API client creates an API consumer, which receives API invocation from an API such that they are processed for an API implementation

  ---

  Explanation/Reference:

  The API consumer creates an API client which sends API invocations to an API such that they are processed by an API implementation This is based on below definitions API client ?An application component that accesses a service by invoking an API of that service -by definition of the term API over HTTP API consumer A business role, which is often assigned to an individual that develops API clients, i.e., performs the activities necessary for enabling an API client to invoke APIs API implementation An application component ?that implements the functionality

• Question 153:

  An organization has chosen Mulesoft for their integration and API platform.

  According to the Mulesoft catalyst framework, what would an integration architect do to create achievement goals as part of their business outcomes?

  A. Measure the impact of the centre for enablement
  B. build and publish foundational assets
  C. agree upon KPI's and help develop and overall success plan
  D. evangelize API's
  C. agree upon KPI's and help develop and overall success plan

  ---

  Explanation/Reference:

  According to the MuleSoft Catalyst framework, an Integration Architect plays a crucial role in defining and achieving business outcomes. One of their key responsibilities is to agree upon Key Performance Indicators (KPIs) and help develop an

  overall success plan. This involves working with stakeholders to identify measurable goals and ensure that the integration initiatives align with the organization's strategic objectives. KPIs are critical for tracking progress, measuring success,

  and making data-driven decisions. By agreeing on KPIs and developing a success plan, the Integration Architect ensures that the organization can objectively measure the impact of its integration efforts and adjust strategies as needed to

  achieve desired business outcomes.

  References:

  MuleSoft Catalyst Knowledge Hub

• Question 154:

  An Integration Mule application is being designed to synchronize customer data between two systems. One system is an IBM Mainframe and the other system is a Salesforce Marketing Cloud (CRM) instance. Both systems have been deployed in their typical configurations, and are to be invoked using the native protocols provided by Salesforce and IBM.

  What interface technologies are the most straightforward and appropriate to use in this Mute application to interact with these systems, assuming that Anypoint Connectors exist that implement these interface technologies?

  A. IBM: DB access CRM: gRPC
  B. IBM: REST CRM:REST
  C. IBM: Active MQ CRM: REST
  D. IBM: CICS CRM: SOAP
  D. IBM: CICS CRM: SOAP

  ---

  Explanation/Reference:

  Correct answer is IBM: CICS CRM: SOAP

  *

  Within Anypoint Exchange, MuleSoft offers the IBM CICS connector. Anypoint Connector for IBM CICS Transaction Gateway (IBM CTG Connector) provides integration with back-end CICS apps using the CICS Transaction Gateway.

  *

  Anypoint Connector for Salesforce Marketing Cloud (Marketing Cloud Connector) enables you to connect to the Marketing Cloud API web services (now known as the Marketing Cloud API), which is also known as the Salesforce Marketing Cloud. This connector exposes convenient operations via SOAP for exploiting the capabilities of Salesforce Marketing Cloud.

• Question 155:

  According to MuleSoft, what is a major distinguishing characteristic of an application network in relation to the integration of systems, data, and devices?

  A. It uses a well-organized monolithic approach with standards
  B. It is built for change and self-service
  C. It leverages well-accepted internet standards like HTTP and JSON
  D. It uses CI/CD automation for real-time project delivery
  B. It is built for change and self-service

  ---

  Explanation/Reference:

  A major distinguishing characteristic of an application network, according to MuleSoft, is that it is built for change and self-service. An application network connects applications, data, and devices with APIs, enabling self-service access and reuse of assets. This architecture allows organizations to rapidly adapt to changing business needs, fosters innovation, and reduces time to market by empowering different teams to access and integrate systems independently without waiting for centralized IT. References: Application Networks: The Future of Integration MuleSoft's Approach to Building Application Networks

• Question 156:

  A developer needs to discover which API specifications have been created within the organization before starting a new project.

  Which Anypoint Platform component can the developer use to find and try out the currently released API specifications?

  A. Anypoint Exchange
  B. Runtime Manager
  C. API Manager
  D. Object Store
  A. Anypoint Exchange

  ---

  Explanation/Reference:

  To discover which API specifications have been created within the organization before starting a new project, a developer can use Anypoint Exchange. Anypoint Exchange is a centralized repository on the Anypoint Platform where developers can find, share, and collaborate on API specifications, connectors, templates, and other reusable assets. In Anypoint Exchange, developers can browse the currently released API specifications, try them out using the built-in testing tools, and access documentation and other resources. This facilitates the reuse of existing APIs and ensures that the new project aligns with the organization's API strategy. References: MuleSoft Documentation on Anypoint Exchange Best Practices for API Reuse and Discovery

• Question 157:

  An organization has various integrations implemented as Mule applications. Some of these Mule applications are deployed to custom hosted Mule runtimes (on-premises) while others execute in the MuleSoft-hosted runtime plane (CloudHub). To perform the Integra functionality, these Mule applications connect to various backend systems, with multiple applications typically needing to access the backend systems.

  How can the organization most effectively avoid creating duplicates in each Mule application of the credentials required to access the backend systems?

  A. Create a Mule domain project that maintains the credentials as Mule domain-shared resources Deploy the Mule applications to the Mule domain, so the credentials are available to the Mule applications
  B. Store the credentials in properties files in a shared folder within the organization's data center Have the Mule applications load properties files from this shared location at startup
  C. Segregate the credentials for each backend system into environment-specific properties files Package these properties files in each Mule application, from where they are loaded at startup
  D. Configure or create a credentials service that returns the credentials for each backend system, and that is accessible from customer-hosted and MuleSoft-hosted Mule runtimes Have the Mule applications toad the properties at startup by invoking that credentials service
  D. Configure or create a credentials service that returns the credentials for each backend system, and that is accessible from customer-hosted and MuleSoft-hosted Mule runtimes Have the Mule applications toad the properties at startup by invoking that credentials service

  ---

  Explanation/Reference:

  * "Create a Mule domain project that maintains the credentials as Mule domain-shared resources" is wrong as domain project is not supported in Cloudhub * We should Avoid Creating duplicates in each Mule application but below two options cause duplication of credentials -Store the credentials in properties files in a shared folder within the organization's data center. Have the Mule applications load properties files from this shared location at startup -Segregate the credentials for each backend system into environment-specific properties files. Package these properties files in each Mule application, from where they are loaded at startup So these are also wrong choices * Credentials service is the best approach in this scenario. Mule domain projects are not supported on CloudHub. Also its is not recommended to have multiple copies of configuration values as this makes difficult to maintain Use the Mule Credentials Vault to encrypt data in a .properties file. (In the context of this document, we refer to the .properties file simply as the properties file.) The properties file in Mule stores data as key-value pairs which may contain information such as usernames, first and last names, and credit card numbers. A Mule application may access this data as it processes messages, for example, to acquire login credentials for an external Web service. However, though this sensitive, private data must be stored in a properties file for Mule to access, it must also be protected against unauthorized ?and potentially malicious ?use by anyone with access to the Mule application

• Question 158:

  An organization is choosing between API-led connectivity and other integration approaches.

  According to MuleSoft, which business benefits is associated with an API-led connectivity approach using Anypoint Platform?

  A. improved security through adoption of monolithic architectures
  B. Increased developer productivity through sell-service of API assets
  C. Greater project predictability through tight coupling of systems
  D. Higher outcome repeatability through centralized development
  B. Increased developer productivity through sell-service of API assets

  ---

  Explanation/Reference:

  According to MuleSoft, a significant business benefit associated with an API-led connectivity approach using Anypoint Platform is increased developer productivity through self-service of API assets. API-led connectivity promotes the creation of reusable APIs that can be easily discovered and consumed by developers across the organization. This self-service model reduces dependencies, accelerates development, and fosters innovation by enabling teams to quickly build and integrate applications using existing APIs without waiting for central IT to provide access. References: API-led Connectivity: The Key to Unlocking IT Agility Benefits of API-led Connectivity

• Question 159:

  In which order are the API Client, API Implementation, and API interface components called in a typical REST request?

  A. API Client > API implementation > API Interface
  B. API interface > API Client > API Implementation
  C. API Client > API Interface > API implementation
  D. API Implementation > API Interface > API Client
  C. API Client > API Interface > API implementation

  ---

  Explanation/Reference:

  In a typical REST request, the order of interaction is:

  API Client: The client initiates the request to access data or functionality exposed by the API.

  API Interface: This represents the contract or the definition of the API, often specified in OpenAPI or RAML. It defines the endpoints, request/response formats, and other API details. API Implementation: This is the actual backend logic that

  processes the request and returns the response. It interacts with databases, other services, or performs business logic to fulfill the request.

  References:

  Understanding REST APIs

  API Design and Implementation

• Question 160:

  Mule applications need to be deployed to CloudHub so they can access on-premises database systems. These systems store sensitive and hence tightly protected data, so are not accessible over the internet.

  What network architecture supports this requirement?

  A. An Anypoint VPC connected to the on-premises network using an IPsec tunnel or AWS DirectConnect, plus matching firewall rules in the VPC and on-premises network
  B. Static IP addresses for the Mule applications deployed to the CloudHub Shared Worker Cloud, plus matching firewall rules and IP whitelisting in the on-premises network
  C. An Anypoint VPC with one Dedicated Load Balancer fronting each on-premises database system, plus matching IP whitelisting in the load balancer and firewall rules in the VPC and on-premises network
  D. Relocation of the database systems to a DMZ in the on-premises network, with Mule applications deployed to the CloudHub Shared Worker Cloud connecting only to the DMZ
  A. An Anypoint VPC connected to the on-premises network using an IPsec tunnel or AWS DirectConnect, plus matching firewall rules in the VPC and on-premises network

  ---

  Explanation/Reference:

  *

  "Relocation of the database systems to a DMZ in the on-premises network, with Mule applications deployed to the CloudHub Shared Worker Cloud connecting only to the DMZ" is not a feasible option

  *

  "Static IP addresses for the Mule applications deployed to the CloudHub Shared Worker Cloud, plus matching firewall rules and IP whitelisting in the on-premises network" -It is risk for sensitive data. -Even if you whitelist the database IP on your app, your app wont be able to connect to the database so this is also not a feasible option

  *

  "An Anypoint VPC with one Dedicated Load Balancer fronting each on-premises database system, plus matching IP whitelisting in the load balancer and firewall rules in the VPC and on-premises network" Adding one VPC with a DLB for each backend system also makes no sense, is way too much work. Why would you add a LB for one system.

  *

  Correct answer: "An Anypoint VPC connected to the on-premises network using an IPsec tunnel or AWS DirectConnect, plus matching firewall rules in the VPC and on-premises network" IPsec Tunnel You can use an IPsec tunnel with network-to-network configuration to connect your on-premises data centers to your Anypoint VPC. An IPsec VPN tunnel is generally the recommended solution for VPC to on-premises connectivity, as it provides a standardized, secure way to connect. This method also integrates well with existing IT infrastructure such as routers and appliances. Reference: https://docs.mulesoft.com/runtime-manager/vpc-connectivity-methods-concept