Answer:
The senders PC is using UDP protocol.
Explanation:
UDP is not like TCP. TCP assigns a sequence number for every byte of data and ensures complete delivery of the data as it passes "hands" until it reaches its destination. UDP has quicker communications but at the expense of ensuring that the data has had a complete successful delivery.
UDP may allow a connection to have continuous data communication but at the expense of ACK. What all of this means is that because UDP cannot guarantee complete data delivery due to it not having backup measures in place to ensure complete delivery has occurred, only TCP is capable of doing this since TCP does have countermeasures in place due to its sequence number check at every byte of data. Since TCP has countermeasures to ensure complete delivery, it is slower than UDP due to the additional checks which UDP does not have.
In the end, "The senders PC is using UDP protocol" when answering "What could be one possible reason where the recipient is not guaranteed that the data being streamed will not get interrupted". Well, based on the choices you provided anyways:
-The recipient is having a static IP connection with the Internet service provider
-The senders PC is using UDP protocol
-The recipient is having an outdated error correction technique installed.
-The Recipient PC is having the higher security settings in his internet
