Your website is serving on-demand training videos to your workforce. Videos are uploaded monthly in high
resolution MP4 format. Your workforce is distributed globally often on the move and using company-provided
tablets that require the HTTP Live Streaming (HLS) protocol to watch a video. Your company has no video
transcoding expertise and it required you may need to pay for a consultant.
How do you implement the most cost-efficient architecture without compromising high availability and quality
of video delivery’?
A.
Elastic Transcoder to transcode original high-resolution MP4 videos to HLS S3 to host videos with Utecycle
Management to archive original flies to Glacier after a few days CloudFront to serve HLS transcoded videos
from S3
B.
A video transcoding pipeline running on EC2 using SQS to distribute tasks and Auto Scaling to adjust the
number or nodes depending on the length of the queue S3 to host videos with Lifecycle Management to
archive all files to Glacier after a few days CloudFront to serve HLS transcoding videos from Glacier
C.
Elastic Transcoder to transcode original nigh-resolution MP4 videos to HLS EBS volumes to host videos and
EBS snapshots to incrementally backup original rues after a fe days.CioudFront to serve HLS transcoded videos
from EC2.
D.
A video transcoding pipeline running on EC2 using SOS to distribute tasks and Auto Scaling to adjust the
number of nodes depending on the length of the queue E8S volumes to host videos and EBS snapshots to
incrementally backup original files after a few days CloudFront to serve HLS transcoded videos from EC2
I would say A
Regards,
Frank
I would say B
you need SQS because the videos are uploaded monthly.
Using S3 and auto-archiving to Glacier will be much efficient and cost effective process.
you missed one
You shouldn’t and can’t use Glacier as a source of Cloudfront.
So, I would say A
A is more appropriate as b says glacier as origin for cloudfront distribution which is of no use
a
A
A
Utecycle = Recycle Ans A
A
I don’t see any high availability in A.
S3 dear don’t u think
AWS Elastic Transcoder
Amazon Elastic Transcoder is a highly scalable, easy-to-use and cost-effective way for developers and businesses to convert (or “transcode”) video files from their source format into versions that will play back on multiple devices like smartphones, tablets and PCs.
Elastic Transcoder is for any customer with media assets stored in S3 for e.g. developers creating apps or websites that publish user-generated content, enterprises and educational establishments converting training and communication videos, and content owners and broadcasters needing to convert media assets into web-friendly formats.
Elastic Transcoder features
can be used to convert files from different media formats into H.264/AAC/MP4 files at different resolutions, bitrates, and frame rates, and set up transcoding pipelines to transcode files in parallel.
can be configured to overlay up to four graphics, known as watermarks, over a video during transcoding
can be configured to transcode captions, or subtitles, from one format to another and supports embedded and sidebar caption types
provides clip stitching ability to stitch together parts, or clips, from multiple input files to create a single output
can be configured to create Thumbnails
Elastic Transcoder is integrated with CloudTrail, an AWS service that captures information about every request that is sent to the Elastic Transcoder API by your AWS account, including your IAM users
Elastic Transcoder Components
Presets
are templates that contain most of the settings for transcoding media files from one format to another.
Elastic Transcoder includes some default presets for common formats and ability to create customized presets
Jobs
do the work of transcoding and converts a file into up to 30 formats.
takes the input file to be transcoded, names of the transcoded files and several other settings as input
For each transcoded format a preset needs to be specified
Pipelines
are queues that manage the transcoding jobs.
Elastic Transcoder starts processing the jobs and transcoding into format (for multiple formats) in the order they are added.
can be paused to temporarily stop processing jobs
Notifications
help keep you apprised of the status of a job, i.e. started, completed, encounters warning or error
eliminate the need for polling to determine when a job has finished and can be configured during pipeline creation
option:A