A service provider receives customer-marked DSCP values and wants to prevent customers from affecting provider QoS. What is the recommended action at the provider edge?

The recommended action is to apply an inbound service-policy on the PE edge that re-marks or resets DSCP values and police customer traffic. This establishes a trust boundary at the network edge, preventing customers from over-marking traffic and consuming excessive provider resources. Re-marking ensures that customer DSCP values are aligned with the service provider's QoS policy, while policing enforces the agreed-upon bandwidth limits. Incorrect options: Configuring mls qos trust dscp would honor customer markings, which is precisely what the service provider wants to prevent. Relying on core routers to enforce trust boundaries is inefficient and reactive. The problem should be addressed at the network ingress (PE edge) to protect the core. Trusting customer DSCP values and using MPLS EXP bits in the core would still allow customers to influence QoS inappropriately at the edge before the EXP bits are applied.