A company runs hundreds of Amazon EC2 instances in a single AWS Region. Each EC2 instance has two attached 1 GiB General Purpose SSD (gp2) Amazon Elastic Block Store (Amazon EBS) volumes. A critical workload is using all the available IOPS capacity on the EBS volumes.
According to company policy, the company cannot change instance types or EBS volume types without completing lengthy acceptance tests to validate that the company's applications will function properly. A SysOps administrator needs to increase the I/O performance of the EBS volumes as quickly as possible.
Which action should the SysOps administrator take to meet these requirements?
Increasing the size of the 1 GiB EBS volumes will increase the IOPS capacity of the volumes, which will improve the I/O performance of the EBS volumes. This option does not require any changes to the instance types or EBS volume types, so it can be done quickly without the need for lengthy acceptance tests to validate that the company's applications will function properly.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/requesting-ebs-volume-modifications.html
The company wants to improve the security and high availability of a two-tier web application that was rehosted to AWS, currently in a single Availability Zone.
Options (Select TWO):
To improve security and availability, the best approach is to configure Multi-AZ for both the web and database tiers.
Multi-AZ Auto Scaling for Web Tier: Deploying the web-tier instances in an Auto Scaling group across multiple AZs with an internet-facing ALB provides high availability and fault tolerance.
RDS Multi-AZ for SQL Server: Migrating the SQL Server to RDS with Multi-AZ deployment ensures database redundancy and failover without additional management overhead.
Placing the web tier in multiple Regions would add unnecessary complexity, and migrating the database to DynamoDB is not suitable for applications requiring SQL Server's relational capabilities.
A company requires that all activity in its AWS account be logged using AWS CloudTrail. Additionally, a SysOps administrator must know when CloudTrail log files are modified or deleted.
How should the SysOps administrator meet these requirements?
CloudTrail Log File Integrity Validation:
AWS CloudTrail provides a feature for log file integrity validation to ensure logs have not been modified or deleted.
Steps to Enable and Validate:
Enable Log File Integrity Validation:
Go to the CloudTrail Console.
Select or create a trail.
In the trail settings, enable Log file validation.
Use the AWS CLI for Validation:
Use the following CLI command:
aws cloudtrail validate-logs --trail-name <trail-name>
This command validates the digest files generated by CloudTrail against the log files.
Why Other Options Are Incorrect:
B: Using the AWS CloudTrail Processing Library is unnecessary for validation.
C: CloudTrail Insights is designed to identify unusual activity, not monitor log modifications.
D: Amazon CloudWatch Logs cannot directly monitor CloudTrail logs for integrity.
A company observes that a newly created Amazon CloudWatch alarm is not transitioning out of the INSUFFICIENT_DATA state. The alarm was created to track the mem_used_percent metric from an Amazon EC2 instance that is deployed in a public subnet.
A review of the EC2 instance shows that the unified CloudWatch agent is installed and is running. However, the metric is not available in CloudWatch. A SysOps administrator needs to implement a solution to resolve this problem
Which solution will meet these requirements?
Objective:
Ensure the mem_used_percent metric from the EC2 instance is available in Amazon CloudWatch.
Root Cause:
The unified CloudWatch agent requires IAM permissions to publish custom metrics to CloudWatch.
If an IAM instance profile is not attached or is missing necessary permissions, the metric will not appear in CloudWatch.
Solution Implementation:
Step 1: Create an IAM role with the required permissions:
Use the AmazonCloudWatchAgentServerPolicy managed policy, which grants permissions for the CloudWatch agent to send metrics.
Step 2: Create an IAM instance profile for the role.
Step 3: Attach the instance profile to the EC2 instance.
Step 4: Restart the unified CloudWatch agent on the EC2 instance to apply the changes:
bash
Copy code
sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a stop
sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a start
AWS Reference:
Unified CloudWatch Agent Configuration: CloudWatch Agent Permissions
Why Other Options Are Incorrect:
Option A: Enabling detailed monitoring only collects predefined metrics; it does not affect custom metrics like mem_used_percent.
Option C: The subnet (public or private) does not affect the collection of metrics by the CloudWatch agent.
Option D: Using IAM user credentials is not a best practice for EC2 instances; instance profiles are the recommended method.
A company runs a multi-tier web application with two Amazon EC2 instances in one Availability Zone in the us-east-1 Region. A SysOps administrator must migrate one of the EC2 instances to a new Availability Zone
Which solution will accomplish this?
Amazon EC2 and Availability Zones:
EC2 instances are tied to a specific Availability Zone within a region. Moving an instance directly is not possible.
Creating an Amazon Machine Image (AMI) allows the instance to be recreated in another Availability Zone.
Steps to Migrate an EC2 Instance to a New Availability Zone:
Create an AMI:
Open the EC2 Console.
Select the EC2 instance you want to migrate.
Choose Actions > Image and templates > Create Image.
Configure the AMI creation settings and create the image.
Launch a New Instance:
Navigate to the AMI section in the EC2 Console.
Select the newly created AMI.
Click Launch Instance from Image.
Specify the new Availability Zone during the instance configuration.
Terminate the Original Instance:
After validating that the new instance is functioning correctly, terminate the original instance to avoid additional costs.
Why Other Options Are Incorrect:
A: Directly copying an instance to another AZ is not supported.
C: There is no AWS CLI command to move an EC2 instance between AZs.
D: Stopping and modifying the AZ of an existing instance is not possible.
Lennie
5 days agoNaomi
1 months agoKendra
1 months agoVi
2 months agoLyndia
2 months agoArthur
2 months agoCristy
3 months agoBernardine
3 months agoColton
3 months agoSol
3 months agoKiera
4 months agoKerry
4 months agoPete
4 months agoTheodora
5 months agoTaryn
5 months agoAnjelica
5 months agoAngella
5 months agoDion
5 months agoDwight
6 months agoFlo
6 months agoKris
6 months agoKindra
6 months agoHollis
6 months agoMelissa
7 months agoBrock
7 months agoLavonda
7 months agoCyndy
7 months agoMelinda
7 months agoOmer
8 months agoBrendan
8 months agoInes
8 months agoIra
8 months agoCornell
9 months agoJoanna
10 months agoMaricela
10 months agoElliott
11 months agoKenneth
11 months agoDorian
1 years ago