What is the main benefit of executing a rolling restart in Maximo Manage?

The correct answer is B. It allows for zero downtime during updates. A rolling restart in Maximo Manage updates application server pods one at a time rather than all at once, ensuring some pods remain active and serving users throughout the process - this is what makes zero downtime (B) possible. Option A is wrong because a rolling restart…

Maximo Manage Architecture and System Administration

Question

Options

AIt completely reinitializes the system state.
BIt allows for zero downtime during updates.
CIt clears all user data for security purposes.
DIt forces a recompilation of all BIRT reports.

How the community answered

(37 responses)

A
3% (1)
B
78% (29)
C
5% (2)
D
14% (5)

Explanation

A rolling restart in Maximo Manage updates application server pods one at a time rather than all at once, ensuring some pods remain active and serving users throughout the process - this is what makes zero downtime (B) possible. Option A is wrong because a rolling restart doesn't reinitialize system state; it simply cycles pods with updated configuration or code. Option C is wrong because user data is never cleared during a restart - that would be a destructive operation unrelated to deployment. Option D is wrong because BIRT report recompilation is a separate process triggered by specific actions, not by a restart strategy.

Memory tip: Think of "rolling" like a relay race - one runner hands off the baton before stopping, so the race never pauses. Similarly, a rolling restart hands off traffic before taking a pod down, so users never experience downtime.

Topics

#rolling restart#zero downtime#system updates#MAS administration

Community Discussion

No community discussion yet for this question.

Full C1000-141 Practice