Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam DVA-C02 Topic 6 Question 29 Discussion

Actual exam question for Amazon's DVA-C02 exam
Question #: 29
Topic #: 6
[All DVA-C02 Questions]

A developer is designing a serverless application for a game in which users register and log in through a web browser The application makes requests on behalf of users to a set of AWS Lambda functions that run behind an Amazon API Gateway HTTP API

The developer needs to implement a solution to register and log in users on the application's sign-in page. The solution must minimize operational overhead and must minimize ongoing management of user identities.

Which solution will meet these requirements'?

Show Suggested Answer Hide Answer
Suggested Answer: A

Amazon Cognito User Pools:A managed user directory service, simplifying user registration and login.

Social Identity Providers:Cognito supports integration with external providers (e.g., Google, Facebook), reducing development effort.

IAM Roles for Authorization:Cognito-managed IAM roles grant fine-grained access to AWS resources (like Lambda functions).

Operational Overhead:Cognito minimizes the need to manage user identities and credentials independently.


Amazon Cognito Documentationhttps://docs.aws.amazon.com/cognito/

Cognito User Pools for Web Applications:https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-app-integration.html

Contribute your Thoughts:

Joesph
5 months ago
Option D might work, but storing passwords in DynamoDB? That's a recipe for disaster. Better stick with the industry-standard solution in Option A.
upvoted 0 times
...
Aileen
5 months ago
Haha, Option B is a classic 'security by obscurity' approach. I hope the developer doesn't try to reinvent the wheel and just use Cognito!
upvoted 0 times
Viola
4 months ago
B: Agreed, it's important to use a secure and reliable solution like Amazon Cognito.
upvoted 0 times
...
Kimberlie
4 months ago
A: Yeah, using Cognito is definitely the way to go for user registration and login.
upvoted 0 times
...
...
Merlyn
5 months ago
I agree, Option A is the way to go. Cognito is designed for this exact use case, and it'll save the developer a lot of time and effort compared to the other options.
upvoted 0 times
Yasuko
4 months ago
Definitely, using Cognito will minimize operational overhead and management of user identities.
upvoted 0 times
...
Glendora
4 months ago
Creating user pools with external identity providers is the most efficient solution.
upvoted 0 times
...
Stefanie
4 months ago
I agree, Cognito simplifies user management and authentication.
upvoted 0 times
...
Staci
4 months ago
Option A is definitely the best choice. Cognito handles user registration and login seamlessly.
upvoted 0 times
...
...
Darnell
5 months ago
I see both points, but I think option A is more scalable and easier to manage in the long run.
upvoted 0 times
...
Renato
5 months ago
Option A seems like the best choice here. Cognito user pools can handle user registration and authentication with minimal overhead, and the IAM roles provide the necessary access control.
upvoted 0 times
Adrianna
5 months ago
B: Agreed, IAM roles with external social identity providers will minimize management of user identities.
upvoted 0 times
...
Joseph
5 months ago
A: I think option A is the way to go. Cognito user pools handle user registration and authentication efficiently.
upvoted 0 times
...
...
Phyliss
5 months ago
I disagree, I believe option D is better as it involves storing user information in an Amazon DynamoDB table with an attached IAM policy for security.
upvoted 0 times
...
Lili
6 months ago
I think option A is the best choice because it involves using Amazon Cognito user pools for user registration and login.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77