chapter 6

Question 1

When do you use the AWS Management Console versus the AWS CLI?

Answer 1

AWS Management Console - required if you want to use the point-and-click interface and want to view visual elements such as CloudWatch graphs or Cost Explorer graphs.
AWS CLI - to manage your AWS resources manually from the command
line or using scripts. It’s good for repetitive or bulk tasks that would take a long time using the Web.

Question 2

How do you use resource tags and resource groups?

Answer 2

You can use tags to label your resources according to whatever you like
You can group resources into a resource group according to resource tags or CloudFormation stacks.

Question 3

What are some use case for CloudWatch?

Answer 3

To collect logs and metrics from AWS and non-AWS services.
To create alarms to trigger when a metric falls above or below a threshold. In response to an alarm, you can send a notification using SNS, or you can take an action using an Auto Scaling action or EC2 action.
Aggregate and search log files.
Take actions in response to specific events that occur with your AWS resources,

Question 4

What are the options for developing applications that integrate with AWS?

Answer 4

SDKs for a variety of programming languages and platforms.
HTTPS-based AWS Query API that you can interface with directly, the SDKs handle the heavy lifting of request authentication, serialization, and connection management, freeing you up to write your application without having to learn the nitty-gritty API details of every AWS service you want to use.

Question 5

What does CloudTrail do and how does it differ from and integrates with
CloudWatch?

Answer 5

CloudTrail logs management and data operations on your account.
You can optionally stream CloudTrail logs to CloudWatch for storage,
searching, and analysis.