- A
Create separate local usernames and passwords in each SaaS application.
Why wrong: Separate local accounts increase password sprawl and make offboarding slow and error-prone. They do not support centralized identity control very well.
- B
Use federation for sign-on and automated provisioning and deprovisioning through an identity lifecycle process.
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.
- C
Require users to share one department password for each SaaS platform.
Why wrong: Shared passwords are insecure, impossible to attribute to one person, and difficult to rotate after staff changes. They also defeat individual accountability and auditing.
- D
Store the same password in every application vault and sync it nightly.
Why wrong: 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.
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.
SY0-701 Security Architecture Practice Question
This SY0-701 practice question tests your understanding of security architecture. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"best"Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
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.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may 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.
Detailed technical explanation
How to think about this question
Under the hood, federation relies on an Identity Provider (IdP) that issues signed assertions (e.g., SAML tokens) to Service Providers (SPs). Automated deprovisioning uses SCIM to push a 'deactivate' or 'delete' operation to each SP's user schema, often triggered by a lifecycle event in the IdP's directory (e.g., Active Directory or LDAP). In real-world scenarios, this integration is critical for compliance with regulations like SOX or HIPAA, where delayed access revocation can lead to audit failures.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A security analyst at a medium-sized enterprise encounters this scenario during an investigation or architecture review. The correct answer reflects best practice for the specific threat or control described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Security exam questions test whether you can match controls to threats in context — not just recall definitions.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Security Architecture — study guide chapter
Learn the concepts, then practise the questions
- →
Security Architecture practice questions
Targeted practice on this topic area only
- →
All SY0-701 questions
1,152 questions across all exam domains
- →
Security+ SY0-701 study guide
Full concept coverage aligned to exam objectives
- →
SY0-701 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SY0-701 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
General Security Concepts practice questions
Practise SY0-701 questions linked to General Security Concepts.
Threats, Vulnerabilities, and Mitigations practice questions
Practise SY0-701 questions linked to Threats, Vulnerabilities, and Mitigations.
Security Architecture practice questions
Practise SY0-701 questions linked to Security Architecture.
Security Operations practice questions
Practise SY0-701 questions linked to Security Operations.
Security Program Management and Oversight practice questions
Practise SY0-701 questions linked to Security Program Management and Oversight.
Security+ social engineering questions
Practise SY0-701 questions linked to Security+ social engineering questions.
Security+ cryptography practice questions
Practise SY0-701 questions linked to Security+ cryptography.
Security+ IAM questions
Practise SY0-701 questions linked to Security+ IAM questions.
Security+ risk management questions
Practise SY0-701 questions linked to Security+ risk management questions.
Security+ incident response questions
Practise SY0-701 questions linked to Security+ incident response questions.
Security+ malware questions
Practise SY0-701 questions linked to Security+ malware questions.
Security+ vulnerability management questions
Practise SY0-701 questions linked to Security+ vulnerability management questions.
Practice this exam
Start a free SY0-701 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SY0-701 question test?
Security Architecture — This question tests Security Architecture — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: 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.
What should I do if I get this SY0-701 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. 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: Option A is correct because 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.
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.