1. Right Answer: A,C
Explanation:
2. Right Answer: C
Explanation: The Cost & Usage Report is your one-stop-shop for accessing the most granular data about your AWS costs and usage. You can also load your cost and usage information into Amazon Athena, Amazon Redshift, AWS QuickSight, or a tool of your choice.https://aws.amazon.com/aws-cost-management/
3. Right Answer: E
Explanation:
4. Right Answer: B
Explanation: Loose coupling between services can also be done through asynchronous integration. It involves one component that generates events and another that consumes them. The two components do not integrate through direct point-to-point interaction, but usually through an intermediate durable storage layer. This approach decouples the two components and introduces additional resiliency. So, for example, if a process that is reading messages from the queue fails, messages can still be added to the queue to be processed when the system recovers.https://www.botmetric.com/blog/aws-cloud-architecture-design-principles/
5. Right Answer: B,E
Explanation: If you decided to create service accounts (that is, accounts used for programmatic access by applications running outside of the AWS environment) and generate access keys for them, you should create a dedicated service account for each use case. This will allow you to restrict the associated policy to only the permissions needed for the particular use case, limiting the blast radius if the credentials are compromised. For example, if a monitoring tool and a release management tool both require access to your AWS environment, create two separate service accounts with two separate policies that define the minimum set of permissions for each tool.https://aws.amazon.com/blogs/security/guidelines-for-protecting-your-aws-account-while-usingprogrammatic-access/
Leave a comment