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…

Question

Options

• ACreate Amazon Cognito user pools for external social identity providers. Configure IAM roles for
• BProgram the sign-in page to create users' IAM groups with the IAM roles attached to the groups.
• CCreate an Amazon RDS for SQL Server DB instance to store the users and manage the
• DConfigure the sign-in page to register and store the users and their passwords in an Amazon

• A
  94% (32)
• B
  3% (1)
• C
  3% (1)

Explanation

Amazon Cognito user pools are purpose-built for exactly this use case - managed user registration, authentication, and identity storage with zero server maintenance, and they integrate natively with API Gateway HTTP APIs as an authorizer. Option B is wrong because IAM is designed to control access to AWS resources, not to manage end-application user accounts; using IAM users/groups for game players would be a security anti-pattern and doesn't scale. Option C is wrong because a self-managed RDS SQL Server database requires provisioning, patching, backups, and custom auth logic - the opposite of minimizing operational overhead. Option D (likely DynamoDB or S3) is wrong for the same reason: storing passwords manually means you own hashing, salting, session management, and security compliance, all of which Cognito handles for you automatically.

Memory tip: On the AWS exam, whenever you see the phrase "minimize operational overhead" paired with "user sign-in/registration," map it directly to Cognito - it's AWS's fully managed "identity as a service" and the default answer for application-level authentication in serverless stacks.

No community discussion yet for this question.