Amazon Web Services SCS-C01 Based on Real Exam Environment

One of the articles from IAM mentions what should be done in such a scenario

If you suspect that your account has been compromised, or if you have received a notification from IAM that the account has been compromised, perform the following tasks:

Change your IAM root account password and the passwords of any IAM users.

Delete or rotate all root and IAM Identity and Access Management (IAM) access keys.

Delete any resources on your account you didn't create, especially running EC2 instances, EC2 spot bids, or IAM users.

Respond to any notifications you received from IAM Support through the IAM Support Center.

Option C is invalid because there could be compromised instances or resources running on your environment. They should be shutdown or stopped immediately.

For more information on the article, please visit the below URL:

https://IAM.amazon.com/premiumsupport/knowledee-center/potential-account-compromise >

The correct answers are: Change the root account password. Rotate all IAM access keys. Change the password for all IAM users. Submit your Feedback/Queries to our Experts

You can use the IAMConfig history to see the history of a particular item.

The below snapshot shows an example configuration for a user in IAM Config

C:\Users\wk\Desktop\mudassar\Untitled.jpg

Option B,C and D are all invalid because these services cannot be used to see the history of a particular configuration item. This can only be accomplished by IAM Config.

For more information on tracking changes in IAM Config, please visit the below URL:

https://docs.IAM.amazon.com/AmazonCloudFront/latest/DeveloperGuide/TrackineChanees.htmll

The correct answer is: Use IAM Config to examine the employee's IAM permissions prior to the incident and compare them the employee's current IAM permissions.

Submit your Feedback/Queries to our Experts

The IAM Documentation mentions the following

Key pairs consist of a public key and a private key. You use the private key to create a digital signature, and then IAM uses the corresponding public key to validate the signature. Key pairs are used only for Amazon EC2 and Amazon CloudFront.

Option A.C and D are all wrong because these are not used to log into EC2 Linux Instances

For more information on IAM Security credentials, please visit the below URL:

https://docs.IAM.amazon.com/eeneral/latest/er/IAM-sec-cred-types.html

The correct answer is: Key pairs

Submit your Feedback/Queries to our Experts

Your answer is incorrect

Answer-A

Such a scenario is also given in the IAM Documentation Cross-Origin Resource Sharing: Use-case Scenarios

The following are example scenarios for using CORS:

• Scenario 1: Suppose that you are hosting a website in an Amazon S3 bucket named website as described in Hosting a Static Website on Amazon S3. Your users load the website endpoint http://website.s3-website-us-east-1 .amazonIAM.com. Now you want to use JavaScript on the webpages that are stored in this bucket to be able to make authenticated GET and PUT requests against the same bucket by using the Amazon S3 API endpoint for the bucket website.s3.amazonIAM.com. A browser would normally block JavaScript from allowing those requests, but with CORS you can configure your bucket to explicitly enable cross-origin requests from website.s3-website-us-east-1 .amazonIAM.com.

• Scenario 2: Suppose that you want to host a web font from your S3 bucket. Again, browsers require a CORS check (also called a preflight check) for loading web fonts. You would configure the bucket that is hosting the web font to allow any origin to make these requests.

Option Bis invalid because versioning is only to create multiple versions of an object and can help in accidental deletion of objects

Option C is invalid because this is used as an extra measure of caution for deletion of objects

Option D is invalid because this is used for Cross region replication of objects

For more information on Cross Origin Resource sharing, please visit the following URL

• ittps://docs.IAM.amazon.com/AmazonS3/latest/dev/cors.html

The correct answer is: Enable CORS for the bucket

Submit your Feedback/Queries to our Experts