Pick all that apply

• 1Choice 1.

  static let holds it strongly, so it isn't released until the process ends and deinit is effectively never called; if you need release, change it to something replaceable and nil-assignable like static var shared: SessionManager?

• 2Choice 2.

  The moment you make it releasable, the singleton's guarantee of "always one" is gone, so it's usually better to build an object scoped to the login session instead, create it at login, discard it at logout, and inject it where needed

• 3Choice 3.

  If you implement deinit, the system releases the singleton to reclaim memory when the app goes to the background, and deinit runs then

• 4Choice 4.

  Declaring it static weak var shared releases it automatically when nobody is using it and saves memory, so it's recommended

• 5Choice 5.

  A real case: at logout, you discard the object holding the user-scoped cache, DB handles, and tokens wholesale so the previous data doesn't leak to the next user