That makes sense too. I guess we need to carefully read the options and choose the one that best fits the procedure for enforcing the agent blockout at system startup.
Haha, I bet the developer who wrote this question is a real comedian. 'Randomize next configuration update time'? What is this, a game of chance? I'll have to go with option B, it seems the most straightforward.
I disagree, I believe the correct answer is B. Enforcing an agent blockout at startup seems more related to configuring the Symantec Management Agent Package install task.
I'm going with option C. Configuring the downloads tab under global agent settings to use bandwidth throttling and restrict 'Agent communications for a set time at startup' sounds like the best way to handle this.
Option D makes the most sense to me. Configuring the target agent settings, under the blockouts tab to 'disable communications at startup' and adding a blackout period seems like the logical way to enforce an agent blockout.
I think option B is the correct answer. Configuring the advanced tab on the Symantec Management Agent Package install task to 'Enforce an agent blockout at startup' seems like the most direct way to ensure the enforcement of an agent blockout at system startup.
Elouise
1 months agoCordelia
1 months agoMuriel
1 months agoElza
1 months agoFranchesca
1 months agoMarci
2 months agoMartha
2 months agoMarvel
10 days agoWayne
11 days agoMaryln
21 days agoEun
1 months agoElouise
2 months agoGlenna
2 months agoXuan
1 months agoSamira
2 months ago