Correct Answer : 1 CloudTrail log files contain one or more log entries where each entry is made up of multiple JSON-formatted events. A log entry represents a single request from any source and includes information about the requested action, any parameters, the date and time of the action, and so on. The log entries are not guaranteed to be in any particular order. That is, they are not an ordered stack trace of the public API calls. Every log entry contains information about who generated the request. The user identity information in the log helps you determine whether the request was made with root or IAM user credentials, with temporary security credentials for a role or federated user, or by another AWS service. For more information, see the userIdentity field in the CloudTrail Event Reference. You can store your log files in your bucket for as long as you want, but you can also define Amazon S3 lifecycle rules to archive or delete log files automatically. By default, your log files are encrypted by using Amazon S3 server-side encryption (SSE). You can choose to have CloudTrail publish Amazon SNS notifications when new log files are delivered if you want to take quick action upon log file delivery. For more information, see Configuring Amazon SNS Notifications. You can also aggregate Amazon SQS log files from multiple AWS regions and multiple AWS accounts into a single Amazon S3 bucket. For more information, see Aggregating CloudTrail Log Files to a Single Amazon S3 Bucket.
Question : Which of the following information can be included in an AMI?
1. A template for the root volume for the instance (for example, an operating system, an application server, and applications) 2. Launch permissions that control which AWS accounts can use the AMI to launch instances 3. A block device mapping that specifies the volumes to attach to the instance when it's launched 4. 1 and 2 only 5. All 1,2 and 3
Correct Answer :5 An Amazon Machine Image (AMI) provides the information required to launch an instance, which is a virtual server in the cloud. You specify an AMI when you launch an instance, and you can launch as many instances from the AMI as you need.
An AMI includes the following: A template for the root volume for the instance (for example, an operating system, an application server, and applications) Launch permissions that control which AWS accounts can use the AMI to launch instances A block device mapping that specifies the volumes to attach to the instance when it's launched
Question :
If your requirement is to have fast re-boot and need more than 500GB storage, which type of AMI you will prefer 1. Amazon EBS-Backed 2. Amazon Instance Store-Backed 3. Any of the 1 and 2 4. None of the above
Correct Answer : 1 All AMIs are categorized as either backed by Amazon EBS or backed by instance store. The former means that the root device for an instance launched from the AMI is an Amazon EBS volume created from an Amazon EBS snapshot. The latter means that the root device for an instance launched from the AMI is an instance store volume created from a template stored in Amazon S3.
Characteristic
Boot time Amazon EBS-Backed : Usually less than 1 minute Amazon Instance Store-Backed : Usually less than 5 minutes
Data persistence Amazon EBS-Backed : Data on Amazon EBS volumes persists after instance termination*; you can also attach instance store volumes that don't persist after instance termination. Amazon Instance Store-Backed : Data on instance store volumes persists only during the life of the instance; you can also attach Amazon EBS volumes that persist after instance termination.
Upgrading Amazon EBS-Backed : The instance type, kernel, RAM disk, and user data can be changed while the instance is stopped. Amazon Instance Store-Backed : Instance attributes are fixed for the life of an instance.
Charges Amazon EBS-Backed : You're charged for instance usage, Amazon EBS volume usage, and storing your AMI as an Amazon EBS snapshot. Amazon Instance Store-Backed : You're charged for instance usage and storing your AMI in Amazon S3.
AMI creation/bundling Amazon EBS-Backed : Uses a single command/call Amazon Instance Store-Backed : Requires installation and use of AMI tools
Stopped state Amazon EBS-Backed : Can be placed in stopped state where instance is not running, but the root volume is persisted in Amazon EBS Amazon Instance Store-Backed : Cannot be in stopped state; instances are running or terminated
1. If Your organization has just a single AWS account. 2. If Your organization has multiple AWS accounts, with each AWS account belonging to a division in the organization 3. Access Mostly Uused Products by 50000+ Subscribers 4. None of the above
1. The organization need to have an individual AWS account per employee 2. AWS resources that your organization has already created can be moved to a different AWS account 3. Access Mostly Uused Products by 50000+ Subscribers 4. 1 and 2 5. 2 and 3