support@Free-Braindumps.com
Register Login
Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  1. Home
  2. Exams
  3. Salesforce
  4. MuleSoft-Integration-Architect-I

Salesforce MuleSoft-Integration-Architect-I Exam Actual Questions
Salesforce Certified MuleSoft Integration Architect I (Page 4 )

Updated On: 10-Aug-2026
Page 4 of 56
PDF with 273 Questions

An API has been unit tested and is ready for integration testing. The API is governed by a Client ID Enforcement policy in all environments.
What must the testing team do before they can start integration testing the API in the Staging environment?

  1. They must access the API portal and create an API notebook using the Client ID and Client Secret supplied by the API portal in the Staging environment
  2. They must request access to the API instance in the Staging environment and obtain a Client ID and Client Secret to be used for testing the API
  3. They must be assigned as an API version owner of the API in the Staging environment
  4. They must request access to the Staging environment and obtain the Client ID and Client Secret for that environment to be used for testing the API

Answer(s): B

Explanation:

* It's mentioned that the API is governed by a Client ID Enforcement policy in all environments.
* Client ID Enforcement policy allows only authorized applications to access the deployed API implementation.
* Each authorized application is configured with credentials: client_id and client_secret.
* At runtime, authorized applications provide the credentials with each request to the API implementation.
MuleSoft


Reference:

https://docs.mulesoft.com/api-manager/2.x/policy-mule3-client-id-based-

policies



What requires configuration of both a key store and a trust store for an HTTP Listener?

  1. Support for TLS mutual (two-way) authentication with HTTP clients
  2. Encryption of requests to both subdomains and API resource endpoints fhttPs://aDi.customer.com/ and https://customer.com/api)
  3. Encryption of both HTTP request and HTTP response bodies for all HTTP clients
  4. Encryption of both HTTP request header and HTTP request body for all HTTP clients

Answer(s): A

Explanation:

1 way SSL : The server presents its certificate to the client and the client adds it to its list of trusted certificate. And so, the client can talk to the server.
2-way SSL: The same principle but both ways. i.e. both the client and the server has to establish trust between themselves using a trusted certificate. In this way of a digital handshake, the server needs to present a certificate to authenticate itself to client and client has to present its certificate to server.
* TLS is a cryptographic protocol that provides communications security for your Mule app.
* TLS offers many different ways of exchanging keys for authentication, encrypting data, and guaranteeing message integrity Keystores and Truststores Truststore and keystore contents differ depending on whether they are used for clients or servers:
For servers: the truststore contains certificates of the trusted clients, the keystore contains the private and public key of the server. For clients: the truststore contains certificates of the trusted servers, the keystore contains the private and public key of the client. Adding both a keystore and a truststore to the configuration implements two-way TLS authentication also known as mutual authentication.
* in this case, correct answer is Support for TLS mutual (two-way) authentication with HTTP clients.



A retailer is designing a data exchange interface to be used by its suppliers. The interface must support secure communication over the public internet. The interface must also work with a wide variety of programming languages and IT systems used by suppliers.
What are suitable interface technologies for this data exchange that are secure, cross-platform, and internet friendly, assuming that Anypoint Connectors exist for these interface technologies?

  1. EDJFACT XML over SFTP JSON/REST over HTTPS
  2. SOAP over HTTPS HOP over TLS gRPC over HTTPS
  3. XML over ActiveMQ XML over SFTP XML/REST over HTTPS
  4. CSV over FTP YAML over TLS JSON over HTTPS

Answer(s): C

Explanation:

* As per definition of API by Mulesoft , it is Application Programming Interface using HTTP-based protocols. Non-HTTP-based programmatic interfaces are not APIs.
* HTTP-based programmatic interfaces are APIs even if they don't use REST or JSON. Hence implementation based on Java RMI, CORBA/IIOP, raw TCP/IP interfaces are not API's as they are not using HTTP.
* One more thing to note is FTP was not built to be secure. It is generally considered to be an insecure protocol because it relies on clear-text usernames and passwords for authentication and does not use encryption.
* Data sent via FTP is vulnerable to sniffing, spoofing, and brute force attacks, among other basic attack methods.
Considering the above points only correct option is
-XML over ActiveMQ
- XML over SFTP
- XML/REST over HTTPS



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?

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

Answer(s): A

Explanation:

* 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 ---------------------------------------------------------------------------------------------------------------

Answer(s): Required redesign of Mule applications to follow microservice architecture principles



A team would like to create a project skeleton that developers can use as a starting point when creating API Implementations with Anypoint Studio. This skeleton should help drive consistent use of best practices within the team.
What type of Anypoint Exchange artifact(s) should be added to Anypoint Exchange to publish the project skeleton?

  1. A custom asset with the default API implementation
  2. A RAML archetype and reusable trait definitions to be reused across API implementations
  3. An example of an API implementation following best practices
  4. a Mule application template with the key components and minimal integration logic

Answer(s): D

Explanation:

* Sharing Mule applications as templates is a great way to share your work with other people who are in your organization in Anypoint Platform.
When they need to build a similar application they can create the mule application using the template project from Anypoint studio.
* Anypoint Templates are designed to make it easier and faster to go from a blank canvas to a production application. They're bit for bit Mule applications requiring only Anypoint Studio to build and design, and are deployable both on-premises and in the cloud.
* Anypoint Templates are based on five common data Integration patterns and can be customized and extended to fit your integration needs. So even if your use case involves different endpoints or connectors than those included in the template, they still offer a great starting point. Some of the best practices while creating the template project: - Define the common error handler as part of template project, either using pom dependency or mule config file - Define common logger/audit framework as part of the template project - Define the env specific properties and secure properties file as per the requirement - Define global.xml for global configuration - Define the config file for connector configuration like Http,Salesforce,File,FTP etc - Create separate folders to create DWL,Properties,SSL certificates etc - Add the dependency and configure the pom.xml as per the business need - Configure the mule-artifact.json as per the business need



  PDF
Viewing page 4 of 56
Viewing questions 16 - 20 out of 273 questions


Post your Comments and Discuss Salesforce MuleSoft-Integration-Architect-I exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!