Master AWS Certifications with Confidence

Reserved Instances

Dedicated Hosts

Spot Instances

On-Demand Instances

Deploy EC2 instances in multiple AWS Regions and use Route 53 latency-based routing.

Use an Application Load Balancer to distribute traffic across EC2 instances in multiple Availability Zones.

Configure Amazon CloudFront to distribute content with the EC2 instances as the origin.

Implement AWS Global Accelerator to route traffic to EC2 instances through the AWS backbone network.

Use IAM roles for user authentication. Deploy Amazon API Gateway HTTP APIs with an IAM authorizer.

Configure an Amazon Cognito user pool for user authentication. Deploy Amazon API Gateway REST APIs with a Cognito authorizer.

Configure an Amazon Cognito identity pool for user authentication. Deploy Amazon API Gateway HTTP APIs with a Cognito authorizer.

Implement a custom AWS Lambda function for user authentication. Deploy Amazon API Gateway REST APIs with a Lambda authorizer.

Configure MySQL binary replication to an Aurora cluster in the secondary Region, maintaining a single DB instance there.

Create an Aurora global database and delete the DB instance in the secondary Region after setup.

Use AWS DMS for continuous replication to the secondary Region and delete the secondary DB instance.

Deploy an Aurora global database with one DB instance in the secondary Region.

Use Amazon Route 53 weighted routing policy configured as 100/0 between the primary and disaster recovery Regions. Set Time to Live (TTL) to 1 hour.

Configure Amazon Route 53 with a failover routing policy for primary-to-disaster recovery Region routing. Set TTL to 30 seconds.

Deploy an Amazon Aurora Global Database with read replicas in both Regions to enable low-latency cross-Region data access.

Schedule hourly snapshots of the Amazon RDS database in the primary Region and replicate them to Amazon S3. Use S3 cross-Region replication to the disaster recovery Region. Restore from snapshots during failover.

Implement a warm standby model using Auto Scaling groups for web/application tiers across Availability Zones. Use Reserved Instances for baseline capacity and On-Demand Instances for scaling.

Use Auto Scaling groups with Spot Instances for web/application layers across multiple Availability Zones.

Create an S3 access point for each department in the central account hosting the bucket. Restrict each access point to the respective VPC. Update the bucket policy to enforce access via access points.

Create an interface VPC endpoint for S3 in each department's VPC. Attach an endpoint policy allowing access to the S3 access point. Associate the endpoint with the VPC's security groups.

Establish a gateway endpoint for S3 in each department's VPC. Configure the endpoint policy to permit access to the S3 access point. Update the route tables to direct traffic through the gateway endpoint.

Deploy an S3 access point in each department's AWS account and link it to the central S3 bucket. Restrict each access point to the department's VPC. Modify the bucket policy to require access through these access points.

Create a gateway endpoint in the central account's VPC. Attach an endpoint policy allowing access to the S3 bucket. Update the route tables to route traffic via the gateway.

Use an SQS FIFO queue. Adjust the visibility timeout setting appropriately.

Use an SQS standard queue with a SendMessageBatchRequestEntry structure. Configure the DelaySeconds parameter.

Use an SQS standard queue with a SendMessageBatchRequestEntry structure. Adjust the visibility timeout setting.

Use an SQS FIFO queue. Configure the DelaySeconds parameter.

Create a global secondary index (GSI) with OrderDate as the sort key.

Modify the sort key to be OrderDateDescending and update the data type to String.

In the Query operation, set the ScanIndexForward parameter to false.

In the Query operation, set the KeyConditionExpression to use a descending sort.