Question : Company B has many users updating the same table. At times it is not uncommon for multiple users to update the same item and attribute of an item at the same time. If user A calls an item in a table to update an attribute at the same time as user B and user B updates the table first, what can we deploy in DynamoDB to ensure User A is not updating an item that was updated since User A's table read?
1. Atomic Counters 2. Extra API read calls to determine if the data was updated before the update call is made 3. Conditional Writes 4. Eventual Consistency
Correct Answer : Get Lastest Questions and Answer : With a conditional write, an operation succeeds only if the item attributes meet one or more expected conditions; otherwise it returns an error
Question : How many global secondary indexes are allowed per table?
Question : Games-R-Us is launching a new game app for mobile devices. Users will log into the game using their existing Facebook account and the game will record player data and scoring information directly to a DynamoDB table. What is the most secure approach for signing requests to the DynamoDB API? 1. Create an IAM user with access credentials that are distributed with the mobile app to sign the requests 2. Distribute the AWS root account access credentials with the mobile app to sign the requests 3. Request temporary security credentials using web identity federation to sign the requests 4. Establish cross account access between the mobile app and the DynamoDB table to sign the requests
Explanation: When a user want to play a game, he signs in to his Login with Amazon account from within the gaming app. The app then calls AWS Security Token Service (AWS STS), providing the Login with Amazon app ID and requesting membership in GameRole. AWS STS returns temporary AWS credentials to the app and allows it to access the GameScores table, subject to theGameRole policy document.
1. can be used to launch EC2 instances in any AWS region 2. can only be used to launch EC2 instances in the same country as the AMI is stored 3. Access Mostly Uused Products by 50000+ Subscribers 4. can only be used to launch EC2 instances in the same AWS availability zone as the AMI is stored