CLF-C02 ยท Deploying on AWS and global infrastructure
Cloud deployment models and AWS Outposts
Cloud (all-in), hybrid and on-premises (private cloud) deployment models, and AWS Outposts for running AWS infrastructure on premises.
Key points
- Cloud (all-in): every part of the application runs in the cloud.
- Hybrid: cloud resources connected to infrastructure outside the cloud, most often an on-premises data center.
- On-premises (private cloud): your own facility with virtualization; dedicated resources, few cloud benefits.
- AWS Outposts: AWS-owned, AWS-managed racks or servers in your building; EC2 and EBS locally, same APIs, service link to a parent Region.
Source: https://docs.aws.amazon.com/whitepapers/latest/aws-overview/types-of-cloud-computing.html
Practice questions
Which deployment model connects cloud resources with infrastructure that remains in the company's own data center?
- Cloud (all-in)
- Hybrid
- On-premises (private cloud)
- Multi-Region
Show answer
Answer: B. Hybrid
Hybrid deployment links cloud resources and existing resources outside the cloud. Cloud (all-in) runs everything in the cloud, on-premises runs everything locally, and multi-Region describes spreading across AWS Regions, not a deployment model.
Which statements about AWS Outposts are correct?
- The hardware is owned and managed by AWS
- It is installed in a facility the customer provides
- It connects back to a parent AWS Region
- The customer buys and maintains the servers themselves
- It runs with no connection to any AWS Region
Show answer
Answer: A. The hardware is owned and managed by AWS, B. It is installed in a facility the customer provides, C. It connects back to a parent AWS Region
Outposts equipment is owned and managed by AWS, installed at a site the customer provides, and each Outpost extends an Availability Zone of its parent Region over a service link. The customer does not buy the hardware outright, and the Outpost is not independent of AWS Regions.
An on-premises private cloud built with virtualization gives a company the same benefits as the public cloud, such as paying only for what it uses.
Show answer
Answer: False
False. On-premises deployment offers dedicated resources but lacks many cloud benefits: the company still buys hardware up front, plans capacity and maintains facilities, even if virtualization improves utilization.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
