Amazon Web Services Related Exams
DOP-C02 Exam
A company is optimizing its AWS costs. Most of the company’s AWS spend is for Amazon EC2. When the company analyzes its EC2 usage metrics in Amazon CloudWatch, the company observes that most of its EC2 instances are in an idle state.
The company considers an instance idle if it has a maximum CPU utilization of less than 2% in the previous 24 hours. The company evaluates metrics for instances based on 1-hour intervals. The company decides to configure a CloudWatch alarm for each EC2 instance in the account. The company wants the alarm to activate when an instance is idle.
How should the company configure the CloudWatch alarm?
A company has deployed a new platform that runs on Amazon Elastic Kubernetes Service (Amazon EKS). The new platform hosts web applications that users frequently update. The application developers build the Docker images for the applications and deploy the Docker images manually to the platform.
The platform usage has increased to more than 500 users every day. Frequent updates, building the updated Docker images for the applications, and deploying the Docker images on the platform manually have all become difficult to manage.
The company needs to receive an Amazon Simple Notification Service (Amazon SNS) notification if Docker image scanning returns any HIGH or CRITICAL findings for operating system or programming language package vulnerabilities.
Which combination of steps will meet these requirements? (Select TWO.)
A company is testing a web application that runs on Amazon EC2 instances behind an Application Load Balancer. The instances run in an Auto Scaling group across multiple Availability Zones. The company uses a blue green deployment process with immutable instances when deploying new software.
During testing users are being automatically logged out of the application at random times. Testers also report that when a new version of the application is deployed all users are logged out. The development team needs a solution to ensure users remain logged m across scaling events and application deployments.
What is the MOST operationally efficient way to ensure users remain logged in?