How are changes from the MAS customization library typically applied to a Maximo instance?

Question

Options

• ABy manually editing configuration files
• BThrough direct database manipulation
• CUsing an integrated development environment
• DBy redeploying Maximo containers

• A
  3% (1)
• B
  15% (5)
• C
  9% (3)
• D
  74% (25)

Explanation

Redeploying Maximo containers (D) is correct because MAS runs on OpenShift/Kubernetes, where customizations packaged in the MAS customization library are applied by rebuilding and redeploying the container images that run Maximo - this is the standard cloud-native update mechanism for containerized applications.

Why the distractors are wrong:

• A (manual config file editing) - MAS containers are ephemeral; direct file edits are lost on restart and bypasses the proper deployment pipeline.
• B (direct database manipulation) - Database changes alone cannot deliver application-layer customizations like Java classes or UI artifacts managed by the customization library.
• C (IDE integration) - An IDE is used to develop customizations, not to apply them to a running instance; deployment still goes through the container pipeline.

Memory tip: Think of MAS customizations like shipping a new version of an app to an app store - you bundle your changes, publish a new image, and redeploy. The container is the unit of delivery, not a config file or a SQL script.

No community discussion yet for this question.