1. Right Answer: B,D
Explanation: The below example policy from the AWS(Amazon Web Service) Documentation is required to be given to the EC2 Instance in order to read a secure string from AWS(Amazon Web Service) KMS. Permissions need to be given to the Get Parameter API and the KMS API call to decrypt the secret. { 'Version': '2012-10-17', 'Statement': [ { 'Effect': 'Allow', 'Action': [ 'ssm:GetParameter*' ], 'Resource': 'arn:aws:ssm:us-west-2:111122223333:/parameter/ReadableParameters/*' }, { 'Effect': 'Allow', 'Action': [ 'kms:Decrypt' ], 'Resource': 'arn:aws:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab' } ] } Option A is invalid because roles can be attached to EC2 and not EC2 roles to SSM Option B is invalid because the KMS key does not need to decrypt the SSM service role. Option E is invalid because this configuration is valid For more information on the parameter store, please visit the below URL https://docs.aws.amazon.com/kms/latest/developerguide/services-parameter-store.html
2. Right Answer: A
Explanation: Use the Systems Manger Patch Manger to generate the report and also install the missing patches The AWS(Amazon Web Service) Documentation mentions the following AWS Systems Manager Patch Manager automates the process of patching managed instances with security-related updates. For Linux-based instances, you can also install patches for non-security updates. You can patch fleets of Amazon EC2 instances or your on-premises servers and virtual machines (VMs) by operating system type. This includes supported versions of Windows, Ubuntu Server, Red Hat Enterprise Linux (RHEL), SUSE Linux Enterprise Server (SLES), and Amazon Linux. You can scan instances to see only a report of missing patches, or you can scan and automatically install all missing patches. Option A is invalid because Amazon QuickSight and Cloud Trail cannot be used to generate the list of servers that don't meet compliance needs. Option C is wrong because deploying instances via new AMI's would impact the applications hosted on these servers Option D is invalid because Amazon Trusted Advisor cannot be used to generate the list of servers that don't meet compliance needs. For more information on the AWS(Amazon Web Service) Patch Manager, please visit the below URL https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-patch.html
3. Right Answer: A
Explanation: When you define access to objects in a bucket, you need to ensure that you specify to which objects in the bucket access needs to be given to. In this case , the * can be used to assign the permission to all objects in the bucket. Option A is invalid because the right permissions are already provided as per the question requirement Option B is invalid because it is not necessary that the policy has the same name as the bucket Option D is invalid because this should be the default flow for applying the policy For more information on bucket policies please visit the below URL https://docs.aws.amazon.com/AmazonS3/latest/dev/example-bucket-policies.html
4. Right Answer: B
Explanation: Sometimes companies want to have custom solutions in place for monitoring Intrusions to their systems. In such a case , you can use the AWS(Amazon Web Service) Marketplace for looking at custom solutions. Option A,C and D are all invalid because they cannot be used to conduct intrusion detection or prevention For more information on using custom security solutions please visit the below URL https://d1.awsstatic.com/Marketplace/security/AWSMP_Security_Solution%20Overview.pdf
5. Right Answer: D
Explanation: In the test environment, the security groups might have been opened to all IP addresses for testing purpose. Always to ensure to remove this rule once all testing is completed. Option A , C and D are all invalid because this would affect the application running on the server. The easiest way is just to remove the rule for access on port 22. For more information on authorizing access to an instance, please visit the below URL https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html
Leave a comment