Premium

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



Question : What kind of following monitoring is possible with Amazon SQS and CloudWatch ?

: What kind of following monitoring is possible with Amazon SQS and CloudWatch ?
1. you can gain better insight into the performance of your Amazon SQS queues and applications
2. you can monitor the NumberOfEmptyReceives metric to make sure that your application isn't spending too much of its time polling for new messages
3. You can set an alarm to send you an email notification if a specified threshold is met for an Amazon SQS metric, such as NumberOfMessagesReceived
4. Only 2 and 3
5. All 1,2 and 3

Correct Answer : 5
Exp: Amazon SQS and CloudWatch are integrated so you can use CloudWatch to easily collect, view, and analyze metrics for your Amazon SQS queues. Once you have configured CloudWatch for Amazon SQS, you can gain better insight into the performance of your Amazon SQS queues and applications. For example, you can monitor the NumberOfEmptyReceives metric to make sure that your application isn't spending too much of its time polling for new messages. You can also set an alarm to send you an email notification if a specified threshold is met for an Amazon SQS metric, such as NumberOfMessagesReceived. For a list of all the metrics that Amazon SQS sends to CloudWatch

The metrics you configure with CloudWatch for your Amazon SQS queues are automatically collected and pushed to CloudWatch every five minutes. These metrics are gathered on all queues that meet the CloudWatch guidelines for being active. A queue is considered active by CloudWatch for up to six hours from the last activity (i.e., any API call) on the queue.


NumberOfMessagesSent The number of messages added to a queue. Units: Count Valid Statistics: Sum

SentMessageSize The size of messages added to a queue. Units: Bytes Valid Statistics: Minimum, Maximum, Average, and Count

NumberOfMessagesReceived The number of messages returned by calls to the ReceiveMessage API action. Units: Count Valid Statistics: Sum

NumberOfEmptyReceives The number of ReceiveMessage API calls that did not return a message. Units: Count Valid Statistics: Sum

NumberOfMessagesDeleted The number of messages deleted from the queue. Units: Count Valid Statistics: Sum

ApproximateNumberOfMessagesDelayed The number of messages in the queue that are delayed and not available for reading immediately. This can happen when the queue is configured as a delay queue or when a message has been sent with a delay parameter. Units: Count Valid Statistics: Average

ApproximateNumberOfMessagesVisible The number of messages available for retrieval from the queue. Units: Count Valid Statistics: Average

ApproximateNumberOfMessagesNotVisible The number of messages that are "in flight." Messages are considered in flight if they have been sent to a client but have not yet been deleted or have not yet reached the end of their visibility window. Units: Count Valid Statistics: Average




Question : You have written an application that uses the Elastic Load Balancing service to spread
traffic to several web servers. Your users complain that they are sometimes forced to login
again in the middle of using your application, after they have already logged in. This is not
behavior you have designed
What is a possible solution to prevent this happening?


: You have written an application that uses the Elastic Load Balancing service to spread
1. Use instance memory to save session state.

2. Use instance storage to save session state.
3. Use EBS to save session state

4. Use ElastiCache to save session state.
5. Use Glacier to save session slate.

Correct Answer : 4

Explanation: I've used both DynamoDB and Elasticache for session storage purposes, depending on the needs of the service. Typically, I have used Elasticache for non-critical session storage or cases where I have set an application to have a very short session expiry such that the number of users that could be impacted by an outage might be relatively small.

For more critical storage (e-commerce sessions for example) or sessions that might be set for longer lifetimes to aid in user convenience, I have opted for Dynamo. Obviously, Dynamo is typically slower than Elasticache, but still very suitable for session storage, especially at high volumes where you can guarantee your read/write throughput (as opposed to traditional database-backed sessions).





Question : Which of the following service you will be using to captures " API calls made by or on behalf of Amazon SQS in your AWS account "



: Which of the following service you will be using to captures
1. CloudWatch
2. CloudTrail
3. SQS Monitoring tool
4. 1 and 2
5. Either of 1,2 and 3

Correct Answer : 2
Amazon SQS is integrated with CloudTrail, a service that captures API calls made by or on behalf of Amazon SQS in your AWS account and delivers the log files to an Amazon S3 bucket that you specify. CloudTrail captures API calls made from the Amazon SQS console or from the Amazon SQS API. Using the information collected by CloudTrail, you can determine what request was made to Amazon SQS, the source IP address from which the request was made, who made the request, when it was made, and so on.



Related Questions

Question : When using a large Scan operation in DynamoDB, what technique can be used to minimize
the impact of a scan on a table's provisioned throughput?
 : When using a large Scan operation in DynamoDB, what technique can be used to minimize
1. Set a smaller page size for the scan
2. Use parallel scans
3. Access Mostly Uused Products by 50000+ Subscribers
4. Prewarm the table by updating all items


Question : Which of the following would you not expect to see in an SNS message body?
 : Which of the following would you not expect to see in an SNS message body?
1. SignatureCertURL
2. Signature
 3. Access Mostly Uused Products by 50000+ Subscribers
4. SubjectId


Question : Which of the following would you expect to see in the body of an SNS notification?

 : Which of the following would you expect to see in the body of an SNS notification?
1. UnsubscribeURL
2. MessageBody
3. Access Mostly Uused Products by 50000+ Subscribers
4. SignatureId


Question : Describe the process of registering a Android mobile device with SNS push notification service using GCM.

 : Describe the process of registering a Android mobile device with SNS push notification service using GCM.
1. Submit GCM notification credentials to Amazon SNS; Receive Registration ID for each mobile device;
Pass device token to SNS; SNS then creates a mobile subscription endpoint for each device and communicates with the GCM service on your behalf

2. Pass device token to SNS to create mobile subscription endpoint for each mobile device;
Request device token from each mobile device; SNS then communicates on your behalf to the GCM service
3. Access Mostly Uused Products by 50000+ Subscribers
Amazon SNS; pass GCM token credentials to Amazon SNS

4. None of the above


Question : Which of the following is a correct command to make AMI private (Using the AWS CLI)

 : Which of the following is a correct command to make AMI private (Using the AWS CLI)
1. aws ec2 modify-image-attribute --image-id ami-2bb65342 --launch-permission "{\"Add\":[{\"Group\":\"all\"}]}"
2. aws ec2 describe-image-attribute --image-id ami-2bb65342 --attribute launchPermission
 3. Access Mostly Uused Products by 50000+ Subscribers
4. None of Above


Question : Which features can be used to restrict access to data in S? Choose answers
A. Use S3 Virtual Hosting
B. Set an S3 Bucket policy.
C. Enable IAM Identity Federation.
D. Set an S3 ACL on the bucket or the object.
E. Create a CloudFront distribution for the bucket
 : Which features can be used to restrict access to data in S? Choose answers
1. A,B
2. B,C
 3. Access Mostly Uused Products by 50000+ Subscribers
4. B,D
5. A,E