Exercise 3: Folder-Level Binding Applied to a Later Project — Possible Solution
====================================================================

GCP's own real IAM policy bindings inherit downward through the
resource hierarchy automatically - a binding applied at the Folder
level cascades to every Project (and every resource inside those
Projects) beneath that Folder, with no need to configure the binding
again at each individual Project.

Because the Project in this scenario is created inside that same
Folder - even though it didn't exist yet when the binding was first
made - it is a real, genuine child of that Folder in the hierarchy.
Inheritance in GCP's model is continuous and automatic, not a one-time
snapshot taken at the moment the binding was created.

ANSWER: The principal automatically has Viewer access to the new
Project as well, with zero additional configuration needed - the
Folder-level binding applies to any resource created beneath it,
including Projects created after the binding itself was made,
because GCP's real IAM inheritance is ongoing rather than fixed at
binding-creation time.

WHY THIS WORKS AS AN ANSWER
------------------------------
This correctly applies the same real, ongoing-inheritance principle
already established in Chapter 1's own Exercise 1 (an Organization-
level role applying to a later-created Project) to a Folder-level
binding instead - showing the same real mechanism holds consistently
at every level of the hierarchy, not just the topmost one.