Q: 1
Which two statements apply when a customer has a large branch office with employees who all
arrive and log in within a five-minute time period? (Choose two.)
Options
Discussion
Makes sense to pick B and C here since the scenario is that huge login burst. The 64 pending TCP DNS requests limit (B) and the 3 retry cap (C) both matter most during a login storm like this. Pretty sure that's the intent, but open to corrections.
C vs B. C makes sense since DNS retries would kick in with lots of simultaneous logins making some queries fail and retry. B could also matter if so many people log in at once that you max out the pending requests, but not totally sure because sometimes these limits are only hit in really big surges. Anyone else see official docs mention both at once?
That burst login window makes me think B and C are right. The 64 pending TCP DNS request cap would matter most with tons of simultaneous queries, and 3 retries fits for failures. Could be a trap with D if thinking about caching though.
If the branch has async logins spread out, does the pending TCP DNS request cap (B) actually limit anything?
B and C look right, but does "all employees" mean literally everyone logs in at the same moment? If it was staggered, maybe the pending request cap wouldn’t be as much of an issue. Official guide covers these limits pretty well.
Be respectful. No spam.
