Académique Documents
Professionnel Documents
Culture Documents
1. AWS recommends using ___ public and ____ private subnets per Availability
Zone
1/1
2. A CIDR notation of /20 includes a set of 4,096 IPs. How many IPs does /22
include?
1,024
3. Which of the following are true about VPC peering? (Select 3)
VPCs cannot transitively connect to VPCs they are not peered with through a
VPC they are peered with.
Peered VPCs must reside in the same region.
The IP space of peered VPCs cannot overload.
4. A customer is using AWS to host development, testing, and production of one
small application that is managed by one IT team that consists of three
members. The application handles highly sensitive data and needs to store it in
several different countries. What type of solution do you recommend they use?
Multi-Account, isolating data with accounts
5. Why are fewer subnets of larger sizes preferred over higher numbers of
subnets of smaller sizes? (Select 2)
Workload placement is simplified with fewer subnets.
You are less likely to run out of IP addresses with fewer subnets.
6. On AWS, a subnet with a /20 CIDR notation includes how many IP addresses
that are available for your use?
4,091
7. AWS recommends that if you are unsure exactly how many Availability Zones
to use, you should start with ____ per region?
2
8. Which of the following is true about choosing a region? (Select 2)
Your choice of region could significantly impact your sales.
Some regions do not provide you with the ability to use all AWS services.
9. Which of the following are true about route tables? (Select 3)
Each subnet in a VPC must be associated with a route table
Each VPC is given a route table by default when the VPC is created.
Route tables can be shared between subnets
10. Why would high-performance computing (HPC) not function best in a multi-
VPC or multi-account environment?
Multi-VPC and multi-account environments introduce additional latency, which
is negligible for the most applications but could slow HPC applications down
unnecessarily.
CCA 3.03 System Design for High Availability (Part I & II)