What is the difference between SSO and federation?
SSO is one login across applications. Federation is trust between organizations, and it often enables SSO.

Exam objectiveGiven a scenario, implement and maintain identity and access management
Objective 4.6 covers implementing and maintaining identity and access management: the account lifecycle, federation and single sign-on, access control models, multifactor authentication, password practices, and privileged access management.
Lifecycle and trust. Provisioning creates accounts with only the access a role needs, and de-provisioning removes it when people leave. Identity proofing establishes real-world identity, typically at enrollment and again at account recovery if needed, and attestation is a routine owner confirmation that access is still correct. Federation lets one organization trust another's authentication, and single sign-on (SSO) lets one login reach many applications, using protocols such as SAML, OAuth, and LDAP.
Authorization models. Mandatory access control uses labels set by a central authority; discretionary access control lets the resource owner decide. Role-based control grants access by job role, rule-based control applies a global condition to everyone, and attribute-based control decides from attributes of the user, resource, and context. Time-of-day restrictions and least privilege narrow access further.
Authentication and privileged access. Multifactor authentication requires evidence from at least two different factor categories: something you know, have, or are, or somewhere you are. Implementations include biometrics, hard and soft tokens, and security keys. Password practice covers length, complexity, reuse, expiration, and age, plus password managers and passwordless sign-in. Privileged access management controls powerful accounts with just-in-time permissions, password vaulting, and ephemeral credentials.
Exam scenarios ask which model, factor, or protocol fits, such as SAML versus OAuth, role-based versus rule-based, or a hard versus soft token.
This page is the map. Knotch is where you drill it until it sticks.
SAML answers who you are, using a signed assertion from the identity provider. OAuth answers what an app may do for you, using a limited token.
Role-based control groups permissions by job role. Rule-based control applies the same system-enforced conditions to everyone, such as admin access only from a jump host.
A hard token is a dedicated device, such as an OTP key fob or smart card, so it must be issued, tracked, and replaced. A soft token is software on a device the user already has, which is cheap but exposed to phone compromise and prompt abuse.
With mandatory control, the system and a central authority decide using labels. With discretionary control, the owner of the resource decides.
The full set of look-alike pairs for this objective is inside Knotch.
Administrators share a root password for production servers. The company wants each use to be approved and attributable to a person, and the password to change afterward.
Which tool BEST fits?
A vault ties each checkout to a person, rotates the secret and can record the session.
Vaults manage privileged and shared secrets with approval, rotation and recording, which makes shared accounts attributable to individuals.
Why not A: A stronger password is still shared, so uses cannot be tied to a person.
Why not B: This limits when the account can be used and does not identify who used it.
Why not C: SSO reduces logins to applications and does not rotate or check out a root password.
SSO is one login across applications. Federation is trust between organizations, and it often enables SSO.
The exam lists somewhere you are as a factor. NIST SP 800-63B-4 recognizes only knowledge, possession, and inherence, and treats location as context for risk-based decisions, so know both views.
No. MFA needs different factor types, and two knowledge questions are the same type.
