1. Right Answer: D
Explanation: The AWS(Amazon Web Service) Documentation mentions the following as a best practise for IAM users For extra security, enable multi-factor authentication (MFA) for privileged IAM users (users who are allowed access to sensitive resources or APIs). With MFA, users have a device that generates a unique authentication code (a one-time password, or OTP). Users must provide both their normal credentials (like their user name and password) and the OTP. The MFA device can either be a special piece of hardware, or it can be a virtual device (for example, it can run in an app on a smartphone). Option B,C and D are invalid because no such security options are available in AWS For more information on IAM best practises, please visit the below URL ttps://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html
2. Right Answer: A
Explanation:
3. Right Answer: C
Explanation: A year's time is generally too long a gap for conducting security audits The AWS(Amazon Web Service) Documentation mentions the following You should audit your security configuration in the following situations: On a periodic basis. If there are changes in your organization, such as people leaving. If you have stopped using one or more individual AWS(Amazon Web Service) services. This is important for removing permissions that users in your account no longer need. If you've added or removed software in your accounts, such as applications on Amazon EC2 instances, AWS(Amazon Web Service) OpsWorks stacks, AWS(Amazon Web Service) CloudFormation templates, etc. If you ever suspect that an unauthorized person might have accessed your account. Option B , C and D are all the right ways and recommended best practises when it comes to conducting audits For more information on Security Audit guideline, please visit the below URL https://docs.aws.amazon.com/general/latest/gr/aws-security-audit-guide.html
4. Right Answer: B
Explanation: The AWS(Amazon Web Service) Documentation gives an example on such a case Inline policies are useful if you want to maintain a strict one-to-one relationship between a policy and the principal entity that it's applied to. For example, you want to be sure that the permissions in a policy are not inadvertently assigned to a principal entity other than the one they're intended for. When you use an inline policy, the permissions in the policy cannot be inadvertently attached to the wrong principal entity. In addition, when you use the AWS(Amazon Web Service) Management Console to delete that principal entity, the policies embedded in the principal entity are deleted as well. That's because they are part of the principal entity. Option A is invalid because AWS(Amazon Web Service) Managed Polices are ok for a group of users , but for individual users , inline policies are better. Option C and D are invalid because they are specifically meant for access to S3 buckets For more information on policies, please visit the following url https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html
5. Right Answer: A
Explanation:
Write a public review