Federation SSO and Automated Provisioning for Rapid Access Revocation
Employees must sign in to several SaaS applications with corporate credentials, and terminated users should lose access quickly without manual changes in each app. Which solution best meets the requirement?
Quick Answer
The answer is a combination of federation for single sign-on and automated provisioning and deprovisioning through an identity lifecycle process. This solution is correct because federation, using standards like SAML 2.0 or OIDC, allows employees to authenticate once with corporate credentials and access multiple SaaS applications, while automated provisioning and deprovisioning via SCIM ensures that terminated users lose access instantly across all apps without manual changes. On the Security+ SY0-701 exam, this question tests your understanding of identity and access management (IAM) concepts, specifically how federation SSO and automated provisioning work together to enforce rapid access revocation. A common trap is choosing only SSO without provisioning, which handles sign-on but not removal. Remember the mnemonic “FED-SCIM” — Federation for sign-on, SCIM for automated removal — to link the two components for exam success.
⚠ Common exam trap
Many candidates confuse federation with simple SSO, overlooking the automated provisioning/deprovisioning component that is essential for the 'lose access quickly' requirement, and instead pick a password-vaulting solution thinking it centralizes credentials.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use federation for sign-on and automated provisioning and deprovisioning through an identity lifecycle process.
Federation enables single sign-on (SSO) using standards like SAML 2.0 or OIDC, allowing users to authenticate once with corporate credentials across multiple SaaS apps. Automated provisioning and deprovisioning via SCIM (System for Cross-domain Identity Management) ensures that when an employee is terminated, their access is revoked from all connected applications instantly without manual intervention, meeting the requirement for rapid access removal.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create separate local usernames and passwords in each SaaS application.
Why it's wrong here
Separate local accounts increase password sprawl and make offboarding slow and error-prone. They do not support centralized identity control very well.
- ✓
Use federation for sign-on and automated provisioning and deprovisioning through an identity lifecycle process.
Why this is correct
Federation allows users to authenticate with the corporate identity provider, while automated provisioning helps create, update, and disable accounts across connected SaaS apps. This design supports single sign-on, faster offboarding, and centralized control over access lifecycle changes. It also reduces the risk of forgotten orphaned accounts remaining active after termination.
- ✗
Require users to share one department password for each SaaS platform.
Why it's wrong here
Shared passwords are insecure, impossible to attribute to one person, and difficult to rotate after staff changes. They also defeat individual accountability and auditing.
- ✗
Store the same password in every application vault and sync it nightly.
Why it's wrong here
Password synchronization still creates many credentials to manage and does not provide clean centralized authorization or offboarding. It also increases the impact of a compromise.
Go deeper
Related to this question
Learn chapter
Unified Threat Management (UTM)
Key term
Deprovisioning
Deprovisioning is the process of removing a user's access to systems and data when they no longer need it, typically when they leave an organization or change roles.
Key term
SAML
Security Assertion Markup Language (SAML) is an open standard that allows one system to securely tell another system that a user is who they say they are, without sharing the user's password.
About these practice questions
Courseiva writes every SY0-701 question from scratch — 1,013 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
3 more ways this is tested on SY0-701
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company uses several SaaS applications and wants employees to sign in once with a corporate account instead of maintaining separate passwords for each app. Which architecture is best?
easy- A.Shared generic accounts for each department.
- ✓ B.Federated single sign-on with a central identity provider.
- C.A separate username and password database in every SaaS application.
- D.A site-to-site VPN for every SaaS vendor.
Why B: Federated single sign-on (SSO) with a central identity provider (IdP) allows users to authenticate once using their corporate account (e.g., via SAML 2.0 or OIDC) and then access multiple SaaS applications without re-entering credentials. The IdP issues a token that each SaaS app trusts, eliminating the need for separate passwords while maintaining centralized control over authentication policies.
Variation 2. Employees use several SaaS applications, and the security team wants one corporate login, MFA for unmanaged devices, and centralized account provisioning. Which architecture should be used?
medium- A.Create separate usernames and passwords for each SaaS application.
- ✓ B.Use federated single sign-on with the corporate identity provider and conditional access policies.
- C.Share one generic account for the team so access is easier to audit.
- D.Put all users on a VPN and let each SaaS application trust the internal network automatically.
Why B: Federated single sign-on (SSO) with a corporate identity provider (IdP) allows users to authenticate once using their corporate credentials and access multiple SaaS applications without separate logins. Conditional access policies can enforce MFA specifically for unmanaged devices, and centralized account provisioning (e.g., via SCIM) ensures accounts are created, updated, and deprovisioned from a single directory. This architecture meets all three requirements: single corporate login, MFA for unmanaged devices, and centralized provisioning.
Variation 3. A company wants employees to sign in once to several SaaS apps, while the security team also wants to require extra verification when users sign in from unmanaged devices or unusual locations. Which two architecture changes best satisfy both requirements? Select two.
medium- ✓ A.Federate authentication to a central identity provider.
- ✓ B.Enable conditional access policies based on device posture and sign-in risk.
- C.Create separate passwords for each SaaS app so compromise is contained.
- D.Turn off MFA because single sign-on already reduces logins.
- E.Use shared generic accounts for contractors to simplify onboarding.
Why A: Federating authentication to a central identity provider (IdP) enables single sign-on (SSO) across multiple SaaS apps using standards like SAML 2.0 or OIDC. This allows employees to sign in once, while the IdP becomes a centralized point to enforce additional security controls.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SY0-701 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SY0-701 exam.