As a part of the smart city initiatives, Hyderabad (GHMC), one of the largest cities in southern India is working on capturing massive volumes of video streams 24/7 captured from the large numbers of “Vivotek IB9371 - HT” cameras installed at traffic lights, parking lots, shopping malls, and just about every public venue to help solve traffic problems, help prevent crime, dispatch emergency responders, and much more.
GHMC uses AWS to host their entire infrastructure. The camera's write stream into Kinesis Video Stream securely and eventually consumed by applications for custom video processing, on-demand video playback and also consumed by AWS Rekognition for video analytics.
Along with the stream, different modes of streaming metadata are sent along with the stream.
There are 2 scenarios that need to be fulfilled. ·Requirement 1 - Affix metadata on a specific Adhoc basis to fragments in a stream, aka when smart camera detects motion in restricted areas, adds metadata [Motion = true] to the corresponding fragments that contain the motion before sending the fragments to its Kinesis Video Stream ·Requirement 2 - affix metadata to successive, consecutive fragments in a stream based on a continuing need, aka all smart cameras in the city sends the current latitude and longitude coordinates associated with all fragments it sends to its Kinesis Video Stream How can this be achieved? Select 2 options.
Click on the arrows to vote for the correct answer
A. B. C. D. E. F.Answer: A, D.
Option A is correct.
Requirement 1 can be fulfilled by sending Nonpersistent data.
https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/how-meta.htmlOption B is incorrect.
Requirement 2 cannot be fulfilled by sending Nonpersistent data.
https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/how-meta.htmlOption C is incorrect.
Requirement 1 cannot be fulfilled by sending Persistent data.
https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/how-meta.htmlOption D is correct.
Requirement 2 can be fulfilled by sending Persistent data.
https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/how-meta.htmlOption E is incorrect.
Requirement 1 can be fulfilled by sending Nonpersistent data while Requirement 2 can be fulfilled by sending Persistent data.
https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/how-meta.htmlOption F is incorrect.
Requirement 1 cannot be fulfilled by sending Persistent data while Requirement 2 can be fulfilled by sending Persistent data.
https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/how-meta.htmlTo fulfill Requirement 1 and Requirement 2 for affixing metadata on the video stream fragments in a smart city initiative, we can use both Nonpersistent data and Persistent data.
A. Requirement 1 can be fulfilled by sending Nonpersistent data We can use Nonpersistent data to fulfill Requirement 1. Nonpersistent data is ephemeral and only available for a short period. The metadata can be affixed to a specific fragment in the stream on an ad-hoc basis when the smart camera detects motion in restricted areas by sending Nonpersistent data. The corresponding fragments that contain the motion can have metadata added to them before sending them to Kinesis Video Stream. Since the metadata is added on an ad-hoc basis and is not required to be retained for an extended period, Nonpersistent data is a suitable option for fulfilling Requirement 1.
B. Requirement 2 can be fulfilled by sending Nonpersistent data We can use Nonpersistent data to fulfill Requirement 2. Since the smart cameras in the city send the current latitude and longitude coordinates associated with all fragments sent to Kinesis Video Stream, we can affix the metadata to successive, consecutive fragments in the stream based on a continuing need by sending Nonpersistent data. Nonpersistent data is suitable for this requirement as it is transient and does not require retention for an extended period.
C. Requirement 1 can be fulfilled by sending Persistent data We can also use Persistent data to fulfill Requirement 1. Persistent data is durable and remains available even after the original application has completed. Since metadata needs to be affixed on an ad-hoc basis to the specific fragment in the stream when the smart camera detects motion in restricted areas, Persistent data can be used to ensure that the metadata is retained for future use.
D. Requirement 2 can be fulfilled by sending Persistent data We can use Persistent data to fulfill Requirement 2 as well. Since the current latitude and longitude coordinates associated with all fragments sent to Kinesis Video Stream need to be retained for future use, Persistent data can be used to ensure that the metadata is not lost and remains available for consumption by other applications.
E. Both Requirement 1 and Requirement 2 can be fulfilled by sending Nonpersistent data Both Requirement 1 and Requirement 2 can be fulfilled by using Nonpersistent data. Nonpersistent data is transient and does not require retention for an extended period, making it a suitable option for fulfilling both requirements.
F. Both Requirement 1 and Requirement 2 can be fulfilled by sending Persistent data. Both Requirement 1 and Requirement 2 can also be fulfilled by using Persistent data. Persistent data is durable and remains available even after the original application has completed, making it a suitable option for retaining metadata for future use in both scenarios.