SSL/TLS relies on digital certificates to support encrypted communications and to help users trust that they are connecting to the correct server. A TLS certificate is typically an X.509 certificate that binds a public key to an identity, such as a domain name, and is digitally signed by a trusted issuer. In most public internet use cases, these certificates are issued by Certificate Authorities that browsers and operating systems already trust through pre-installed root certificates. Because of that trust chain, organizations commonly obtain certificates by purchasing or otherwise obtaining them from certificate authorities, which is why option B is correct.

During the TLS handshake, the server presents its certificate to the client. The client validates the certificate's signature chain, validity period, and that the certificate matches the domain being accessed. Once validated, TLS establishes session keys used to encrypt data in transit and protect it from eavesdropping and tampering. Certificates themselves are not ''similar to unencrypted data,'' and they are not specific to thumb-drive storage; they are used to secure network communications. Certificates also do not primarily provide ''authorization'' to access data. Authorization is typically enforced by application and access control mechanisms after authentication. Certificates support authentication of endpoints and enable secure key exchange, which are prerequisites for secure transport encryption and trustworthy connections.