Core Services for Cloud Architects
Cloud core services are the building blocks every architecture is assembled from: compute such as virtual machines, containers and functions, storage in object, block and file forms, virtual networks, and identity and governance tools that control who can do what. Choosing among them fits the design to the workload.
Stage: Foundations · Part of the Cloud Architect roadmap · Last reviewed 19 November 2026
What to learn in Core Services
- Choose between virtual machines, containers and serverless for a workload
- Match object, block and file storage to access patterns
- Lay out a virtual network with public and private subnets
- Define roles, policies and groups using least privilege
- Organise accounts or subscriptions with guardrails
Core Services interview questions
When would you choose serverless over virtual machines?
Serverless suits event-driven, spiky or low-traffic workloads where you want no server management and pay per execution. Virtual machines fit long-running, stateful or specialised workloads that need full control of the operating system or steady high utilisation.
What is the difference between object, block and file storage?
Object storage holds whole objects with metadata accessed over HTTP and scales cheaply. Block storage presents raw volumes to a server for databases and boot disks. File storage offers shared directories using protocols like NFS or SMB.
Where Core Services fits in the Cloud Architect roadmap
Core Services belongs to the Foundations stage (intermediate level), which takes about 38 hours. Cloud building blocks.
Other units in this stage
Back to the full Cloud Architect roadmap