Q: 8
[Post-Deployment Management and Configuration]
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
techniques should the engineer implement? (Choose two.)
Options
Discussion
I think B and D. Had something like this in a mock, and those two seemed like they reduced bandwidth just by limiting what gets downloaded and using local settings. Could be missing something, but not ruling these out yet.
Don’t think D is the right fit unless you’re dealing with segmentation or brokers specifically. A and C actually target bandwidth reduction: P2P reduces cloud pulls, and bandwidth control limits usage. Pretty sure that's what the question wants, but open to other views.
B . Enabling minor content version updates should also help with bandwidth, since it only pulls smaller/delta updates. Not sure if that's actually as effective as the other options, but feels like B plus C would reduce costs. Thoughts?
My vote is it’s A and C. Setting up P2P downloads (A) means agents can pull updates from each other instead of all hitting the cloud, which really cuts bandwidth. C lets you actually limit how much bandwidth gets used for content updates. Unless your network is really segmented, D isn’t as useful here. If anyone’s implemented D in a straightforward setup and saw benefit, let me know!
Looks like A and C. P2P updates (A) let agents grab files from each other, cutting download traffic, and C gives you more direct bandwidth control. Not fully certain, but these two seem the most efficient for this scenario.
Don’t think D is right here. A looks like a trap unless you want new infra, pretty sure it’s A and C.
A C tbh. P2P agent updates (A) keep most traffic local, and bandwidth management (C) lets you set limits directly. D is mostly for segmented setups, so not as helpful here unless the infra is split up. Not 100% but seems right according to what I've seen in practice.
I think A, C. Both directly target bandwidth optimization without extra infra. Not seeing how D fits unless you're segmenting the network more heavily. Open to other ideas if I'm missing a use case.
I was thinking C and D since Broker VM (D) acts as local relay, so less cloud traffic. C is obvious for direct bandwidth management. Not totally sure though, maybe A helps more internally? Open to better logic here.
A and C tbh. P2P update sharing (A) keeps traffic local, and bandwidth management (C) lets you throttle usage, so both help cut cloud network costs. D feels more about segmentation than basic bandwidth savings.
Be respectful. No spam.
