Which Classic policy option is NOT typically allowed as a standard policy component?

Which Classic policy option is NOT typically allowed as a standard policy component?

• A. DNS
• B. IP
• C. HTTP
• D. TCP

Answer: (A)

Classic policy components in this context are built around network and application-layer features you can inspect and match directly: IP addresses identify where traffic is going, TCP defines the transport connection, and HTTP allows decisions based on web traffic characteristics. DNS isn’t provided as a standard policy component because DNS is a domain-name resolution process rather than a straightforward transport or application-layer signature used in these standard policy items. In practice, you’d handle DNS behavior with DNS-specific controls or separate DNS policies rather than a standard policy element. That’s why DNS is not typically allowed as a standard policy component.

Classic policy components in this context are built around network and application-layer features you can inspect and match directly: IP addresses identify where traffic is going, TCP defines the transport connection, and HTTP allows decisions based on web traffic characteristics. DNS isn’t provided as a standard policy component because DNS is a domain-name resolution process rather than a straightforward transport or application-layer signature used in these standard policy items. In practice, you’d handle DNS behavior with DNS-specific controls or separate DNS policies rather than a standard policy element. That’s why DNS is not typically allowed as a standard policy component.