Table of Contents
Question
An administrator notices that the Cisco ESA delivery queue is consistently full. After further investigation, it is determined that the IP addresses currently in use by the Cisco ESA are being rate-limited by some destinations. The administrator creates a new interface with an additional IP address using virtual gateway technology, but the issue is not solved. Which configuration change resolves the issue?
A. Use the CLI command alt-src-host to set the new interface as a possible delivery candidate.
B. Use the CLI command loadbalance auto to enable mail delivery over all interfaces.
C. Use the CLI command deliveryconfig to set the new interface as the primary interface for mail delivery.
D. Use the CLI command altsrchost to set the new interface as the source IP address for all mail.
Answer
B. Use the CLI command loadbalance auto to enable mail delivery over all interfaces.
Explanation
To resolve the issue of the Cisco ESA delivery queue consistently being full due to rate limitations on the existing IP addresses, the configuration change that would likely solve the problem is to use the CLI command “loadbalance auto” (Option B).
Here’s a comprehensive explanation of the options:
A. Use the CLI command “alt-src-host” to set the new interface as a possible delivery candidate: The “alt-src-host” command is used to specify an alternative source IP address for outgoing mail. While this command can be used to set the new interface as a possible delivery candidate, it may not solve the issue of rate limitations on the existing IP addresses. It does not directly address the load balancing or distribution of outgoing mail over multiple interfaces.
B. Use the CLI command “loadbalance auto” to enable mail delivery over all interfaces: The “loadbalance auto” command is used to configure the Cisco ESA to automatically distribute outgoing mail across all available interfaces. This configuration change would likely resolve the issue of rate limitations by allowing the ESA to utilize the additional IP address and interface effectively. It ensures that the load is balanced across multiple interfaces, increasing the chances of successful mail delivery.
C. Use the CLI command “deliveryconfig” to set the new interface as the primary interface for mail delivery: The “deliveryconfig” command is used to configure the delivery settings on the Cisco ESA. While setting the new interface as the primary interface might help direct some outgoing mail through that interface, it may not fully address the problem of rate limitations on the existing IP addresses. It does not ensure load balancing or distribution of outgoing mail across multiple interfaces.
D. Use the CLI command “altsrchost” to set the new interface as the source IP address for all mail: The “altsrchost” command is used to specify an alternative source IP address for outgoing mail. While setting the new interface as the source IP address may help in certain scenarios, it does not directly address the issue of rate limitations on the existing IP addresses or facilitate load balancing of outgoing mail.
In conclusion, to resolve the issue of the Cisco ESA delivery queue consistently being full due to rate limitations on the existing IP addresses, the recommended configuration change is to use the CLI command “loadbalance auto” (Option B). This command enables the ESA to distribute outgoing mail across all available interfaces, including the new interface, ensuring better load balancing and increasing the chances of successful mail delivery.
Securing Email with Cisco Email Security Appliance (300-720 SESA) certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the Securing Email with Cisco Email Security Appliance (300-720 SESA) exam and earn Securing Email with Cisco Email Security Appliance (300-720 SESA) certification.