Challenge 2: Bitrate Set Higher Than the Connection Can Sustain — Solution Walkthrough

What viewers are actually likely to experience:

Per this chapter's own warning box, exceeding your own actual upload
bandwidth doesn't produce smoother, higher-quality video for viewers —
it causes dropped frames and buffering instead. The streamer's modest
upload speed simply cannot deliver data at the rate the high bitrate
setting demands, so viewers experience stuttering, frozen frames, or
frequent buffering interruptions, rather than the improved quality the
streamer was expecting.

Why higher bitrate doesn't help if bandwidth can't support it:

Bitrate determines how much data needs to be uploaded every second to
maintain the stream. If the actual upload connection can't sustain
that data rate, the excess data has nowhere to go — it queues up,
causing delays, or gets dropped entirely, causing visible stutters and
frame loss. The visual quality per frame might theoretically be
higher, but viewers rarely see the benefit if the stream itself is
constantly stuttering or buffering.

What the streamer should do instead:

Lower the bitrate to a level their own actual upload connection can
reliably sustain — even if this means a lower theoretical quality
ceiling, per this chapter's own material a slightly lower, genuinely
sustainable bitrate produces a smoother, better viewing experience
overall than an unsustainably high one.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise directly applies this chapter's own warning box to the
exact bandwidth-mismatch scenario it describes, correctly explaining
why "higher bitrate = better quality" breaks down once upload bandwidth
becomes the limiting factor.