問題一覧
1
Opt for Multi-AZ configuration with automatic failover functionality to help mitigate failure
2
test.example.com
3
Amazon CloudFront can route to multiple origins based on the content type, Use field level encryption in Amazon CloudFront to protect sensitive data for specific content, Use an origin group with primary and secondary origins to configure Amazon CloudFront for high-availability and failover
4
Copy data from the source bucket to the destination bucket using the aws S3 sync command, Set up Amazon S3 batch replication to copy objects across Amazon S3 buckets in another Region using S3 console and then delete the replication configuration
5
Use Amazon EventBridge to decouple the system architecture
6
Use a Network Load Balancer with an Auto Scaling Group
7
Use Amazon RDS Read Replicas
8
AWS Snowball Edge Compute Optimized
9
Warm Standby
10
Use multi-part upload feature of Amazon S3
11
The Time To Live (TTL) is still in effect
12
Use Amazon Elastic Container Service (Amazon ECS) with AWS Fargate for serverless orchestration of the containerized services, Use Amazon Elastic Kubernetes Service (Amazon EKS) with AWS Fargate for serverless orchestration of the containerized services
13
The instance with the oldest launch template or launch configuration will be terminated in AZ-B
14
Use AWS CloudTrail to analyze API calls
15
Create a Golden Amazon Machine Image (AMI) with the static installation components already setup, Use Amazon EC2 user data to customize the dynamic installation parts at boot time
16
Pilot Light
17
Create an Amazon Machine Image (AMI) after installing the software and copy the AMI across all Regions. Use this Region-specific AMI to run the recovery process in the respective Regions
18
The Auto Scaling group should be configured with the minimum capacity set to 4, with 2 instances each in two different Availability Zones. The maximum capacity of the Auto Scaling group should be set to 6
19
A process replaces an existing object and immediately tries to read it. Amazon S3 always returns the latest version of the object
20
Network Load Balancer
21
Create a new launch configuration to use the correct instance type. Modify the Auto Scaling group to use this new launch configuration. Delete the old launch configuration as it is no longer needed
22
Use database cloning to create multiple clones of the production database and use each clone as a test database
23
The Auto Scaling group is using Amazon EC2 based health check and the Application Load Balancer is using ALB based health check
24
3
25
Set up Amazon Route 53 active-passive type of failover routing policy. If Amazon Route 53 health check determines the Application Load Balancer endpoint as unhealthy, the traffic will be diverted to a static error page, hosted on Amazon S3 bucket
26
Use cross-Region Read Replicas, Enable the automated backup feature of Amazon RDS in a multi-AZ deployment that creates backups across multiple Regions
27
By default, cross-zone load balancing is enabled for Application Load Balancer and disabled for Network Load Balancer
28
The CNAME record will be updated to point to the standby database
29
http://169.254.169.254/latest/meta-data/public-ipv4
30
Enable an Amazon Route 53 health check
31
http://bucket-name.s3-website-Region.amazonaws.com, http://bucket-name.s3-website.Region.amazonaws.com
32
Only Standard Amazon SQS queue is allowed as an Amazon S3 event notification destination, whereas FIFO SQS queue is not allowed
33
Handle all read operations for your application by connecting to the reader endpoint of the Amazon Aurora cluster so that Aurora can spread the load for read-only connections across the Aurora replica, Create a replica Aurora instance in another Availability Zone to improve the availability as the replica can serve as a failover target
34
Use a dead-letter queue to handle message processing failures
35
Auto Scaling group scheduled action
36
Create two Amazon SQS standard queues: one for pro and one for lite. Set up Amazon EC2 instances to prioritize polling for the pro queue over the lite queue
37
Use Amazon CloudFront signed URLs, Use Amazon CloudFront signed cookies
38
Amazon ElastiCache for Memcached
39
Any database engine level upgrade for an Amazon RDS database instance with Multi-AZ deployment triggers both the primary and standby database instances to be upgraded at the same time. This causes downtime until the upgrade is complete
40
Create an Amazon S3 Event Notification that sends a message to an Amazon SQS queue. Make the Amazon EC2 instances read from the Amazon SQS queue
41
Create an Auto-Scaling group with a desired capacity of a total of two Amazon EC2 instances across two Availability Zones. Configure an Application Load Balancer having a target group of these Amazon EC2 instances. Set up Amazon RDS MySQL DB in a multi-AZ configuration
42
Run the custom scripts as user data scripts on the Amazon EC2 instances
43
Amazon MQ
44
Create a read-replica with the same compute capacity and the same storage capacity as the primary. Point the reporting queries to run against the read replica
45
Provisioned IOPS SSD Amazon EBS volumes
46
Amazon Aurora Serverless
47
Opt for two separate AWS Direct Connect connections terminating on separate devices in more than one Direct Connect location
48
Amazon RDS applies operating system updates by performing maintenance on the standby, then promoting the standby to primary and finally performing maintenance on the old primary, which becomes the new standby, Amazon RDS automatically initiates a failover to the standby, in case primary database fails for any reason
49
Application Load Balancer + dynamic port mapping
50
Set up Amazon EBS as the Amazon EC2 instance root volume and then configure the application to use Amazon S3 as the document store
xj9 - 19628 - a
xj9 - 19628 - a
critical flaw · 98問 · 2年前xj9 - 19628 - a
xj9 - 19628 - a
98問 • 2年前xj9 - 19628 - b
xj9 - 19628 - b
critical flaw · 30問 · 2年前xj9 - 19628 - b
xj9 - 19628 - b
30問 • 2年前xj9 - 19628 - c
xj9 - 19628 - c
critical flaw · 99問 · 1年前xj9 - 19628 - c
xj9 - 19628 - c
99問 • 1年前xj9 - 19628 - d1
xj9 - 19628 - d1
critical flaw · 99問 · 1年前xj9 - 19628 - d1
xj9 - 19628 - d1
99問 • 1年前xj9 - 19628 - d2
xj9 - 19628 - d2
critical flaw · 98問 · 1年前xj9 - 19628 - d2
xj9 - 19628 - d2
98問 • 1年前1. Shattershot
1. Shattershot
critical flaw · 50問 · 1年前1. Shattershot
1. Shattershot
50問 • 1年前Conquest Book 1
Conquest Book 1
critical flaw · 100問 · 1年前Conquest Book 1
Conquest Book 1
100問 • 1年前k3ch - 2910116 - D1 - A
k3ch - 2910116 - D1 - A
critical flaw · 100問 · 1年前k3ch - 2910116 - D1 - A
k3ch - 2910116 - D1 - A
100問 • 1年前k3ch - 2910116 - D1 - B
k3ch - 2910116 - D1 - B
critical flaw · 65問 · 1年前k3ch - 2910116 - D1 - B
k3ch - 2910116 - D1 - B
65問 • 1年前k3ch - 2910116 - D2 - A
k3ch - 2910116 - D2 - A
critical flaw · 100問 · 1年前k3ch - 2910116 - D2 - A
k3ch - 2910116 - D2 - A
100問 • 1年前k3ch - 2910116 - D2 - B
k3ch - 2910116 - D2 - B
critical flaw · 55問 · 1年前k3ch - 2910116 - D2 - B
k3ch - 2910116 - D2 - B
55問 • 1年前k3ch - 2910116 - D3 - A
k3ch - 2910116 - D3 - A
critical flaw · 100問 · 1年前k3ch - 2910116 - D3 - A
k3ch - 2910116 - D3 - A
100問 • 1年前k3ch - 2910116 - D3 - B
k3ch - 2910116 - D3 - B
critical flaw · 63問 · 1年前k3ch - 2910116 - D3 - B
k3ch - 2910116 - D3 - B
63問 • 1年前k3ch - 2910116 - D4 - A
k3ch - 2910116 - D4 - A
critical flaw · 100問 · 1年前k3ch - 2910116 - D4 - A
k3ch - 2910116 - D4 - A
100問 • 1年前1. X-Tinction Agenda
1. X-Tinction Agenda
critical flaw · 100問 · 1年前1. X-Tinction Agenda
1. X-Tinction Agenda
100問 • 1年前2. X-Tinction Agenda
2. X-Tinction Agenda
critical flaw · 100問 · 1年前2. X-Tinction Agenda
2. X-Tinction Agenda
100問 • 1年前3. X-Tinction Agenda
3. X-Tinction Agenda
critical flaw · 100問 · 1年前3. X-Tinction Agenda
3. X-Tinction Agenda
100問 • 1年前4. X-Tinction Agenda
4. X-Tinction Agenda
critical flaw · 90問 · 1年前4. X-Tinction Agenda
4. X-Tinction Agenda
90問 • 1年前Executioner's Song Book 1
Executioner's Song Book 1
critical flaw · 30問 · 1年前Executioner's Song Book 1
Executioner's Song Book 1
30問 • 1年前問題一覧
1
Opt for Multi-AZ configuration with automatic failover functionality to help mitigate failure
2
test.example.com
3
Amazon CloudFront can route to multiple origins based on the content type, Use field level encryption in Amazon CloudFront to protect sensitive data for specific content, Use an origin group with primary and secondary origins to configure Amazon CloudFront for high-availability and failover
4
Copy data from the source bucket to the destination bucket using the aws S3 sync command, Set up Amazon S3 batch replication to copy objects across Amazon S3 buckets in another Region using S3 console and then delete the replication configuration
5
Use Amazon EventBridge to decouple the system architecture
6
Use a Network Load Balancer with an Auto Scaling Group
7
Use Amazon RDS Read Replicas
8
AWS Snowball Edge Compute Optimized
9
Warm Standby
10
Use multi-part upload feature of Amazon S3
11
The Time To Live (TTL) is still in effect
12
Use Amazon Elastic Container Service (Amazon ECS) with AWS Fargate for serverless orchestration of the containerized services, Use Amazon Elastic Kubernetes Service (Amazon EKS) with AWS Fargate for serverless orchestration of the containerized services
13
The instance with the oldest launch template or launch configuration will be terminated in AZ-B
14
Use AWS CloudTrail to analyze API calls
15
Create a Golden Amazon Machine Image (AMI) with the static installation components already setup, Use Amazon EC2 user data to customize the dynamic installation parts at boot time
16
Pilot Light
17
Create an Amazon Machine Image (AMI) after installing the software and copy the AMI across all Regions. Use this Region-specific AMI to run the recovery process in the respective Regions
18
The Auto Scaling group should be configured with the minimum capacity set to 4, with 2 instances each in two different Availability Zones. The maximum capacity of the Auto Scaling group should be set to 6
19
A process replaces an existing object and immediately tries to read it. Amazon S3 always returns the latest version of the object
20
Network Load Balancer
21
Create a new launch configuration to use the correct instance type. Modify the Auto Scaling group to use this new launch configuration. Delete the old launch configuration as it is no longer needed
22
Use database cloning to create multiple clones of the production database and use each clone as a test database
23
The Auto Scaling group is using Amazon EC2 based health check and the Application Load Balancer is using ALB based health check
24
3
25
Set up Amazon Route 53 active-passive type of failover routing policy. If Amazon Route 53 health check determines the Application Load Balancer endpoint as unhealthy, the traffic will be diverted to a static error page, hosted on Amazon S3 bucket
26
Use cross-Region Read Replicas, Enable the automated backup feature of Amazon RDS in a multi-AZ deployment that creates backups across multiple Regions
27
By default, cross-zone load balancing is enabled for Application Load Balancer and disabled for Network Load Balancer
28
The CNAME record will be updated to point to the standby database
29
http://169.254.169.254/latest/meta-data/public-ipv4
30
Enable an Amazon Route 53 health check
31
http://bucket-name.s3-website-Region.amazonaws.com, http://bucket-name.s3-website.Region.amazonaws.com
32
Only Standard Amazon SQS queue is allowed as an Amazon S3 event notification destination, whereas FIFO SQS queue is not allowed
33
Handle all read operations for your application by connecting to the reader endpoint of the Amazon Aurora cluster so that Aurora can spread the load for read-only connections across the Aurora replica, Create a replica Aurora instance in another Availability Zone to improve the availability as the replica can serve as a failover target
34
Use a dead-letter queue to handle message processing failures
35
Auto Scaling group scheduled action
36
Create two Amazon SQS standard queues: one for pro and one for lite. Set up Amazon EC2 instances to prioritize polling for the pro queue over the lite queue
37
Use Amazon CloudFront signed URLs, Use Amazon CloudFront signed cookies
38
Amazon ElastiCache for Memcached
39
Any database engine level upgrade for an Amazon RDS database instance with Multi-AZ deployment triggers both the primary and standby database instances to be upgraded at the same time. This causes downtime until the upgrade is complete
40
Create an Amazon S3 Event Notification that sends a message to an Amazon SQS queue. Make the Amazon EC2 instances read from the Amazon SQS queue
41
Create an Auto-Scaling group with a desired capacity of a total of two Amazon EC2 instances across two Availability Zones. Configure an Application Load Balancer having a target group of these Amazon EC2 instances. Set up Amazon RDS MySQL DB in a multi-AZ configuration
42
Run the custom scripts as user data scripts on the Amazon EC2 instances
43
Amazon MQ
44
Create a read-replica with the same compute capacity and the same storage capacity as the primary. Point the reporting queries to run against the read replica
45
Provisioned IOPS SSD Amazon EBS volumes
46
Amazon Aurora Serverless
47
Opt for two separate AWS Direct Connect connections terminating on separate devices in more than one Direct Connect location
48
Amazon RDS applies operating system updates by performing maintenance on the standby, then promoting the standby to primary and finally performing maintenance on the old primary, which becomes the new standby, Amazon RDS automatically initiates a failover to the standby, in case primary database fails for any reason
49
Application Load Balancer + dynamic port mapping
50
Set up Amazon EBS as the Amazon EC2 instance root volume and then configure the application to use Amazon S3 as the document store