SAA-C03 Question 291

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose AB1

  A: AWS Signed Cookie: A temporary access token stored in the browser that allows access to multiple protected files (like a whole video library) without changing the URLs. This can be used for the clients that can't change their hardcoded URL. B: AWS Signed URL: A temporary, secure link to access a specific file (like a video) on CloudFront or S3. Only users with this special URL can access the content. This can be used for the clients that have. custom clients which don't support cookies. Using both methods, both type of clients will experience no impact.

• Chose AB1

  Signed cookies, signed URLs, and JSON web token (JWT) are Amazon Cloudfront authentication methods. But as the question says with the least possible impact for users, I would go with AB since D requires using Lambda@Edge and I suppose it has more impact to the users than the first two.

• Chose BD1

  B. Signed URLs: Signed URLs allow you to control access to your content in CloudFront by providing URLs that are valid only for a specified duration. This means users can access the content using the same URLs they have hardcoded, without the need for cookies or special client support. D. JSON Web Token (JWT): JSON Web Tokens (JWTs) can be used to control access to resources by embedding authentication and authorization information in the token itself. Users can include the JWT in the request headers, allowing access to be controlled without relying on cookies. This approach doesn't require changes to hardcoded URLs and can be integrated into custom HTTP clients.