Amazon Exam SCS-C02 Topic 8 Question 23 Discussion

Actual exam question for Amazon's SCS-C02 exam

Question #: 23
Topic #: 8

A company uses HTTP Live Streaming (HL'S) to stream live video content to paying subscribers by using Amazon CloudFront. HLS splits the video content into chunks so that the user can request the right chunk based on different conditions. Because the video events last for several hours, the total video is made up of thousands of chunks.

The origin URL is not disclosed, and every user is forced to access the CloudFront URL. The company has a web application that authenticates the paying users against an internal repository and a CloudFront key pair that is already issued.

What is the simplest and MOST effective way to protect the content?

ADevelop the application to use the CloudFront key pair to create signed URLs that users will use to access the content.

BDevelop the application to use the CloudFront key pair to set the signed cookies that users will use to access the content.

CDevelop the application to issue a security token that Lambda@Edge will receive to authenticate and authorize access to the content

DKeep the CloudFront URL encrypted inside the application, and use AWS KMS to resolve the URL on-the-fly after the user is authenticated.

Show Suggested Answer

Suggested Answer: B

Utilizing CloudFront signed cookies is the simplest and most effective way to protect HLS video content for paying subscribers. Signed cookies provide access control for multiple files, such as video chunks in HLS streaming, without the need to generate a signed URL for each video chunk. This method simplifies the process for long video events with thousands of chunks, enhancing user experience while ensuring content protection.

by Jacquline at Jul 08, 2024, 10:58 PM

Limited Time Offer

25%

Off

Get Premium SCS-C02 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Pete

10 months ago

Haha, I love how they're trying to 'not disclose the origin URL.' Like that's going to stop anyone these days. All the more reason to go with option B and keep things simple. Signed cookies all the way!

upvoted 0 times

Lenita

9 months ago

I think using signed cookies is more secure and easier to manage in the long run.

upvoted 0 times

...

Van

9 months ago

But what about using the CloudFront key pair to create signed URLs? Wouldn't that be effective too?

upvoted 0 times

...

Anglea

9 months ago

Yeah, I agree. Signed cookies are the way to go for simplicity.

upvoted 0 times

...

Marta

11 months ago

I don't know, guys. Signed URLs just seem like the most straightforward solution to me. Less overhead than managing cookies or security tokens, and it still keeps the content protected. I think option A is the winner here.

upvoted 0 times

Xochitl

9 months ago

I see your point, but I think using Lambda@Edge with a security token could provide better control. Option C might be worth considering.

upvoted 0 times

...

Valda

9 months ago

I think using signed cookies might be a bit more secure though. Option B could be a good choice.

upvoted 0 times

...

Lea

9 months ago

I agree, signed URLs are definitely the simplest solution. Option A all the way.

upvoted 0 times

...

Hermila

9 months ago

I see your point, but I think using Lambda@Edge with a security token could provide more control and flexibility. Option C might be the best choice.

upvoted 0 times

...

Karina

9 months ago

I think using signed cookies could also work well. It's a good balance between security and simplicity. Option B is worth considering.

upvoted 0 times

...

Lacresha

10 months ago

I agree, signed URLs are simple and effective. Option A is the way to go.

upvoted 0 times

...

Tamala

11 months ago

Ah, the old 'encrypt the URL and use KMS' trick. Clever, but I think that might be a bit overkill for this scenario. Why make things more complicated than they need to be? I'd go with option B as well.

upvoted 0 times

Chaya

10 months ago

Yeah, option B seems like the most straightforward solution here.

upvoted 0 times

...

Thea

10 months ago

I agree, keeping it simple is usually the best approach.

upvoted 0 times

...

Raul

11 months ago

I think option D could also be a good choice. Keeping the CloudFront URL encrypted and using AWS KMS sounds like a secure method as well.

upvoted 0 times

...

Jerrod

11 months ago

Hmm, I'm not so sure. Signed cookies could be a bit of a hassle to manage. Maybe option C with a security token and Lambda@Edge would be a better choice. That way, we can have more fine-grained control over who can access the content.

upvoted 0 times

...

Richelle

11 months ago

Okay, the key here is protecting the content from unauthorized access. I think option B is the way to go - using the CloudFront key pair to set signed cookies seems like the simplest and most effective approach.

upvoted 0 times

Yoko

10 months ago

True, simplicity and effectiveness are key when it comes to protecting content. Option B seems like the best choice.

upvoted 0 times

...

Skye

10 months ago

I think using signed cookies is easier to implement and manage compared to signed URLs.

upvoted 0 times

...

Reuben

10 months ago

But wouldn't using signed URLs with the key pair be just as effective?

upvoted 0 times

...

Haydee

11 months ago

I agree, using signed cookies with the CloudFront key pair sounds like a secure method.

upvoted 0 times

...

Moon

11 months ago

I agree with Letha. Using signed URLs seems like a secure way to control access to the content.

upvoted 0 times

...

Letha

11 months ago

I think the simplest and most effective way to protect the content is to develop the application to use the CloudFront key pair to create signed URLs.

upvoted 0 times

...