What describes a session ID?

What describes a session ID?

• A. A unique token that a server assigns for the duration of a client's communications with the server
• B. An identifying user name
• C. A session cookie used after login
• D. A cryptographic nonce for each request

Answer: (A)

A session ID is a unique token that the server creates to identify a specific user's session for the duration of their interaction with the application. HTTP is stateless, so the server wouldn’t know who you are from one request to the next. It generates a random, hard-to-guess identifier and associates any session data (like login status, shopping cart contents, preferences) with that ID on the server. The client then presents this token with subsequent requests (typically via a cookie), and the server uses it to fetch the correct session data and continue where you left off. This concept is different from a user name, which identifies the user themselves, and it’s not a per-request nonce. A session cookie is a common transport method for the ID, but what matters is the server-issued token that links requests to a particular session.

A session ID is a unique token that the server creates to identify a specific user's session for the duration of their interaction with the application. HTTP is stateless, so the server wouldn’t know who you are from one request to the next. It generates a random, hard-to-guess identifier and associates any session data (like login status, shopping cart contents, preferences) with that ID on the server. The client then presents this token with subsequent requests (typically via a cookie), and the server uses it to fetch the correct session data and continue where you left off. This concept is different from a user name, which identifies the user themselves, and it’s not a per-request nonce. A session cookie is a common transport method for the ID, but what matters is the server-issued token that links requests to a particular session.