Which ESA feature is used to apply smart identifiers?

Question

Options

• AContent filters
• BRSA data loss prevention engine
• CEncryption policies
• DText resources

• A
  92% (49)
• B
  2% (1)
• C
  4% (2)
• D
  2% (1)

Explanation

Content filters (A) are correct because Cisco ESA includes smart identifiers as a built-in content filter feature - they are predefined pattern-matching rules that detect common sensitive data formats (credit card numbers, Social Security numbers, banking details) directly within the content filtering engine, no additional licensing required.

The RSA DLP engine (B) is a trap answer - it's a separate, enterprise-grade DLP integration that requires additional licensing and configuration; smart identifiers are the lighter, built-in alternative that lives inside content filters. Encryption policies (C) govern how messages are encrypted after a policy match, not how sensitive data is identified in the first place. Text resources (D) are templates used for disclaimers, notifications, and message bodies - purely presentational, with no detection capability.

Memory tip: Think "Smart = Simple filtering" - smart identifiers are the simple, built-in way to catch sensitive data patterns inside content filters, whereas the RSA DLP engine is the heavy enterprise option you only reach for when you need more.

No community discussion yet for this question.