The core ideas a cloud engineer works with every day: service models and regions, identity and access, virtual networks, compute, storage, managed databases, disaster recovery and cost. Examples use real AWS, Azure and Google Cloud service names.
You’re reading a free preview. Sign up to see every topic and question — and to play this deck as games.
What IaaS, PaaS and SaaS hand to the provider, who secures what under the shared responsibility model, and how regions, availability zones and edge locations are laid out.
40 total questions
Card #1
IaaS (Infrastructure as a Service)
Card #2
PaaS (Platform as a Service)
Card #3
SaaS (Software as a Service)
1. A customer leaves a storage bucket open to the public and its files are downloaded by strangers. Under the shared responsibility model, whose failure is this?
2. Your company uses a SaaS email product. Which job is still yours?
3. Your web app runs on servers in one availability zone only, and that zone loses power. What happens?
1. Moving an existing application onto cloud virtual machines with little or no change to its code is often called lift and ___.
Hint: The second half of a phrase about picking something up
2. A cloud environment that one organisation runs only for its own use, on its own premises or hosted by someone else, is a ___ cloud.
Hint: The opposite of public
3. Running workloads on two or more public cloud providers at the same time is called a ___ strategy.
Hint: A prefix meaning many, plus the word cloud
