A recent engine update was pulled down for graymail and has caused the service to start crashing. It is critical to fix this as quickly as possible. What must be done to address this issue?

The correct answer is A. Roll back to a previous version of the engine from the Services Overview page. On Cisco ESA, the Services Overview page provides visibility into running service engines (including graymail, anti-spam, anti-virus, etc.) and allows administrators to roll back to a previously installed engine version without waiting for a new update. This is the correct and…

Cisco Email Security Appliance Administration

Question

Options

ARoll back to a previous version of the engine from the Services Overview page.
BRoll back to a previous version of the engine from the System Health page.
CDownload another update from the IMS and Graymail page.
DDownload another update from the Service Updates page.

How the community answered

(26 responses)

A
92% (24)
C
4% (1)
D
4% (1)

Explanation

On Cisco ESA, the Services Overview page provides visibility into running service engines (including graymail, anti-spam, anti-virus, etc.) and allows administrators to roll back to a previously installed engine version without waiting for a new update. This is the correct and fastest remediation path when a pulled engine update causes service instability. The System Health page (B) monitors appliance health metrics but does not offer engine rollback controls. Downloading another update from IMS and Graymail (C) or Service Updates (D) would push the same broken version again and would not resolve the crash.

Topics

#ESA Troubleshooting#Engine Rollback#Services Overview Page

Community Discussion

No community discussion yet for this question.

Full 300-720 Practice