Scope the workload and cloud boundary

Begin by checking an offer against five cloud characteristics, separating absent evidence from a demonstrated contradiction for the particular service. Distinguish service models from deployment models and assign remaining application, identity and data duties to the customer or provider according to the actual offer. Then turn a vague booking brief into measurable requirements: request type and peak, booking success, acceptable data loss and recovery time. Produce a characteristic evidence table, responsibility matrix and unit-aware requirements sheet. Seek a specific observation rather than accept provider branding or a rate without a measurement window, and distinguish service capability from success of the workload that uses it. The unit closes by identifying which decisions the specialist can prepare and which belong to service and data owners.

Read the whole first subject without an account: its lessons, summary and review questions.