A tax assessor must classify civic voice and SCADA into DiffServ PHBs on IOS XE edge routers. Which MQC structure correctly implements that classification and marking?
Select an answer to reveal the explanation.
Short Explanation
MQC is the three-step recipe: pick the ingredients (class-map), cook the treatment (policy-map marks and queues), then plate it on an interface (service-policy). That is how voice and SCADA get real DiffServ PHBs instead of hope-and-FIFO.
Full Explanation
Modular QoS CLI separates classification (class-map), policy actions such as marking to DSCP/PHBs (policy-map), and attachment (service-policy). DiffServ relies on consistent marking and subsequent queueing/policing. Skipping class-maps or never attaching a policy leaves traffic unmarked. Carrier CPE marking alone does not replace campus/edge MQC when the assessor controls the IOS XE edges.