Design and build a secure, reliable, cost-aware solution and review it against the Google Cloud Architecture Framework.
A fintech company wants a production design it can defend to auditors.
The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.
Travel: Staying online when a data centre fails. A booking site went down when one zone failed. The app was spread across zones with load balancing and managed databases. A later zone failure caused no outage.
Startup: Paying only for what is used. Servers sat idle most of the day. Event-driven parts moved to serverless functions and managed services. Monthly costs fell and scaling became automatic.
Manufacturing: Moving out of an old data centre. An ageing data centre needed costly hardware renewal. Workloads were assessed, grouped and migrated to the cloud in waves. The data centre closed on schedule.
Yes. Once your trainer approves it, list it under Projects with the tools you used, one line on the problem it solves and a link to your repository and demo video.
About 20 hours of hands-on work, and it fits best after week 12 of the Google Cloud Engineer (Associate Cloud Engineer) course.
Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.