A cloud administrator reports high network bandwidth costs attributed to Cortex XDR operations and asks for bandwidth usage to be optimized without compromising agent functionality. Which two…

Question

Options

• AConfigure P2P download sources for agent upgrades and content updates
• BEnable minor content version updates
• CEnable agent content management bandwidth control
• DDeploy a Broker VM and activate the local agent settings applet

• A
  79% (23)
• B
  14% (4)
• D
  7% (2)

Explanation

Cortex XDR offers two built-in mechanisms that directly address cloud bandwidth consumption. Option A (P2P download sources) allows endpoints within the network to share agent upgrades and content updates with each other, so only one or a few machines pull data from the cloud while the rest receive it locally - dramatically cutting outbound bandwidth. Option C (agent content management bandwidth control) provides throttling controls that limit how much bandwidth Cortex XDR consumes during update operations, preventing it from saturating the network link.

Option B is wrong because enabling minor content version updates controls update granularity, not bandwidth volume - it has no direct effect on how much data traverses the WAN. Option D is a distractor because while a Broker VM serves legitimate purposes (such as enabling connectivity in restricted environments), it is not the designated tool for bandwidth optimization of agent traffic; it doesn't reduce the volume of data consumed by updates or upgrades.

Memory tip: Think of the two correct answers as "share the load" (P2P) and "throttle the flow" (bandwidth control) - both attack the same problem from different angles. If a choice sounds like it's about scheduling or versioning, it's probably not about bandwidth.

No community discussion yet for this question.