MCQs on VPC Scaling and High Availability | AWS Amazon VPC Virtual Private Cloud
Get ready to strengthen your understanding of AWS Amazon VPC with this set of carefully crafted MCQ questions and answers. These questions cover essential topics such as Elastic Load Balancers (ELB), Auto Scaling in VPC, and Multi-Region Architectures, helping you sharpen your skills in VPC scaling and high availability.
5. VPC Scaling and High Availability
1-10: Elastic Load Balancers (ELB)
- What is the main function of an Elastic Load Balancer (ELB) in AWS?
a) To automatically scale EC2 instances
b) To distribute incoming traffic across multiple targets
c) To manage VPC CIDR blocks
d) To create a virtual private network - Which of the following is a type of ELB?
a) Application Load Balancer
b) EC2 Load Balancer
c) Gateway Load Balancer
d) Network Balancer - ELB automatically distributes traffic based on:
a) Traffic volume only
b) The region
c) Health of targets and routing rules
d) Security group settings - How does the Application Load Balancer (ALB) route traffic?
a) Based on IP addresses
b) Based on request content such as URL path
c) Based on user location
d) Based on session cookies - Which ELB type is best for TCP traffic?
a) Application Load Balancer
b) Network Load Balancer
c) Classic Load Balancer
d) Internal Load Balancer - Which service does ELB integrate with for automated instance health checks?
a) CloudWatch
b) EC2 Auto Scaling
c) Lambda
d) Route 53 - What is the benefit of using an ELB in a VPC?
a) It encrypts traffic
b) It automatically configures security groups
c) It distributes traffic to multiple availability zones
d) It provides a static IP address - What feature does the Application Load Balancer support that the Classic Load Balancer does not?
a) SSL termination
b) Path-based routing
c) Health checks
d) DNS support - Which of the following is a valid use case for a Network Load Balancer?
a) Content-based routing
b) Handling millions of requests per second with low latency
c) Application session management
d) Managing static web hosting - How can you secure communication between ELB and EC2 instances?
a) Using IAM roles
b) Using VPC Peering
c) By enabling SSL/TLS encryption
d) By deploying EC2 instances in private subnets
11-20: Auto Scaling in VPC
- What is the main purpose of Auto Scaling in AWS VPC?
a) To create multiple VPCs
b) To automatically adjust the number of EC2 instances
c) To monitor EC2 instances
d) To manage Elastic IP addresses - Auto Scaling works in conjunction with:
a) CloudFormation
b) Elastic Load Balancer
c) VPC Peering
d) AWS Organizations - Which of the following can trigger Auto Scaling to launch or terminate instances?
a) Predefined rules based on CloudWatch metrics
b) Manual intervention
c) External DNS changes
d) Changes in instance type - When setting up Auto Scaling, you must define a:
a) Launch Configuration or Launch Template
b) Network Access Control List
c) Route Table
d) VPN Connection - Which metric does Auto Scaling use to monitor performance?
a) EC2 instance cost
b) CloudWatch metrics
c) Security Group usage
d) Lambda invocation count - Auto Scaling allows instances to scale based on:
a) Time of day
b) Instance type
c) CloudWatch alarms
d) VPC CIDR block changes - Which Auto Scaling feature allows EC2 instances to scale across multiple availability zones?
a) Elastic IP
b) Multi-AZ scaling
c) VPC Peering
d) VPC Flow Logs - Which Auto Scaling feature is used to ensure that new instances are registered with ELB?
a) Instance health checks
b) VPC Flow Logs
c) Auto Scaling Groups
d) Security groups - What is the function of an Auto Scaling Group in a VPC?
a) It defines the EC2 instance size
b) It automates instance launching and terminating
c) It handles database backups
d) It monitors network traffic - How can Auto Scaling improve application availability in VPC?
a) By isolating traffic within one region
b) By scaling up during high traffic
c) By limiting traffic across multiple availability zones
d) By restricting VPC Peering connections
21-30: Multi-Region Architectures
- What is the main advantage of deploying a Multi-Region architecture?
a) Reduced network latency
b) Enhanced data replication
c) Improved fault tolerance and disaster recovery
d) Simplified IAM roles management - When configuring Multi-Region VPCs, you must consider:
a) VPC Peering across regions
b) DNS settings only
c) VPC Flow Logs
d) IAM roles for different regions - How can AWS services communicate across different VPCs in different regions?
a) Using VPC Peering
b) Using VPN Connections
c) Using Transit Gateway
d) Using S3 Transfer Acceleration - Which AWS service helps connect VPCs across regions without requiring VPC Peering?
a) AWS Direct Connect
b) Amazon Route 53
c) AWS Transit Gateway
d) AWS DataSync - In a Multi-Region architecture, how can you route traffic to the nearest region?
a) By using VPC Peering
b) By using CloudFront
c) By using Route 53 latency routing
d) By using IAM policies - What is the key feature of AWS Global Accelerator for Multi-Region architectures?
a) It improves application availability and performance
b) It encrypts data between regions
c) It manages instance health
d) It scales EC2 instances - How do you ensure high availability when deploying a Multi-Region architecture?
a) By using Elastic Load Balancing across regions
b) By deploying only in one region
c) By using multiple NAT Gateways
d) By reducing EC2 instance size - Which AWS service can help with replication of data across regions?
a) AWS Lambda
b) Amazon S3 Cross-Region Replication
c) Amazon EC2 Auto Scaling
d) AWS Backup - In a Multi-Region architecture, what is the role of Route 53?
a) To provide DNS routing based on latency
b) To manage IAM roles
c) To monitor EC2 instances
d) To scale EC2 instances - What should you consider when setting up a Multi-Region architecture in AWS?
a) Inter-region network latency
b) EC2 instance size
c) The number of availability zones
d) Security group configurations
Answer Key
| Qno | Answer (Option with Text) |
|---|---|
| 1 | b) To distribute incoming traffic across multiple targets |
| 2 | a) Application Load Balancer |
| 3 | c) Health of targets and routing rules |
| 4 | b) Based on request content such as URL path |
| 5 | b) Network Load Balancer |
| 6 | b) EC2 Auto Scaling |
| 7 | c) It distributes traffic to multiple availability zones |
| 8 | b) Path-based routing |
| 9 | b) Handling millions of requests per second with low latency |
| 10 | c) By enabling SSL/TLS encryption |
| 11 | b) To automatically adjust the number of EC2 instances |
| 12 | b) Elastic Load Balancer |
| 13 | a) Predefined rules based on CloudWatch metrics |
| 14 | a) Launch Configuration or Launch Template |
| 15 | b) CloudWatch metrics |
| 16 | c) CloudWatch alarms |
| 17 | b) Multi-AZ scaling |
| 18 | c) Auto Scaling Groups |
| 19 | b) It automates instance launching and terminating |
| 20 | b) By scaling up during high traffic |
| 21 | c) Improved fault tolerance and disaster recovery |
| 22 | a) VPC Peering across regions |
| 23 | c) Using Transit Gateway |
| 24 | c) AWS Transit Gateway |
| 25 | c) By using Route 53 latency routing |
| 26 | a) It improves application availability and performance |
| 27 | a) By using Elastic Load Balancing across regions |
| 28 | b) Amazon S3 Cross-Region Replication |
| 29 | a) To provide DNS routing based on latency |
| 30 | a) Inter-region network latency |