In Maximo Manage, which option may be used to execute Integrity Checker?

Question

Options

• AAccess the Maximo Admin POD to execute Integrity Checker on the server.
• BAccess the Administration application to activate the Integrity Checker Action.
• CAccess the Database Configuration application to activate the Integrity Checker Action.
• DAccess the WebSphere Application Server console to execute Integrity Checker.

• A
  84% (41)
• B
  4% (2)
• C
  10% (5)
• D
  2% (1)

Explanation

In IBM Maximo Application Suite (MAS) Manage, the containerized architecture moves server-side administrative tasks - including the Integrity Checker - out of the browser UI and into the Kubernetes/OpenShift pod layer, so the correct method is to exec into the Maximo Admin POD and run the tool from the server command line.

Why the distractors are wrong:

• B (Administration application): The Administration app handles user/security settings, not database integrity tools - no Integrity Checker action lives there.
• C (Database Configuration): This is the classic trap. In traditional on-premise Maximo, Integrity Checker is launched from Database Configuration - but MAS Manage's containerized deployment removed that GUI-based path in favor of pod-level execution.
• D (WebSphere Application Server console): MAS Manage runs on Liberty/OpenShift, not WAS, and the app server console was never the correct entry point for Integrity Checker regardless.

Memory tip: Think "container = pod." Whenever MAS Manage asks where to run a server-side admin utility, the answer almost always points to the Admin POD - if the question mentions a traditional Maximo UI path (like Database Configuration), that's the decoy designed to catch people who learned classic Maximo first.

No community discussion yet for this question.