Question

Megan says she never needs to look at the Transport Layer when she is searching for what went wrong with the network she supports. Is Megan right or wrong, and why? Right, because the Transport Layer is software, and network engineers do not need to focus on software. Right, because the Transport Layer usually does not go wrong in a way that involves a network engineer. Wrong, because if data are coming through garbled, it is a Transport Layer problem. Wrong, because transporting information is what a network does, and the Transport Layer is at the heart of that layer.

Answer 1

Right, because the Transport Layer usually does not go wrong in a way that involves a network engineer.

Step-by-step explanation:

The transport layer is the fourth layer in the OSI networking model. It encapsulates the data with a port number to identify the application port address and split them to segments. It's protocols helps to transport packets to destination devices. Two protocols in the transport layer are the TCP and UDP protocols.

TCP is connection oriented while UDP does not establish a connection. Protocol functions are determined and a network engineer can only analyse it's processes.

Answer 2

I'd say D: Wrong, because transporting information is what a network does, and the Transport Layer is at the heart of that layer.

Transport layer is truly at the heart of the OSI model. Its main function is to transfer application data from the source to destination. This layer provides a reliable end-to-end communication service and transfers data for the user layers above it, as well as shielding the rest of the layers below from details like message error and flow control functions. If packets get destroyed or lost during transmission, it is in the best interest of Megan to check the transport layer. Transport layer ensures that whenever something like this happens, packets must be re-transmitted.