MuleSoft Certified Integration Architect – Level 1 Exam (MCIA-Level 1) - Mulesoft

deployed to the CloudHub Shared Worker Cloud connecting only to the DMZ" is not a feasible option<br />
<br />
* "Relocation of the database systems to a DMZ in the on-premises network, with Mule applications<br />
<br />
* "Static IP addresses for the Mule applications deployed to the CloudHub Shared Worker Cloud, plus<br />
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<br />
<br />
* "An Anypoint VPC with one Dedicated Load Balancer fronting each on-premises database system,<br />
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.<br />
<br />
* Correct answer: "An Anypoint VPC connected to the on-premises network using an IPsec tunnel or<br />
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.<br />
<br />
Reference: https://docs.mulesoft.com/runtime-manager/vpc-connectivity-methods-concept<br />
<br />
<img src="https://examsqa.com/storage/question-images/mulesoft-certified-integration-architect-level-1-exam-mcia-level-1_page_2_Im2.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" />

In this scenario, both A & C will work, but A is better as it does not require repackage to the domain<br />
<br />
Correct answer is Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it project at all.<br />
from all Mule applications that need to expose an HTTPS endpoint. Store the server-side certificate<br />
in a shared filesystem location in the Mule runtime’s classpath, OUTSIDE the Mule DOMAIN or any Mule APPLICATION. What is Mule Domain Project?<br />
<br />
* A Mule Domain Project is implemented to configure the resources that are shared among different<br />
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.<br />
<br />
* Use domains Project to share the same host and port among multiple projects. You can declare the<br />
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.<br />
<br />
* If you use connector configuration in the domain and let all the applications use the new domain<br />
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.<br />
<br />
1) Create a Mule Domain project<br />
<br />
2) Create the global connector configurations which needs to be shared across the applications inside<br />
<br />
You can start using domains in only three steps: the Mule Domain project<br />
<br />
3) Modify the value of domain in mule-deploy.properties file of the applications<br />
<br />
<img src="https://examsqa.com/storage/question-images/mulesoft-certified-integration-architect-level-1-exam-mcia-level-1_page_4_Im4.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
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.)

Correct choice is: "The external API reported an error with the HTTP request that was received from the outbound HTTP Request operation of the Mule application" Understanding HTTP 4XX Client Error Response Codes : A 4XX Error is an error that arises in cases<br />
<br />
where there is a problem with the user’s request, and not with the server.<br />
Such cases usually arise when a user’s access to a webpage is restricted, the user misspells the URL, or when a webpage is nonexistent or removed from the public’s view. In short, it is an error that occurs because of a mismatch between what a user is trying to access, and its availability to the user — either because the user does not have the right to access it, or because<br />
<br />
what the user is trying to access simply does not exist. Some of the examples of 4XX errors are 400 Bad Request The server could not understand the request due to invalid syntax. 401 Unauthorized Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response. 403 Forbidden The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401, the client's identity is known to the server. 404 Not Found The server can not find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 to hide the existence of a resource<br />
from an unauthorized client. This response code is probably the most famous one due to its frequent<br />
occurrence on the web. 405 Method Not Allowed The request method is known by the server but has been disabled and cannot be used. For example, an API may forbid DELETE-ing a resource. The two mandatory methods, GET and HEAD, must never be disabled and should not return this error code. 406 Not Acceptable This response is sent when the web server, after performing server-driven content negotiation, doesn't find any content that conforms to the criteria given by the user agent. The external API reported that the API implementation has moved to a different external endpoint cannot be the correct answer as in this situation 301 Moved Permanently The URL of the requested<br />
resource has been changed permanently. The new URL is given in the response. ----------------------------<br />
<br />
------------------------------------------------------------------------------------------------------------------- In Lay man's<br />
term the scenario would be: API CLIENT —> MuleSoft API - HTTP request “Hey, API.. process this” — > External API API CLIENT <– MuleSoft API - http response "I'm sorry Client.. something is wrong with that request" <– (4XX) External API

* Setting a transaction timeout for the Bitronix transaction manager<br />
● Set the transaction timeout either – In wrapper.conf – In CloudHub in the Properties tab of the Mule application deployment mule.bitronix.transactiontimeout = 120 ● The default is 60 secs. It is defined as<br />
<br />
* This property defines the timeout for each transaction created for this manager.<br />
If the transaction has not terminated before the timeout expires it will be automatically rolled<br />
<br />
---------------------------------------------------------------------------------------------------------------------<br />
back.<br />
<br />
Additional Info around Transaction Management: Bitronix is available as the XA transaction manager for Mule applications ● To use Bitronix, declare it as a global configuration element in the Mule application <bti:transaction-manager /> ● Each Mule runtime can have only one instance of a Bitronix transaction manager, which is shared by all Mule applications ● For customer-hosted deployments, define the XA transaction manager in a Mule domain – Then share this global element among all Mule applications in the Mule runtime<br />
<br />
<img src="https://examsqa.com/storage/question-images/mulesoft-certified-integration-architect-level-1-exam-mcia-level-1_page_6_Im5.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" />

Correct answer is EACH item VM message is processed AT LEAST ONCE by ONE ARBITRARY CloudHub worker. Each of the four CloudHub workers can be expected to process some item VM messages In Cloudhub, each persistent VM queue is listened on by every CloudHub worker - But each message is read and processed at least once by only one CloudHub worker and the duplicate processing is possible - If the CloudHub worker fails , the message can be read by another worker to prevent loss of messages and this can lead to duplicate processing - By default , every CloudHub worker's VM<br />
<br />
Listener receives different messages from VM Queue Referenece: https://dzone.com/articles/deploying-mulesoft-application-on-1-worker-vs-mult