Challenge 1: Upgrading Internet for an Encoding-Overload Problem — Solution Walkthrough

Why this fix wouldn't actually help:

Per this chapter's own material, network-related dropped frames and
rendering/encoding-related dropped frames are two genuinely different
problems with different causes. In this scenario, the Stats Dock shows
zero network-related dropped frames and instead shows encoding
overload with CPU usage near 100% — a clear sign the actual bottleneck
is the computer's own inability to encode video fast enough, not
anything related to the internet connection's upload speed at all.

Why upgrading internet specifically misses the actual cause:

An internet upgrade increases available upload bandwidth — genuinely
useful if the problem were a bitrate/bandwidth mismatch. But since the
Stats Dock already shows the network side is fine (zero network-
related dropped frames) and the actual problem is the CPU being
maxed out trying to encode, more bandwidth does nothing to help the
CPU encode any faster. The bottleneck sits entirely on the computer's
own processing side, not anywhere the internet connection could
address.

What would actually help, per this chapter's own material:

Switching to a hardware encoder (NVENC/AMF/QuickSync, per Chapter 4),
lowering the output resolution or framerate, or reducing the
encoder's own preset/complexity setting — all of which reduce the
actual CPU workload causing the overload, unlike an internet upgrade,
which addresses an entirely different resource.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise directly applies this chapter's own warning box to a
concrete Stats Dock reading, correctly using the specific numbers given
(100% CPU, zero network drops) to justify why the internet upgrade
was the wrong fix.