The Harbor application team sees a database record and assumes the connection is ready. The review shows a private subnet reference and mTLS enabled, but neither setting proves that the client can resolve the endpoint, reach it or execute an authorized transaction. A database resource and a working application path are different outcomes.
Configure the supplied connection intent, then examine the access and recovery evidence that belongs in a real handoff. The local model does not create private routes, retrieve connection material or run SQL. It also does not restore a backup. Keep those limits visible while deciding which responsibility is covered by the managed service and which must be validated by the application team.
Validate every part of the actual application connection rather than infer access from placement.