A company has multiple member accounts that are part of an organization in AWS Organizations. The security team needs to review every Amazon EC2 security group and their inbound and outbound rules. The security team wants to programmatically retrieve this information from the member accounts using an AWS Lambda function in the management account of the organization.
Which combination of access changes will meet these requirements? (Choose three.)
https://aws.amazon.com/premiumsupport/knowledge-center/lambda-function-assume-iam-role/ https://kreuzwerker.de/post/aws-multi-account-setups-reloaded
A DevOps team manages infrastructure for an application. The application uses long-running processes to process items from an Amazon Simple Queue Service (Amazon SQS) queue. The application is deployed to an Auto Scaling group.
The application recently experienced an issue where items were taking significantly longer to process. The queue exceeded the expected size, which prevented various business processes from functioning properly. The application records all logs to a third-party tool.
The team is currently subscribed to an Amazon Simple Notification Service (Amazon SNS) topic that the team uses for alerts. The team needs to be alerted if the queue exceeds the expected size.
Which solution will meet these requirements with the MOST operational efficiency?
Comprehensive and Detailed Explanation From Exact Extract:
The Amazon SQS service publishes several standard CloudWatch metrics by default, including ApproximateNumberOfMessagesVisible, which represents the number of messages available for retrieval from the queue (i.e., the number of messages waiting to be processed). This is the primary metric to monitor queue backlog and processing delays.
Using ApproximateNumberOfMessagesVisible to monitor the visible messages in the queue gives a direct and near real-time indication of processing delays or backlog.
CloudWatch metrics are automatically collected and available without the need to create custom metrics or Lambda functions, which increases operational efficiency by reducing complexity and maintenance overhead.
Setting a CloudWatch alarm on this metric with a static threshold and a reasonable evaluation period (such as 1 hour) is sufficient to alert the team when the queue grows beyond an expected size.
The alarm can be directly configured to send notifications to an existing SNS topic, maintaining seamless integration with the team's alerting mechanisms.
The ApproximateNumberOfMessagesDelayed metric refers to messages that are delayed and not available for processing yet due to delay settings, which is not the direct backlog that causes business process delays.
Options C and D introduce unnecessary complexity by requiring Lambda functions and custom metrics or scheduled invocations, which reduce operational efficiency compared to using built-in CloudWatch metrics and alarms.
Reference from AWS Official Documentation and Study Guide:
Amazon SQS Monitoring with CloudWatch Metrics:
'Amazon SQS automatically sends metrics to CloudWatch, including ApproximateNumberOfMessagesVisible, which shows the number of messages available for retrieval.'
(Source: Amazon SQS Monitoring - AWS Documentation)
Setting CloudWatch Alarms for SQS Queues:
'You can create CloudWatch alarms on SQS metrics such as ApproximateNumberOfMessagesVisible to receive notifications when the queue size exceeds a threshold.'
(Source: Amazon CloudWatch Alarms - AWS Documentation)
AWS DevOps Engineer Professional Exam Guide:
'Efficient alerting for queue backlogs should leverage native CloudWatch metrics to minimize operational overhead.'
(Source: Official AWS Certified DevOps Engineer Professional Study Guide)
A company has an application that runs on Amazon EC2 instances behind an Application Load Balancer (ALB) The EC2 Instances are in multiple Availability Zones The application was misconfigured in a single Availability Zone, which caused a partial outage of the application.
A DevOps engineer made changes to ensure that the unhealthy EC2 instances in one Availability Zone do not affect the healthy EC2 instances in the other Availability Zones. The DevOps engineer needs to test the application's failover and shift where the ALB sends traffic During failover. the ALB must avoid sending traffic to the Availability Zone where the failure has occurred.
Which solution will meet these requirements?
* Turn off cross-zone load balancing on the ALB's target group:
Cross-zone load balancing distributes traffic evenly across all registered targets in all enabled Availability Zones. Turning this off will ensure that each target group only handles requests from its respective Availability Zone.
To disable cross-zone load balancing:
Go to the Amazon EC2 console.
Navigate to Load Balancers and select the ALB.
Choose the Target Groups tab, select the target group, and then select the Group details tab.
Click on Edit and turn off Cross-zone load balancing.
* Use Amazon Route 53 Application Recovery Controller to start a zonal shift away from the Availability Zone:
Amazon Route 53 Application Recovery Controller provides the ability to control traffic flow to ensure high availability and disaster recovery.
By using Route 53 Application Recovery Controller, you can perform a zonal shift to redirect traffic away from the unhealthy Availability Zone.
To start a zonal shift:
Configure Route 53 Application Recovery Controller by creating a cluster and control panel.
Create routing controls to manage traffic shifts between Availability Zones.
Use the routing control to shift traffic away from the affected Availability Zone.
A company must encrypt all AMIs that the company shares across accounts. A DevOps engineer has access to a source account where an unencrypted custom AMI has been built. The DevOps engineer also has access to a target account where an Amazon EC2 Auto Scaling group will launch EC2 instances from the AMI. The DevOps engineer must share the AMI with the target account.
The company has created an AWS Key Management Service (AWS KMS) key in the source account.
Which additional steps should the DevOps engineer perform to meet the requirements? (Choose three.)
The Auto Scaling group service-linked role must have a specific grant in the source account in order to decrypt the encrypted AMI. This is because the service-linked role does not have permissions to assume the default IAM role in the source account.
The following steps are required to meet the requirements:
In the source account, copy the unencrypted AMI to an encrypted AMI. Specify the KMS key in the copy action.
In the source account, create a KMS grant that delegates permissions to the Auto Scaling group service-linked role in the target account.
In the source account, share the encrypted AMI with the target account.
In the target account, attach the KMS grant to the Auto Scaling group service-linked role.
The first three steps are the same as the steps that I described earlier. The fourth step is required to grant the Auto Scaling group service-linked role permissions to decrypt the AMI in the target account.
A company manages a web application that runs on Amazon EC2 instances behind an Application Load Balancer (ALB). The EC2 instances run in an Auto Scaling group across multiple Availability Zones. The application uses an Amazon RDS for MySQL DB instance to store the dat
a. The company has configured Amazon Route 53 with an alias record that points to the ALB.
A new company guideline requires a geographically isolated disaster recovery (DR> site with an RTO of 4 hours and an RPO of 15 minutes.
Which DR strategy will meet these requirements with the LEAST change to the application stack?
Lenna
3 days agoDeeanna
11 days agoIola
18 days agoBarabara
26 days agoLashanda
1 month agoRosio
1 month agoAvery
2 months agoLynsey
2 months agoLuann
2 months agoArthur
2 months agoNoel
3 months agoGeoffrey
3 months agoJanella
3 months agoDell
3 months agoTequila
4 months agoAnglea
4 months agoShawna
4 months agoSonia
5 months agoKing
5 months agoKathrine
5 months agoElke
5 months agoTheron
6 months agoDenise
6 months agoGrover
8 months agoBeckie
9 months agoAlyce
10 months agoMelissia
11 months agoHaydee
1 year agoTruman
1 year agoNida
1 year agoArlean
1 year agoFelicidad
1 year agoSophia
1 year agoGeorgeanna
1 year agoIluminada
1 year agoMariann
1 year agoShelia
1 year agoHoney
1 year agoAshlyn
1 year agoKanisha
1 year agoMireya
1 year agoTyisha
1 year agoCasie
1 year agoCheryl
2 years agoLon
2 years agoEmeline
2 years agoElmer
2 years agoJustine
2 years agoJosefa
2 years agoVernice
2 years agoMilly
2 years agoCherilyn
2 years agoHerman
2 years ago