Question : Which of the following is an example of a good DynamoDB hash key schema for provisioned throughput efficiency? 1. User ID, where the application has many different users. 2. Status Code where most status codes are the same 3. Device ID, where one is by far more popular than all the others. 4. Game Type, where there are three possible game types
Question : When a Simple Queue Service message triggers a task that takes minutes to complete, which process below will result in successful processing of the message and remove it from the queue while minimizing the chances of duplicate processing? 1. Retrieve the message with an increased visibility timeout, process the message, delete the message from the queue 2. Retrieve the message with an increased visibility timeout, delete the message from the queue, process the message 3. Retrieve the message with increased DelaySeconds, process the message, delete the message from the queue 4. Retrieve the message with increased DelaySeconds, delete the message from the queue, process the message
Correct Answer : Get Lastest Questions and Answer : Explanation: When a consuming component in your system receives and processes a message from the queue, the message remains in the queue. Why doesn't Amazon SQS automatically delete it? Because your system is distributed, there's no guarantee that the component will actually receive the message (it's possible the connection could break or the component could fail before receiving the message). Therefore, Amazon SQS does not delete the message, and instead, your consuming component must delete the message from the queue after receiving and processing it. Immediately after the component receives the message, the message is still in the queue. However, you don't want other components in the system receiving and processing the message again. Therefore, Amazon SQS blocks them with a visibility timeout, which is a period of time during which Amazon SQS prevents other consuming components from receiving and processing that message. There is a 120,000 limit for the number of inflight messages per queue. Messages are inflight after they have been received from the queue by a consuming component, but have not yet been deleted from the queue. If you reach the 120,000 limit, you will receive an OverLimit error message from Amazon SQS. To help avoid reaching the limit, you should delete the messages from the queue after they have been processed. You can also increase the number of queues you use to process the messages. Extending a Message's Visibility Timeout When you receive a message from a queue and begin processing it, you may find the visibility timeout for the queue is insufficient to fully process and delete that message. To give yourself more time to process the message, you can extend its visibility timeout by using the ChangeMessageVisibility action to specify a new timeout value. Amazon SQS restarts the timeout period using the new value. For example, let's say the timeout for the queue is 30 seconds, and you receive a message from that queue. When you're 20 seconds into the timeout for that message (i.e., you have 10 seconds left), you want to give yourself 60 more seconds, so you immediately call ChangeMessageVisibility for the message with VisibilityTimeout set to 60 seconds. This means that you extended the message's visibility timeout from 30 seconds to 80 seconds: 20 seconds from the initial timeout setting plus 60 seconds from when you changed the timeout. When you extend a message's visibility timeout, the new timeout applies only to that particular receipt of the message. ChangeMessageVisibility does not affect the timeout for the queue or later receipts of the message. If for some reason you don't delete the message and receive it again, its visibility timeout is the original value set for the queue.
Question :
If an AMI has a product code, you can't make it
1. Private 2. Public 3. Shareable 4. There is no attribute like product code on AMI
Explanation: Amazon EC2 enables you to share your AMIs with other AWS accounts. You can allow all AWS accounts to launch the AMI (make the AMI public), or only allow a few specific accounts to launch the AMI. You are not billed when your AMI is launched by other AWS accounts; only the accounts launching the AMI are billed. Note
If an AMI has a product code, you can't make it public. You must share the AMI with only specific AWS accounts.
1. This permission change will be effective after instance restarted 2. This permission change will be effective almost immediately 3. Access Mostly Uused Products by 50000+ Subscribers 4. You have to drop this role first and create another one and launch the ec2 server again with the new role as input parameter