# Define the infrastructure beyond a prototype

Taiga Learning · Worksheet
https://taiga.training/en/lessons/enterprise-infrastructure/

Use fictional or approved information. Do not put secrets in this worksheet.

## Learning objectives
- Explain what a container and database do not establish by themselves.
- Identify ownership across cloud, platform, application, and delivery systems.
- Define evidence needed before a prototype handles company data.

## Exercise
A fictional tool creates a public web container and managed PostgreSQL database. The company wants employee access and confidential contract records. Complete the seven production questions in this lesson. Mark each answer as verified, missing, or inapplicable with a reason. Name who closes each gap.

## Your response
- Scenario and scope:
- Assumptions and open questions:
- Proposed answer or decision, with reasons:

## Verify your response
| Claim or criterion | Evidence or test | Result or gap | Owner |
| --- | --- | --- | --- |
| | | | |
| | | | |
| | | | |

## Next action
- Action, owner, and date:
- When will you review this response?

## Principle to retain
A deployment target is only part of the operating environment. Verify the complete path for identity, data, release, monitoring, recovery, and ownership.

## Sources
- [AWS: Well-Architected Framework](https://docs.aws.amazon.com/wellarchitected/latest/framework/welcome.html)
- [CNCF: Platforms White Paper](https://tag-app-delivery.cncf.io/whitepapers/platforms/)
- [Google SRE: Implementing SLOs](https://sre.google/workbook/implementing-slos/)

This worksheet supports learning. Completing it does not itself authorize a production change.