How are changes applied when using the MAS customization library?

Question

Options

• ABy restarting the entire system
• BThrough direct database manipulation
• CBy deploying custom containers
• DThrough an integrated update tool within MAS

• A
  14% (6)
• B
  2% (1)
• C
  79% (34)
• D
  5% (2)

Explanation

Option C is correct because IBM Maximo Application Suite (MAS) is built on a containerized, cloud-native architecture (Kubernetes/OpenShift), so customizations are packaged as custom container images that layer on top of the base MAS containers and are deployed through the orchestration platform. The MAS customization library provides a structured framework for building these images, allowing organizations to bundle their custom code, scripts, and configurations into deployable containers.

Option A is wrong because the container-based approach enables rolling deployments - individual pods are updated without taking down the entire system. Option B is wrong because direct database manipulation bypasses the application layer entirely and is an unsupported, risky practice that could corrupt data or break integrity constraints. Option D is wrong because MAS does not provide a built-in GUI update tool for applying customizations; the deployment pipeline itself (via the container registry and Kubernetes) is the mechanism.

Memory tip: Think "MAS = containers all the way down." Just as MAS itself runs in containers, your customizations live in containers too - you ship code by shipping images.

No community discussion yet for this question.