A managed relational service removes some database infrastructure work while leaving the application contract with its owner. Copper Transit needs a PostgreSQL configuration, private connection intent and a recovery plan. Those requirements do not become one proven outcome merely because a Cloud SQL instance record is present.
Read the engine version, machine choice, availability setting, network and backup window separately. A private-only setting still needs a real supported network path. Regional availability does not reverse a mistaken application update, and a scheduled backup is not a tested restore. The local adapter stores those settings without running PostgreSQL, creating private service access, measuring query performance or executing failover. You will configure fictional requirements and choose the additional evidence needed for a production handoff. Use the explicit service boundary to avoid claiming more than the exercise can show.
Separate database settings from the connection and recovery proof.