Exercise 3: The Real Risk of a Public /admin/ — Possible Solution
====================================================================

THE REAL RISK
------------------------------
Once deployed publicly, /admin/ is a powerful, largely unrestricted interface available to anyone who successfully logs in - it isn't sandboxed the way the app's own end-user-facing views might be, and a successful login there grants broad ability to view, add, edit, and delete real data directly. Treating it as purely a development convenience with no real exposure risk once the app goes live would be a mistake, since the same interface that's convenient in development becomes a genuine attack surface once it's reachable from the public internet.

TWO REAL MITIGATIONS NAMED
------------------------------
1. Using a genuinely strong password for admin/superuser accounts.
2. Restricting network access to /admin/ where feasible (so it isn't reachable from just anywhere on the internet).

(A third mitigation the chapter also names is using a third-party two-factor authentication package for admin logins - any two of these three would satisfy the question.)

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains that the admin's power and lack of sandboxing become a genuine security exposure once publicly deployed, rather than remaining purely a development-time convenience, and correctly names concrete mitigations (strong passwords, restricted network access, and/or two-factor authentication) the chapter actually mentions.