フリー問題

問題文

A developer runs the command line client and successfully logs in with the username and password method. On the next command, no token is passed on the command line, yet the request is authenticated. What explains this?

選択肢

1. The client cached the token through its token helper, which writes it to a file in the user's home directory, and later commands read it from there.
2. The server remembers the source address of the successful login and treats later requests from that address as already authenticated.
3. The client keeps an authenticated session open with the server, so no token is needed for subsequent requests on the same connection.
4. The login stored the username and password in the operating system's credential store, and the client silently repeats the login before each command so that a fresh token is used every time.