New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Amazon SCS-C02 Exam - 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.


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:

0/2000 characters
Submit Cancel
Dorothy
3 months ago
Wait, can you really keep the URL encrypted like that? Sounds tricky!
upvoted 0 times
...
Kathrine
3 months ago
I agree, signed URLs seem simpler and effective!
upvoted 0 times
...
Lennie
3 months ago
Isn't using AWS KMS a bit overkill for this?
upvoted 0 times
...
Johna
4 months ago
I think signed cookies are more flexible though.
upvoted 0 times
...
Gary
4 months ago
A signed URL is the way to go!
upvoted 0 times
...
Tawanna
4 months ago
I think keeping the URL encrypted sounds interesting, but it seems overly complicated for just protecting video content. I’d lean towards option A or B instead.
upvoted 0 times
...
Glendora
4 months ago
I vaguely recall something about Lambda@Edge and security tokens, but I’m not confident if that’s the simplest method. Option C feels a bit complex for this scenario.
upvoted 0 times
...
Olen
4 months ago
I'm not entirely sure, but I feel like signed cookies could also work well for managing user sessions. Maybe option B is worth considering?
upvoted 0 times
...
Johana
5 months ago
I remember we discussed signed URLs in class, and they seem like a straightforward way to control access. I think option A might be the right choice.
upvoted 0 times
...
Keith
5 months ago
Okay, I've got a strategy. I'll focus on the requirement to protect the content, so I think using signed URLs or cookies with the CloudFront key pair is the way to go. That should be the most effective approach.
upvoted 0 times
...
Ettie
5 months ago
Hmm, I'm a bit confused about the different options here. I'll need to think through the pros and cons of each approach to decide which one is the simplest and most effective.
upvoted 0 times
...
Viva
5 months ago
This seems like a straightforward question about securing video content using CloudFront. I think the key is to use the CloudFront key pair to create signed URLs or cookies for authenticated users.
upvoted 0 times
...
Yaeko
5 months ago
I feel pretty confident about this one. Developing the application to use the CloudFront key pair to create signed URLs or set signed cookies seems like the simplest and most effective way to protect the content.
upvoted 0 times
...
Ona
5 months ago
This looks like a question about MPLS and BGP. I'll need to carefully review the options and the exhibit to determine what the output is showing.
upvoted 0 times
...
Marge
5 months ago
I'm not sure, but didn't we discuss that failures could sometimes not be directly reported? That makes me think option D could be possible.
upvoted 0 times
...
Pete
2 years 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
1 year ago
I think using signed cookies is more secure and easier to manage in the long run.
upvoted 0 times
...
Van
2 years ago
But what about using the CloudFront key pair to create signed URLs? Wouldn't that be effective too?
upvoted 0 times
...
Anglea
2 years ago
Yeah, I agree. Signed cookies are the way to go for simplicity.
upvoted 0 times
...
...
Marta
2 years 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
1 year 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
1 year ago
I think using signed cookies might be a bit more secure though. Option B could be a good choice.
upvoted 0 times
...
Lea
1 year ago
I agree, signed URLs are definitely the simplest solution. Option A all the way.
upvoted 0 times
...
Hermila
1 year 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
2 years 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
2 years ago
I agree, signed URLs are simple and effective. Option A is the way to go.
upvoted 0 times
...
...
Tamala
2 years 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
2 years ago
Yeah, option B seems like the most straightforward solution here.
upvoted 0 times
...
Thea
2 years ago
I agree, keeping it simple is usually the best approach.
upvoted 0 times
...
...
Raul
2 years 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 years 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 years 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
2 years ago
True, simplicity and effectiveness are key when it comes to protecting content. Option B seems like the best choice.
upvoted 0 times
...
Skye
2 years ago
I think using signed cookies is easier to implement and manage compared to signed URLs.
upvoted 0 times
...
Reuben
2 years ago
But wouldn't using signed URLs with the key pair be just as effective?
upvoted 0 times
...
Haydee
2 years ago
I agree, using signed cookies with the CloudFront key pair sounds like a secure method.
upvoted 0 times
...
...
Moon
2 years ago
I agree with Letha. Using signed URLs seems like a secure way to control access to the content.
upvoted 0 times
...
Letha
2 years 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