MCQs on Performance Optimization | AWS Amazon CloudFront MCQs
AWS Amazon CloudFront is a globally distributed content delivery network (CDN) designed for fast and secure delivery of data, applications, and videos to users worldwide. Chapter 3 focuses on topics such as edge location caching, TTL (Time to Live) settings, cache invalidation, leveraging AWS Global Accelerator, and latency optimization techniques to enhance performance.
AWS Amazon CloudFront MCQs – Performance Optimization
Section 1: Edge Location Caching and TTL (Time to Live)
- What is the primary function of edge locations in Amazon CloudFront?
a) Host EC2 instances
b) Cache and deliver content closer to users
c) Manage VPC peering connections
d) Store application logs - In CloudFront, TTL (Time to Live) is used to:
a) Manage content lifecycle in S3
b) Determine how long cached content stays in edge locations
c) Define database timeout settings
d) Configure Lambda execution times - What happens when the TTL of an object expires in CloudFront?
a) The object is immediately deleted from S3
b) The cached object is refreshed from the origin server
c) A new object version is created
d) The request is routed to a different region - Which metric indicates the efficiency of edge location caching?
a) Cache Hit Ratio
b) Lambda Invocation Count
c) TTL Refresh Count
d) Data Transfer Costs - You can control the TTL of cached objects in CloudFront by:
a) Editing the S3 bucket policy
b) Configuring Cache-Control headers
c) Using AWS CLI commands
d) Modifying EC2 instance settings
Section 2: Cache Invalidation
- What does cache invalidation in Amazon CloudFront achieve?
a) Disables all edge locations temporarily
b) Removes specific cached objects from edge locations
c) Changes origin server configuration
d) Clears the entire content delivery network cache - Which method can be used to perform cache invalidation?
a) CloudWatch Events
b) CloudFront Invalidation API
c) S3 Lifecycle Policies
d) AWS Systems Manager - Cache invalidation requests are billed based on:
a) Number of invalidated objects
b) Data transfer to edge locations
c) Cache hit ratios
d) Total size of invalidated objects - What is the default TTL for cached objects in CloudFront if not explicitly set?
a) 0 seconds
b) 1 day
c) 24 hours
d) 7 days - Which feature minimizes the need for frequent cache invalidations in CloudFront?
a) Signed Cookies
b) Versioned URLs
c) Content Delivery Logs
d) CloudTrail Monitoring
Section 3: Using AWS Global Accelerator with CloudFront
- AWS Global Accelerator improves CloudFront performance by:
a) Caching content globally in S3
b) Routing traffic through AWS’s global network
c) Hosting EC2 instances closer to users
d) Distributing workloads across regions - What type of traffic does AWS Global Accelerator optimize?
a) HTTP and HTTPS
b) UDP and TCP
c) VPN and IPsec
d) FTP and SMTP - Which AWS service integrates seamlessly with Global Accelerator for low-latency content delivery?
a) Amazon RDS
b) CloudFront
c) Elastic Load Balancer
d) Amazon Macie - AWS Global Accelerator uses which components to manage traffic?
a) Route 53 hosted zones
b) Anycast IP addresses
c) Edge location logs
d) Lambda@Edge functions - What is the primary difference between AWS Global Accelerator and CloudFront?
a) CloudFront optimizes dynamic content delivery, while Global Accelerator improves static content delivery.
b) Global Accelerator is for optimizing traffic, while CloudFront delivers cached content globally.
c) CloudFront focuses on CDN only, while Global Accelerator enables direct server connections.
d) Global Accelerator is region-specific, while CloudFront is global.
Section 4: Latency Optimization Techniques
- Which AWS CloudFront feature reduces latency by running code at edge locations?
a) AWS Lambda@Edge
b) AWS Direct Connect
c) Amazon ElastiCache
d) AWS Outposts - How can latency be reduced for frequently requested objects in CloudFront?
a) Increasing cache invalidations
b) Using origin failover
c) Pre-warming the cache
d) Using multiple origin servers - What does “origin failover” in CloudFront help with?
a) Automatically switching to a secondary origin if the primary one fails
b) Routing traffic to a different edge location
c) Redirecting users to another AWS region
d) Decreasing TTL for cached content - Which AWS tool can be used to analyze latency issues in CloudFront?
a) AWS X-Ray
b) AWS CodeDeploy
c) AWS DataSync
d) AWS Snowball - What is the role of CloudFront Regional Edge Caches?
a) Store frequently accessed content closer to edge locations
b) Route requests directly to origin servers
c) Compress data before delivery
d) Analyze traffic patterns in real time
Answers
| Q No. | Answer (Option with Text) |
|---|---|
| 1 | b) Cache and deliver content closer to users |
| 2 | b) Determine how long cached content stays in edge locations |
| 3 | b) The cached object is refreshed from the origin server |
| 4 | a) Cache Hit Ratio |
| 5 | b) Configuring Cache-Control headers |
| 6 | b) Removes specific cached objects from edge locations |
| 7 | b) CloudFront Invalidation API |
| 8 | a) Number of invalidated objects |
| 9 | c) 24 hours |
| 10 | b) Versioned URLs |
| 11 | b) Routing traffic through AWS’s global network |
| 12 | b) UDP and TCP |
| 13 | b) CloudFront |
| 14 | b) Anycast IP addresses |
| 15 | b) Global Accelerator is for optimizing traffic, while CloudFront delivers cached content globally |
| 16 | a) AWS Lambda@Edge |
| 17 | c) Pre-warming the cache |
| 18 | a) Automatically switching to a secondary origin if the primary one fails |
| 19 | a) AWS X-Ray |
| 20 | a) Store frequently accessed content closer to edge locations |