AWS Certified Developer - Associate Questions and Answers (Dumps and Practice Questions)

Question : What is the maximum number of S Buckets available per AWS account?

1. 100 per region
2. there is no limit
3. 100 per account
4. 500 per account
5. 100 per IAM user

Correct Answer : 1
Exp: Bucket Restrictions and Limitations

A bucket is owned by the AWS account that created it. Each AWS account can own up to 100 buckets at a time. Bucket ownership is not transferable; however, if a bucket is empty, you can delete it. After a bucket is deleted, the name becomes available to reuse, but the name might not be available for you to reuse for various reasons. For example, some other account could create a bucket with that name. Note, too, that it might take some time before the name can be reused. So if you want to use the same bucket name, don't delete the bucket.

There is no limit to the number of objects that can be stored in a bucket and no difference in performance whether you use many buckets or just a few. You can store all of your objects in a single bucket, or you can organize them across several buckets.

You cannot create a bucket within another bucket.

The high-availability engineering of Amazon S3 is focused on get, put, list, and delete operations. Because bucket operations work against a centralized, global resource space, it is not appropriate to create or delete buckets on the high-availability code path of your application. It is better to create or delete buckets in a separate initialization or setup routine that you run less often.

Note
If your application automatically creates buckets, choose a bucket naming scheme that is unlikely to cause naming conflicts. Ensure that your application logic will choose a different bucket name if a bucket name is already taken.





Question : You have EC instance which is booted using an AMI, you have one java process running on it
and calculate some ratios and store the final values in local system. However, because of some exception
your ec2 image failed or crashed and stopped. Now you re-start the instance, but all the ratio values
which you have stored locally is not available what could be the reason ?


1. Image was EBS backed
2. Image was Instance Store-Backed
3. It needs to be stored not in the file system
4. None of the above


Correct Answer : 2

You can launch an instance from one of two types of AMIs: an instance store-backed AMI or an Amazon EBS-backed AMI. The description of an AMI includes which type of AMI it is; you'll see the root device referred to in some places as either ebs (for Amazon EBS-backed) or instance store (for instance store-backed). This is important because there are significant differences between what you can do with each type of AMI.
Instances that use instance stores for the root device automatically have instance store volumes available, with one serving as the root device volume. When an instance is launched, the image that is used to boot the instance is copied to the root volume (typically sda1). Any data on the instance store volumes persists as long as the instance is running, but this data is deleted when the instance is terminated (instance store-backed instances do not support the Stop action) or if it fails (such as if an underlying drive has issues).





Question : Disable password-based logins for instances launched from your AMI, why ?

1. Passwords can be found or cracked, and are a security risk
2. Passwords based images are not supported
3. There is no way while launching the AMI you can insert the password
4. None of the above

Correct Answer : 1
Security Best Practices


* Use AWS Identity and Access Management (IAM) to control access to your AWS resources, including your instances. You can create IAM users and groups under your AWS account, assign security credentials to each, and control the access that each has to resources and services in AWS. For more information, see Controlling Access to Amazon EC2 Resources.
* Restrict access by only allowing trusted hosts or networks to access ports on your instance. For example, you can restrict SSH access by restricting incoming traffic on port 22. For more information, see Amazon EC2 Security Groups.
* Review the rules in your security groups regularly, and ensure that you apply the principle of least privilege only open up permissions that you require. You can also create different security groups to deal with instances that have different security requirements. Consider creating a bastion security group that allows external logins, and keep the remainder of your instances in a group that does not allow external logins.
* Disable password-based logins for instances launched from your AMI. Passwords can be found or cracked, and are a security risk.

Related Questions

---

Question : IAM AWS Account is



1. Region specific
2. Availability zone specific
3. Access Mostly Uused Products by 50000+ Subscribers
4. None of above


Question : While setting up IAM , is following configuration possible ?

AWS Account has a limit of 20 Amazon EC2 instances, and a user can maximum start 2 instances



1. Yes
2. No


Question : AWSTemplateFormatVersion declaration is required for the template to work inside CloudFormation.

1. True
2. False


Question : AWS CloudFormation enables you to create and delete related AWS resources together as a unit called a _______


1. Intrinsic Functions
2. Resources
3. Access Mostly Uused Products by 50000+ Subscribers
4. Stacks


Question : If for any reason a half of the member resource cannot be created, AWS CloudFormation keeps the half of the member resources that were created.


1. True
2. False
3. Access Mostly Uused Products by 50000+ Subscribers


Question : Explain what the following resource in a CloudFormation template does. Choose the best possible answer.
"SNSTopic" : { "Type" : "AWS::SNS::Topic", "Properties" :
{ "Subscription" :
[
{ "Protocol" : "sqs", "Endpoint" :
{ "Fn::GetAtt" :
[ "SQSQueue", "Arn" ]
}
}]
}

1. Creates an SNS topic that allow SQS subscription endpoints
2. Creates an SNS topic and then invokes the call to create an SQS queue with a logical resource name of SQSQueue
3. Access Mostly Uused Products by 50000+ Subscribers
4. Creates an SNS topic and adds a subscription ARN endpoint for the SQS resource created under the logical name SQSQueue