Which two steps are needed to disable local spam quarantine before external quarantine is enabled? (Choose two.)

To disable the local (on-box) Spam Quarantine on a Cisco Email Security Appliance (ESA), an administrator must first navigate to the feature's configuration page. This is accomplished by selecting the "Security Services" menu and then clicking on "Spam Quarantine". On the resulting configuration page, the feature is disabled by unchecking the "Enable Spam Quarantine" checkbox. These two steps are prerequisites before configuring an external quarantine, as the local and external quarantine services cannot be enabled simultaneously on the same appliance.

B: The "Monitor" tab is used for viewing quarantined messages and reports, not for enabling or disabling the quarantine service itself.

C: This option pertains to configuring the External Safelist/Blocklist (SLBL), which is a separate feature and does not disable the local spam quarantine.

D: This step is for configuring the external spam quarantine, which is performed after the local quarantine has been disabled, as stated in the question's premise.

1. Cisco

"AsyncOS 14.0 for Email Security User Guide - GD (General Deployment)

" Page 15-2

"Enabling and Configuring the Spam Quarantine on the Email Security Appliance."

This document outlines the procedure for managing the Spam Quarantine. It specifies the navigation path: "Choose Security Services > Spam Quarantine." It also shows the "Enable Spam Quarantine (On-Box)" checkbox on that page

which must be unchecked to disable the feature.

2. Cisco

"Centralized Management with Cisco Security Management Appliance M-Series Appliances

" Page 10-1

"Centralizing Spam Quarantine."

This guide explains

"You can enable the Spam Quarantine on the Security Management appliance to store quarantined messages from one or more Email Security appliances... Before you enable the Spam Quarantine on the Security Management appliance

you must disable the Spam Quarantine on the Email Security appliance." This confirms the procedural dependency described in the question. The steps to disable it on the ESA remain as described in the first reference.