NBAR supports all of these with the exception of which one?

A.
HTTP

B.
IP multicast

C.
TCP flows with dynamically assigned port numbers

D.
non-UDP protocols

Explanation:
Restrictions for Using NBAR
NBAR does not support the following:
More than 24 concurrent URLs, hosts, or Multipurpose Internet Mail Extension (MIME) type
matches.
Matching beyond the first 400 bytes in a packet payload in Cisco IOS releases before Cisco IOS
Release 12.3 (7)T. In Cisco IOS Release 12.3(7)T, this restriction was removed, and NBAR now
supports full payload inspection. The only exception is that NBAR can inspect custom protocol
traffic for only 255 bytes into the payload.
Non-IP traffic
Multiprotocol Label Switching (MPLS)-labeled packets – NBAR classifies IP packets only. You can,
however, use NBAR to classify IP traffic before the traffic is handed over to MPLS. Use the
Modular Quality of Service (QoS) Command-Line Interface (CLI) (MQC) to set the IP differentiated
services code point (DSCP) field on the NBAR-classified packets and make MPLS map the DSCP
setting to the MPLS experimental (EXP) setting inside the MPLS header.
Multicast and other non-CEF switching modes Fragmented packets Pipelined persistent HTTP
requests
URL/host/MIME classification with secure HTTP
Asymmetric flows with stateful protocols
Packets that originate from or that are destined to the router running NBAR
NBAR is not supported on the following logical interfaces:
Fast EtherChannel
Dialer interfaces until Cisco IOS Release 12.2(4) T
Interfaces where tunneling or encryption is used