MQC traffic behavior supports multiple actions on packets. Please match the following MQC traffic behavior actions with their functions.

Question

Options

• Astatistic enable maps to 'Configuring Traffic Statistics'; permit maps to 'Allow the message to pass'; remark vlan-id maps to 'The VLAN Tag value of the packet'; redirect cpu maps to 'Redirect packets to the CPU'
• BNot provided in the source.
• CNot provided in the source.
• DNot provided in the source.

• A
  83% (35)
• B
  2% (1)
• C
  10% (4)
• D
  5% (2)

Explanation

Option A is correct because each mapping accurately reflects how MQC (Modular QoS CLI) traffic behavior actions function on a network device: statistic enable activates traffic statistics collection for monitoring purposes, permit allows matched packets to forward normally through the device, remark vlan-id rewrites the VLAN tag value in the packet header, and redirect cpu diverts packets away from normal forwarding to be processed by the CPU instead. Options B, C, and D are not valid choices as no alternative mappings were provided in the source material, making A the only viable answer. Each action name is deliberately descriptive: "statistic" hints at counting/monitoring, "permit" means allow, "remark" means rewrite a field, and "redirect cpu" explicitly names both the action and its destination.

Memory tip: Group the four actions by category -- statistics (statistic enable), forwarding decision (permit), header modification (remark vlan-id), and traffic redirection (redirect cpu) -- and remember that MQC behavior actions describe what happens to a packet after it is classified, so the function always follows logically from the action name.

No community discussion yet for this question.