問題一覧
1
The AWS Lambda function is timing out
2
Amazon ElastiCache for Redis
3
Amazon Simple Queue Service (Amazon SQS)
4
Set up an on-premises file gateway. Configure data sources to write the .json files to the file gateway. Point the legacy analytics application to the file gateway. The file gateway should replicate the .json files to Amazon S3
5
Partition placement groups
6
Deploy Amazon EC2 instances in a cluster placement group, Deploy Amazon EC2 instances with Elastic Fabric Adapter (EFA)
7
Amazon Simple Queue Service (Amazon SQS) temporary queues
8
As the resources are unbalanced in the Availability Zones, Amazon EC2 Auto Scaling will compensate by rebalancing the Availability Zones. When rebalancing, Amazon EC2 Auto Scaling launches new instances before terminating the old ones, so that rebalancing does not compromise the performance or availability of your application, Amazon EC2 Auto Scaling creates a new scaling activity for terminating the unhealthy instance and then terminates it. Later, another scaling activity launches a new instance to replace the terminated instance
9
Set up Amazon Kinesis Data Streams to ingest the data, Set up AWS Fargate with Amazon ECS to process the data
10
If you create an Amazon Machine Image (AMI) from an instance, the data on its instance store volumes isn't preserved, You can't detach an instance store volume from one instance and attach it to a different instance
11
AWS Glue
12
Create an application that will traverse the S3 bucket, issue a Byte Range Fetch for the first 250 bytes, and store that information in Amazon RDS
13
Create a public Network Load Balancer that links to Amazon EC2 instances that are bastion hosts managed by an Auto Scaling Group
14
Convert the gp2 volume to an io1
15
Use Amazon EFS with Provisioned Throughput mode
16
Amazon Redshift
17
Business, Enterprise, Developer
18
Availability is related to accessing the data at a point in time and durability is related to the existence of the data whether accessible or not
19
Automated backups and automated snapshots
20
Implement EBS-optimized instances
21
Copy the AMI from us-west-2, manually apply launch permissions, user-defined tags, and Amazon S3 bucket permissions of the default AMI to the new instance, and launch the instance.
22
Hosted zone
23
CloudWatch
24
Instance store
25
Provisioned IOPS SSD
26
Gateway-Stored
27
Snapshots
28
Ensure that “Source/Destination Checks” is disabled on the NAT instance.
29
Snowball
30
Use Amazon SQS to decouple the application components and keep the requests in queue until the extra Auto Scaling instances are available.
31
Auto Scaling
32
Performance will be degraded
33
Simple routing
34
Microsoft SQL Server RDS databases
35
28
36
4 GiB
37
The instance in AZ -C that has the oldest launch configuration will terminate first.
38
The proxy server is on an inadequately sized EC2 instance and does not have sufficient network throughput to handle all updates simultaneously. You should increase the instance size of the EC2 instance for the proxy server., The proxy server is in a private subnet and uses a NAT gateway instance to connect to the Internet. However, this instance is too small to handle the required network traffic. You should re-provision the NAT gateway instance so that it’s able to handle the throughput.
39
0
40
Use NFSv4.1
41
AWS reserves both the first four and the last IP address in each subnet’s CIDR block., Your Auto Scaling group (ASG) has provisioned too many EC2 instances and has exhausted the number of internal IP addresses available in the subnet.
42
JSON
43
RDS, ElastiCache, DynamoDB
44
Read replicas are accessed the same as any other database in RDS
45
Cold HDD
46
Spread the instances over multiple AZs to minimize the traffic concentration and maximize the fault tolerance.
47
Large file sizes because the time to access the file location is the same regardless of file size
48
Resources are in multiple Availability Zones
49
Kinesis Firehose
50
Aurora
51
CPU credits
52
For development and test servers
53
Route 53, Identity Access Management roles
54
Redis and memcached
55
The throughput is not balanced across your partitions. One partition is being subjected to a disproportionate amount of the traffic and is therefore exceeding the limits.
56
Private AMI
57
During times of normally low write IOPS
58
High I/O instances
59
Tune SQL queries
60
Set up a read replica of your production environment in the Asia Pacific region and configure latency-based routing on Route 53., Use ElastiCache to cache the most commonly accessed DB queries., Set up CloudFront with dynamic content support to enable the caching of reusable content from the media-rich website.
61
In different Availability Zones
62
DAX
63
Performance
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 - 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
The AWS Lambda function is timing out
2
Amazon ElastiCache for Redis
3
Amazon Simple Queue Service (Amazon SQS)
4
Set up an on-premises file gateway. Configure data sources to write the .json files to the file gateway. Point the legacy analytics application to the file gateway. The file gateway should replicate the .json files to Amazon S3
5
Partition placement groups
6
Deploy Amazon EC2 instances in a cluster placement group, Deploy Amazon EC2 instances with Elastic Fabric Adapter (EFA)
7
Amazon Simple Queue Service (Amazon SQS) temporary queues
8
As the resources are unbalanced in the Availability Zones, Amazon EC2 Auto Scaling will compensate by rebalancing the Availability Zones. When rebalancing, Amazon EC2 Auto Scaling launches new instances before terminating the old ones, so that rebalancing does not compromise the performance or availability of your application, Amazon EC2 Auto Scaling creates a new scaling activity for terminating the unhealthy instance and then terminates it. Later, another scaling activity launches a new instance to replace the terminated instance
9
Set up Amazon Kinesis Data Streams to ingest the data, Set up AWS Fargate with Amazon ECS to process the data
10
If you create an Amazon Machine Image (AMI) from an instance, the data on its instance store volumes isn't preserved, You can't detach an instance store volume from one instance and attach it to a different instance
11
AWS Glue
12
Create an application that will traverse the S3 bucket, issue a Byte Range Fetch for the first 250 bytes, and store that information in Amazon RDS
13
Create a public Network Load Balancer that links to Amazon EC2 instances that are bastion hosts managed by an Auto Scaling Group
14
Convert the gp2 volume to an io1
15
Use Amazon EFS with Provisioned Throughput mode
16
Amazon Redshift
17
Business, Enterprise, Developer
18
Availability is related to accessing the data at a point in time and durability is related to the existence of the data whether accessible or not
19
Automated backups and automated snapshots
20
Implement EBS-optimized instances
21
Copy the AMI from us-west-2, manually apply launch permissions, user-defined tags, and Amazon S3 bucket permissions of the default AMI to the new instance, and launch the instance.
22
Hosted zone
23
CloudWatch
24
Instance store
25
Provisioned IOPS SSD
26
Gateway-Stored
27
Snapshots
28
Ensure that “Source/Destination Checks” is disabled on the NAT instance.
29
Snowball
30
Use Amazon SQS to decouple the application components and keep the requests in queue until the extra Auto Scaling instances are available.
31
Auto Scaling
32
Performance will be degraded
33
Simple routing
34
Microsoft SQL Server RDS databases
35
28
36
4 GiB
37
The instance in AZ -C that has the oldest launch configuration will terminate first.
38
The proxy server is on an inadequately sized EC2 instance and does not have sufficient network throughput to handle all updates simultaneously. You should increase the instance size of the EC2 instance for the proxy server., The proxy server is in a private subnet and uses a NAT gateway instance to connect to the Internet. However, this instance is too small to handle the required network traffic. You should re-provision the NAT gateway instance so that it’s able to handle the throughput.
39
0
40
Use NFSv4.1
41
AWS reserves both the first four and the last IP address in each subnet’s CIDR block., Your Auto Scaling group (ASG) has provisioned too many EC2 instances and has exhausted the number of internal IP addresses available in the subnet.
42
JSON
43
RDS, ElastiCache, DynamoDB
44
Read replicas are accessed the same as any other database in RDS
45
Cold HDD
46
Spread the instances over multiple AZs to minimize the traffic concentration and maximize the fault tolerance.
47
Large file sizes because the time to access the file location is the same regardless of file size
48
Resources are in multiple Availability Zones
49
Kinesis Firehose
50
Aurora
51
CPU credits
52
For development and test servers
53
Route 53, Identity Access Management roles
54
Redis and memcached
55
The throughput is not balanced across your partitions. One partition is being subjected to a disproportionate amount of the traffic and is therefore exceeding the limits.
56
Private AMI
57
During times of normally low write IOPS
58
High I/O instances
59
Tune SQL queries
60
Set up a read replica of your production environment in the Asia Pacific region and configure latency-based routing on Route 53., Use ElastiCache to cache the most commonly accessed DB queries., Set up CloudFront with dynamic content support to enable the caching of reusable content from the media-rich website.
61
In different Availability Zones
62
DAX
63
Performance