Challenge 2: What a Premiere Editor Would Need for Deep Audio Cleanup — Solution Walkthrough

What they'd need to do:

Switch to Adobe Audition, a separate application entirely, per this
chapter's own material.

Why, per this chapter's own material:

Premiere Pro only has basic audio tools built directly into its own
timeline — genuinely deep audio work in the Premiere ecosystem
requires switching to Audition specifically. This means the Premiere
editor's workflow for deep dialogue cleanup involves leaving Premiere
Pro, doing the audio work in a completely separate application, and
then bringing the result back into their video project.

Why a Resolve editor wouldn't need this extra step:

Per this chapter's own material, Resolve's own Fairlight page keeps
all of this inside one single application — no context-switching
required at all. A Resolve editor doing the same deep dialogue cleanup
could do it directly on the Fairlight page without ever leaving the
project or switching to a separate piece of software.

Why this is a genuine, named advantage rather than an even-handed
comparison:

This chapter explicitly frames this as "a real, concrete advantage
worth naming plainly... not just diplomatic even-handedness" — the
workflow difference here is a real, practical convenience gap, not
simply two different but equally deep options.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise is a direct, practical application of this chapter's own
Premiere-Pro-vs-Resolve audio material to a concrete workflow
question, correctly naming Audition as the required extra step.