An administrator has configured a QoS policy rule and a QoS Profile that limits the maximum allowable bandwidth for the YouTube application. However, YouTube is consuming more than the maximum…

Question

Options

• AEnable QoS interface
• BEnable QoS in the Interface Management Profile
• CEnable QoS Data Filtering Profile
• DEnable QoS monitor

• A
  71% (17)
• B
  8% (2)
• C
  4% (1)
• D
  17% (4)

Explanation

Configuring a QoS Profile and Policy Rule defines what restrictions should apply, but QoS enforcement only activates when you explicitly enable QoS on the egress interface - without this step, the firewall simply ignores the policy, allowing YouTube to consume unrestricted bandwidth. Option B is wrong because Interface Management Profiles govern management access (SSH, HTTPS, ping) to the interface itself, not traffic-shaping behavior. Option C is a fabricated distractor - "QoS Data Filtering Profile" is not a real Palo Alto Networks configuration object; Data Filtering Profiles are DLP security constructs unrelated to bandwidth control. Option D is wrong because QoS Monitor is an observability/reporting tool for viewing QoS statistics, not a prerequisite for enforcement.

Memory tip: Think of QoS as a three-legged stool - Profile (the limits), Policy (who gets them), and Interface (the on/off switch). You can build two legs all day, but nothing stands until the interface leg is in place.

No community discussion yet for this question.