Briefly discuss the type of tasks typically handled by connectionless protocols.

What will be an ideal response?

Message checksum: Although connectionless protocols don't track transmission behavior or completeness of delivery (that's what best-effort delivery means), they can optionally include a checksum for each datagram. This makes it easy for the Transport layer protocol to report to a higher-layer protocol whether the packet made it to the destination in the same form as when it left the sender, without having to handle the potentially complicated details involved.
Higher-layer protocol identification: Generally speaking, all TCP/IP Transport layer protocols use source and destination port address fields in their headers to identify specific Application layer protocols on the sending and receiving hosts, so they can exchange messages at that higher layer. This protocol identification mechanism identifies an Application layer protocol through the well-known port addresses associated with most higher-layer TCP/IP protocols and services. This mechanism also permits application processes that use those protocols or services to exchange data to identify each other uniquely while individual or multiple streams of communications between a sender and a receiver are underway. Thus, even though a connectionless protocol has no internal methods for creating, managing, and terminating connections, it does provide a mechanism for such activities to occur at the Application layer.