Requester: Harbor service owner. Evidence: the app source range is 10.42.1.0/24, PostgreSQL listens on 5432, and the database must stay private. Question: what narrow repair and validation sequence addresses the connection without creating public database access?
Harbor Support reports that a newly deployed application cannot connect to its private database. You will work through one account, carrying every accepted change into the next step. The initial resources are a fictional company's starting configuration, not a blank cloud account. Your deliverable is the final account state and the checked decision at the end.
Inspect the named resources before changing them. Earlier work remains part of the requirements, so a later step must preserve it. Some steps use a prepared JSON or YAML file; read its contents and then verify the resulting configuration. Other steps ask for a recommendation supported by the evidence you've established. The final check includes previous requirements as well as the new one, which prevents a quick repair from undoing an earlier protection.