Which AWS service helps you understand how your AWS resources are performing and whether they can handle the load you're throwing at them?

• AWS Config

• CloudTrail

• CloudWatch

• AWS Security

What can tracking performance over time help you identify in your AWS resources?

• User permissions

• Spikes in usage

• Security breaches

• Logging events

What might the words 'exception' or 'warning' in a log indicate when detecting application problems?

• Successful performance

• User access issues

• A data corruption or timeout

• An inventory of AWS resources

What is the purpose of auditing user permissions in AWS?

• To maintain an inventory of AWS resources

• To track performance

• To reduce risk and improve security posture

• To log every single action

Why is logging every single action that occurs against your AWS resources important?

• To understand existing resources

• To prevent future problems

• To track user permissions

• To handle the load on resources

What is the benefit of maintaining an inventory of AWS Resources?

• To identify spikes in usage

• To predict how proposed changes will impact the current environment

• To detect application problems

• To track performance

What is the purpose of AWS CloudTrail?

• It collects numeric performance metrics from AWS resources.

• It provides a detailed log of every read or write action that occurs against your AWS resources.

• It configures how your AWS resources are configured and how they change over time.

• It automatically adjusts AWS resource levels to meet demand.

Which AWS service collects numeric performance metrics from AWS and non-AWS resources?

• AWS Config

• AWS CloudTrail

• CloudWatch

• AWS Management Console

What can AWS Config do when a resource falls out of compliance with a baseline that you define?

• It can delete the resource.

• It can ignore the non-compliance.

• It can alert you.

• It can perform automatic action in response to events.

What are management events in AWS CloudTrail?

• They are detailed logs of security breaches.

• They are operations that a principal executes against an AWS resource.

• They are automatic adjustments of AWS resource levels.

• They are logs of non-API actions only.