Exam MCIA - Level 1 topic 1 question 42 discussion

Actual exam question from Mulesoft's MCIA - Level 1

Question #: 42
Topic #: 1

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?

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

Show Suggested Answer

Suggested Answer: D 🗳️

by awsExpert007 at June 27, 2021, 5:36 a.m.

Comments

Submit Cancel

edogwest

3 months ago

Selected Answer: D

By packaging the Mule runtime, JVM, and required libraries into a single, version-pinned Docker image, every container that runs your Mule application inherits exactly the same OS libraries, Mule version, and Java settings. Kubernetes then schedules those identical containers onto any worker node, so the execution environment is consistent whatever host the container lands on. The other options are not inherently required by moving to Docker/Kubernetes: B – External client URLs can stay the same if you front the cluster with the same load balancer or ingress name. C – You can run Mule containers in any Kubernetes distribution; adopting Anypoint Platform – PCE is optional. D – Existing monolithic Mule apps still run in a container; adopting microservices is an architectural choice, not a container mandate.

upvoted 1 times

edogwest

3 months ago

Answer should have been 'A' - checked the wrong box

upvoted 1 times

...

gilofernandes

8 months, 3 weeks ago

Selected Answer: D

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/

upvoted 1 times

...

jmay

1 year, 8 months ago

Selected Answer: D

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.

upvoted 1 times

...