1. Right Answer: D
Explanation: Applications must sign their API requests with AWS(Amazon Web Service) credentials. Therefore, if you are an application developer, you need a strategy for managing credentials for your applications that run on EC2 instances. For example, you can securely distribute your AWS(Amazon Web Service) credentials to the instances, enabling the applications on those instances to use your credentials to sign requests, while protecting your credentials from other users. However, it's challenging to securely distribute credentials to each instance, especially those that AWS(Amazon Web Service) creates on your behalf, such as Spot Instances or instances in Auto Scaling groups. You must also be able to update the credentials on each instance when you rotate your AWS(Amazon Web Service) credentials. IAM roles are designed so that your applications can securely make API requests from your instances, without requiring you to manage the security credentials that the applications use. Option A,C and D are invalid because using AWS(Amazon Web Service) Credentials in an application in production is a direct no recommendation for secure access For more information on IAM Roles, please visit the below URL http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html
2. Right Answer: D
Explanation: Option A is invalid because once you schedule the deletion , you cannot come back from the deletion process Option C and D are invalid because these will not check to see if the keys are being used or not The AWS(Amazon Web Service) Documentation mentions the following Deleting a customer master key (CMK) in AWS(Amazon Web Service) Key Management Service (AWS KMS) is destructive and potentially dangerous. It deletes the key material and all metadata associated with the CMK, and is irreversible. After a CMK is deleted you can no longer decrypt the data that was encrypted under that CMK, which means that data becomes unrecoverable. You should delete a CMK only when you are sure that you don't need to use it anymore. If you are not sure, consider disabling the CMK instead of deleting it. You can re-enable a disabled CMK if you need to use it again later, but you cannot recover a deleted CMK. For more information on deleting keys from KMS, please visit the below URL https://docs.aws.amazon.com/kms/latest/developerguide/deleting-keys.html
3. Right Answer: B
Explanation:
4. Right Answer: C
Explanation: Option A is invalid because the normal AWS(Amazon Web Service) Shield Service will not help in immediate action against a DDos attack. This can be done via the AWS(Amazon Web Service) Shield Advanced Service Option B is invalid because this is a logging service for VPC's traffic flow but cannot specifically protect against DDos attacks. Option D is invalid because this is a logging service for AWS(Amazon Web Service) Services but cannot specifically protect against DDos attacks. The AWS(Amazon Web Service) Documentation mentions the following AWS Shield Advanced provides enhanced protections for your applications running on Amazon EC2, Elastic Load Balancing (ELB), Amazon CloudFront and Route 53 against larger and more sophisticated attacks. AWS(Amazon Web Service) Shield Advanced is available to AWS(Amazon Web Service) Business Support and AWS(Amazon Web Service) Enterprise Support customers. AWS(Amazon Web Service) Shield Advanced protection provides always-on, flow-based monitoring of network traffic and active application monitoring to provide near real-time notifications of DDoS attacks. AWS(Amazon Web Service) Shield Advanced also gives customers highly flexible controls over attack mitigations to take actions instantly. Customers can also engage the DDoS Response Team (DRT) 24X7 to manage and mitigate their application layer DDoS attacks. For more information on AWS(Amazon Web Service) Shield, please visit the below URL https://aws.amazon.com/shield/faqs/
5. Right Answer: A,C
Explanation:
Leave a comment