MCIA - Level 1 Exam QuestionsBrowse all questions from this exam
Go to Exam

MCIA - Level 1 Exam - Question 42

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?

Show Answer
Correct Answer: A

Transitioning to container-based Mule application deployments using Docker and Kubernetes ensures that all applications will run in a standardized execution environment dictated by the Docker image, which includes the Mule runtime and all required dependencies. This standardization guarantees consistency of execution environments across all deployments of a Mule application, making option A the expected outcome.

Discussion

7 comments
Sign in to comment
awsExpert007Option: A
Jun 27, 2021

Answer should be A

mgwuOption: A
Aug 29, 2021

A is correct

Outdoor25Option: A
Jan 2, 2022

It should be A

arkadOption: D
Mar 28, 2022

D is the correct answer

madgeezerOption: D
Aug 4, 2022

D. Required redesign of Mule applications to follow microservice architecture principles

jmayOption: D
Dec 2, 2022

Kubernetes cluster can be comprised of heterogeneous worker nodes. So A is not quite necessary. However, since currently "each Mule runtime hosts several Mule applications", any "Domain Project" or patterns, or certain technologies used by current applications must be redesigned. So D is correct.

gilofernandesOption: D
Nov 9, 2023

What is necessary to have in consideration to migrate from a multi-node Mule runtime deployment model to a RTF: Shared resources: Runtime Fabric does not support the usage of domain shared resources In some scenarios, sharing the application logic in Runtime Fabric may be required — for example, error handling, logging, notifications. Modify the pom.xml to change the dependencies for Runtime Fabric. Eg: Mule Maven plugin modify for Runtime Fabric Make changes to the applications that use connectors that are not supported in Runtime Fabric. For example, the File Connector can be replaced with the SFTP connector. Make changes to your applications to replace persistent object stores with external Caching provider like Redis Cache as a custom object store. https://blogs.mulesoft.com/dev-guides/how-to-tutorials/migrating-on-premises-standalone-apps-to-runtime-fabric/