Practice Free MuleSoft Integration Architect I Exam Online Questions
As an enterprise architect, what are the two reasons for which you would use a canonical data model in the new integration project using MuleSoft Anypoint platform (choose two answers)
- A . To have consistent data structure aligned in processes
- B . To isolate areas within a bounded context
- C . To incorporate industry standard data formats
- D . There are multiple canonical definitions of each data type
- E . Because the model isolates the back and systems and support mule applications from change
An organization has an HTTPS-enabled Mule application named Orders API that receives requests from another Mule application named Process Orders.
The communication between these two Mule applications must be secured by TLS mutual authentication (two-way TLS).
At a minimum, what must be stored in each truststore and keystore of these two Mule applications to properly support two-way TLS between the two Mule applications while properly protecting each Mule application’s keys?
- A . Orders API truststore: The Orders API public key
Process Orders keystore: The Process Orders private key and public key - B . Orders API truststore: The Orders API private key and public key
Process Orders keystore: The Process Orders private key public key - C . Orders API truststore: The Process Orders public key
Orders API keystore: The Orders API private key and public key
Process Orders truststore: The Orders API public key
Process Orders keystore: The Process Orders private key and public key - D . Orders API truststore: The Process Orders public key
Orders API keystore: The Orders API private key
Process Orders truststore: The Orders API public key
Process Orders keystore: The Process Orders private key
C
Explanation:
Reference: https://www.caeliusconsulting.com/blogs/one-way-and-two-way-tls-and-their-implementation-in-mulesoft/
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
What are two reasons why a typical MuleSoft customer favors a MuleSoft-hosted Anypoint Platform runtime plane over a customer-hosted runtime for its Mule application deployments? (Choose two.)
- A . Reduced application latency
- B . Increased application isolation
- C . Reduced time-to-market for the first application
- D . Increased application throughput
- E . Reduced IT operations effort
Refer to the exhibit.
An organization deploys multiple Mule applications to the same customer -hosted Mule runtime. Many of these Mule applications must expose an HTTPS endpoint on the same port using a server-side certificate that rotates often.
What is the most effective way to package the HTTP Listener and package or store the server-side certificate when deploying these Mule applications, so the disruption caused by certificate rotation is minimized?
- A . Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint Package the server-side certificate in ALL Mule
APPLICATIONS that need to expose an HTTPS endpoint - B . Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint. Store the server-side certificate in a shared filesystem location in the Mule runtime’s classpath, OUTSIDE the Mule DOMAIN or any Mule APPLICATION
- C . Package an HTTPS Listener configuration In all Mule APPLICATIONS that need to expose an HTTPS endpoint Package the server-side certificate in a NEW Mule DOMAIN project
- D . Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing It from all Mule applications that need to expose an HTTPS endpoint. Package the server-side certificate in the SAME Mule DOMAIN project Go to Set
B
Explanation:
In this scenario, both A & C will work, but A is better as it does not require repackage to the domain project at all.
Correct answer is Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint. Store the server-side certificate in a shared filesystem location in the Mule runtime’s classpath, OUTSIDE the Mule DOMAIN or any Mule APPLICATION.
What is Mule Domain Project?
* A Mule Domain Project is implemented to configure the resources that are shared among different projects. These resources can be used by all the projects associated with this domain. Mule applications can be associated with only one domain, but a domain can be associated with multiple projects. Shared resources allow multiple development teams to work in parallel using the same set of reusable connectors. Defining these connectors as shared resources at the domain level allows the team to: – Expose multiple services within the domain through the same port. – Share the connection to persistent storage. – Share services between apps through a well-defined interface. – Ensure consistency between apps upon any changes because the configuration is only set in one place.
* Use domains Project to share the same host and port among multiple projects. You can declare the http connector within a domain project and associate the domain project with other projects. Doing this also allows to control thread settings, keystore configurations, time outs for all the requests made within multiple applications. You may think that one can also achieve this by duplicating the http connector configuration across all the applications. But, doing this may pose a nightmare if you have to make a change and redeploy all the applications.
* If you use connector configuration in the domain and let all the applications use the new domain instead of a default domain, you will maintain only one copy of the http connector configuration. Any changes will require only the domain to the redeployed instead of all the applications.
You can start using domains in only three steps:
1) Create a Mule Domain project
2) Create the global connector configurations which needs to be shared across the applications inside the Mule Domain project
3) Modify the value of domain in mule-deploy.properties file of the applications
Use a certificate defined in already deployed Mule domain Configure the certificate in the domain so that the API proxy HTTPS Listener references it, and then deploy the secure API proxy to the target Runtime Fabric, or on-premises target. (CloudHub is not supported with this approach because it does not support Mule domains.)
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
What is an advantage of using OAuth 2.0 client credentials and access tokens over only API keys for API authentication?
- A . If the access token is compromised, the client credentials do not to be reissued.
- B . If the access token is compromised, I can be exchanged for an API key.
- C . If the client ID is compromised, it can be exchanged for an API key
- D . If the client secret is compromised, the client credentials do not have to be reissued.
A
Explanation:
The advantage of using OAuth 2.0 client credentials and access tokens over only API keys for API authentication is that if the access token is compromised, the client credentials do not have to be reissued.
OAuth 2.0 is a secure protocol for authenticating clients and authorizing them to access protected resources. It works by having the client authenticate with the authorization server and receive an access token, which is then used to authenticate requests to the API. If the access token is compromised, it can be revoked and replaced without needing to reissue the client credentials.
Reference: MuleSoft Certified Integration Architect – Level 1 Official Text Book and Resources:
Chapter 7: Security
Section 7.2: OAuth 2.0
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
Explanation:
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.
So Correct answer is: Asynchronous logging can improve Mule event processing throughput while also reducing the processing time for each Mule event
A Mule application is built to support a local transaction for a series of operations on a single database. The mule application has a Scatter-Gather scope that participates in the local transaction.
What is the behavior of the Scatter-Gather when running within this local transaction?
- A . Execution of all routes within Scatter-Gather occurs in parallel Any error that occurs inside Scatter-Gather will result in a roll back of all the database operations
- B . Execution of all routes within Scatter-Gather occurs sequentially Any error that occurs inside Scatter-Gather will be handled by error handler and will not result in roll back
- C . Execution of all routes within Scatter-Gather occurs sequentially Any error that occurs inside Scatter-Gather will result in a roll back of all the database operations
- D . Execution of all routes within Scatter-Gather occurs in parallel Any error that occurs inside Scatter-Gather will be handled by error handler and will not result in roll back
What is an advantage that Anypoint Platform offers by providing universal API management and Integration-Platform-as-a-Service (iPaaS) capabilities in a unified platform?
- A . Ability to use a single iPaaS to manage and integrate all API gateways
- B . Ability to use a single connector to manage and integrate all APis
- C . Ability to use a single control plane for both full-lifecycle AP] management and integration
- D . Ability to use a single iPaaS to manage all API developer portals
C
Explanation:
Anypoint Platform offers universal API management and Integration-Platform-as-a-Service (iPaaS) capabilities in a unified platform, meaning that it provides a single control plane to manage both full-lifecycle API management and integration. This allows organizations to easily manage their APIs and integrations, as well as deploy APIs and integrations quickly and efficiently. According to the MuleSoft Certified Integration Architect – Level 1 Course Book, “Anypoint Platform provides a unified platform for managing, deploying, and monitoring both API and integration solutions, allowing organizations to quickly and easily build and manage their APIs and integrations.”