Question : An application that you are managing has EC instances and Dynamo OB tables deployed to several AWS Regions In order to monitor the performance of the application globally, you would like to see two graphs 1) Avg CPU Utilization across all EC2 instances and 2) Number of Throttled Requests for all DynamoDB tables. How can you accomplish this? 1. Tag your resources with the application name, and select the tag name as the dimension in the Cloudwatch Management console to view the respective graphs 2. Use the Cloud Watch CLI tools to pull the respective metrics from each regional endpoint Aggregate the data offline and store it for graphing in CloudWatch. 3. Access Mostly Uused Products by 50000+ Subscribers Cloud Watch for graphing. 4. Add a CloudWatch agent to each instance and attach one to each DynamoDB table. When configuring the agent set the appropriate application name and view the graphs in CloudWatch.
Correct Answer : Get Lastest Questions and Answer : Explanation: Collect from all regions, aggregate and then add to whichever region you run your primary support/monitoring from?
1, don't think that will work across region. 3, how can you put SNMP in a dynamoDB table 4, don't see how this would solve cross region problem.
Question : When assessing an organizations use of AWS API access credentials which of the following three credentials should be evaluated? Choose 3 answers A. Key pairs B. Console passwords C. Access keys D. Signing certificates E. Security Group memberships 1. A,C,D 2. B,C,D 3. Access Mostly Uused Products by 50000+ Subscribers 4. A,B,D 5. B,C,E
Explanation: AWS provides a number of authentication mechanisms including a console, account IDs and secret keys, X.509 certificates, and MFA devices to control access to AWS APIs. Console authentication is the most appropriate for administrative or manual activities, account IDs and secret keys for accessing REST-based interfaces or tools, and X.509 certificates for SOAP-based interfaces and tools. Your organization should consider the circumstances under which it will leverage access keys, x.509 certificates, console passwords, or MFA devices.
Console passwords are rarely used with AWS, majority of us are using ssh key pairs to authenticate. Not that ssh key pairs are used much with API calls but by process of elimination it sounds like a better choice.
Question : You have a Linux EC web server instance running inside a VPC. The instance is in a public subnet and has an EIP associated with it so you can connect to it over the internet via HTTP or SSH. The instance was also fully accessible when you last logged in via SSH. and was also serving web requests on port 80. Now you are not able to SSH into the host nor does it respond to web requests on port 80 that were working fine last time you checked. You have double-checked that all networking configuration parameters (security groups route tables. IGW , EIP, NACLs etc) are properly configured and you haven't made any changes to those anyway since you were last able to reach the Instance). You look at the EC2 console and notice that system status check shows "impaired." Which should be your next step in troubleshooting and attempting to get the instance back to a healthy state so that you can log in again? 1. Stop and start the instance so that it will be able to be redeployed on a healthy host system that most likely will fix the "impaired" system status 2. Reboot your instance so that the operating system will have a chance to boot in a clean healthy state that most likely will fix the 'impaired" system status 3. Access Mostly Uused Products by 50000+ Subscribers "impaired" system status. 4. Add another Elastic Network Interface to the instance and try to connect via that new path since the networking stack of the OS may be locked up causing the "impaired" system status 5. un-map and then re-map the EIP to the instance, since the IGW/NAT gateway may not be working properly, causing the "impaired" system status
Explanation: Watch this video : https://www.youtube.com/watch?v=YPf7wSEq9d0
There are two types of status checks: system status checks and instance status checks.
System Status Checks : Monitor the AWS systems required to use your instance to ensure they are working properly. These checks detect problems with your instance that require AWS involvement to repair. When a system status check fails, you can choose to wait for AWS to fix the issue, or you can resolve it yourself (for example, by stopping and starting an instance, or by terminating and replacing an instance).
The following are examples of problems that can cause system status checks to fail: Loss of network connectivity Loss of system power Software issues on the physical host Hardware issues on the physical host
Instance Status Checks : Monitor the software and network configuration of your individual instance. These checks detect problems that require your involvement to repair. When an instance status check fails, typically you will need to address the problem yourself (for example, by rebooting the instance or by making instance configuration changes). The following are examples of problems that can cause instance status checks to fail:
Failed system status checks Incorrect networking or startup configuration Exhausted memory Corrupted file system Incompatible kernel