Requester: Copper Transit platform lead. Inputs: an authoritative booking requirement, a permitted-placement constraint and analytical reporting demand. Done: local database configuration and a checked recommendation for correctness, placement, isolation and recovery.
Copper Transit needs unique confirmed bookings and a reliable reporting handoff. You will configure a local Spanner instance and database, then evaluate transaction, placement and recovery decisions from the original fictional brief. Each accepted decision remains in the carried record.
A live database workload is outside this console. The configuration does not prove transaction correctness, permitted residency, application failover or report freshness. Read each requirement as a separate part of the proposed design. A second region may help one failure case while conflicting with a placement rule. The final recommendation must reconcile those constraints and name the tests still needed rather than choose a service from its name.