Exercise 3: Naming the Honest Alternative — Possible Solution
====================================================================

WHY PUMA-BEHIND-NGINX IS NAMED AS THE MORE COMMON CHOICE
------------------------------
Per this chapter, standalone Puma - Rails' own default application server, already bundled in the Gemfile - running behind an nginx reverse proxy is genuinely the more typical production setup most current Rails deployment guides recommend, independent of this specific rebuild project's own circumstances.

WHY PASSENGER WAS STILL CHOSEN FOR THIS CHAPTER
------------------------------
Per this chapter, Passenger is used here specifically because its Apache module lets this chapter continue the same "reuse what's already live" throughline every other rebuild course's own deployment chapter has built - not because it's the field's dominant default choice for a new Rails application in general.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that Puma-behind-nginx is named as the more common modern choice based on real-world Rails deployment practice, and correctly explains that Passenger's own selection here is a deliberate choice serving this course's own specific "modernize in place" narrative rather than a claim that it's generally the better or more typical option.