Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam SCS-C02 Topic 8 Question 23 Discussion

Actual exam question for Amazon's SCS-C02 exam
Question #: 23
Topic #: 8
[All SCS-C02 Questions]

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?

Show Suggested Answer Hide 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.


Contribute your Thoughts:

Pete
18 days 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
...
Marta
1 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
Lacresha
20 days ago
I agree, signed URLs are simple and effective. Option A is the way to go.
upvoted 0 times
...
...
Tamala
1 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
18 days ago
Yeah, option B seems like the most straightforward solution here.
upvoted 0 times
...
Thea
29 days ago
I agree, keeping it simple is usually the best approach.
upvoted 0 times
...
...
Raul
1 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
2 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
2 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
7 days ago
True, simplicity and effectiveness are key when it comes to protecting content. Option B seems like the best choice.
upvoted 0 times
...
Skye
17 days ago
I think using signed cookies is easier to implement and manage compared to signed URLs.
upvoted 0 times
...
Reuben
27 days ago
But wouldn't using signed URLs with the key pair be just as effective?
upvoted 0 times
...
Haydee
1 months ago
I agree, using signed cookies with the CloudFront key pair sounds like a secure method.
upvoted 0 times
...
...
Moon
2 months ago
I agree with Letha. Using signed URLs seems like a secure way to control access to the content.
upvoted 0 times
...
Letha
2 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
...

Save Cancel