Which authentication approach enables access to multiple network resources with one login?

Which authentication approach enables access to multiple network resources with one login?

• A. Password vault
• B. Single Sign-On
• C. Two-Factor Authentication
• D. Multi-domain login

Answer: (B)

Single Sign-On lets you authenticate once to a central identity source and then access multiple network resources without re-entering credentials for each one. In practice, you log in to an identity provider that verifies who you are. Once this is confirmed, the provider issues a token or ticket you can present to other services. Those services trust the identity provider and accept the token, letting you use each resource without a fresh login. This is commonly implemented using standards like SAML, OAuth, or OpenID Connect, or via enterprise methods such as Kerberos, depending on the environment. The big benefit is a smoother workflow: you gain access to many resources through a single authentication event, reducing password fatigue and giving IT a centralized point to enforce access policies. Security-wise, it’s important to protect that central identity source, since a compromise here could affect many resources. Strong authentication at the identity provider (often MFA), proper session management, and timely revocation are essential to keep the system secure. Other options don’t fit as well because a password vault simply stores and autofills passwords without creating a shared, ongoing authenticated session across multiple resources. Two-Factor Authentication strengthens a single login with an extra verification step but doesn’t by itself enable access to multiple resources with one login. The term multi-domain login isn’t a standard mechanism for providing cross-resource single-login access.

Single Sign-On lets you authenticate once to a central identity source and then access multiple network resources without re-entering credentials for each one. In practice, you log in to an identity provider that verifies who you are. Once this is confirmed, the provider issues a token or ticket you can present to other services. Those services trust the identity provider and accept the token, letting you use each resource without a fresh login. This is commonly implemented using standards like SAML, OAuth, or OpenID Connect, or via enterprise methods such as Kerberos, depending on the environment. The big benefit is a smoother workflow: you gain access to many resources through a single authentication event, reducing password fatigue and giving IT a centralized point to enforce access policies.

Security-wise, it’s important to protect that central identity source, since a compromise here could affect many resources. Strong authentication at the identity provider (often MFA), proper session management, and timely revocation are essential to keep the system secure.

Other options don’t fit as well because a password vault simply stores and autofills passwords without creating a shared, ongoing authenticated session across multiple resources. Two-Factor Authentication strengthens a single login with an extra verification step but doesn’t by itself enable access to multiple resources with one login. The term multi-domain login isn’t a standard mechanism for providing cross-resource single-login access.