The answer is SAML 2.0 federation with trust relationships to the partner identity providers. This is the correct choice because SAML enables the supplier portal to accept authentication assertions from multiple external identity providers (IdPs) using signed XML tokens, eliminating the need to create separate local passwords for each partner. On the Security+ SY0-701 exam, this scenario tests your understanding of federated identity management, specifically how SAML handles cross-domain single sign-on when an organization must trust assertions from multiple, independent IdPs. A common trap is confusing SAML with OAuth or OpenID Connect—remember that SAML is designed for enterprise federation with XML-based assertions, while OAuth focuses on delegated API access. For the exam, think of SAML as the “trust broker” that lets a service provider accept login claims from any partner’s IdP without storing credentials locally. Memory tip: “SAML = Signed Assertions, Multiple IdPs, Local passwords avoided.”
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.
A supplier portal is browser-based and used by external partner companies. Each partner already has its own identity provider. The portal must trust assertions from those IdPs and avoid creating separate local passwords for each partner. Which integration is best?
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 the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use SAML 2.0 federation with trust relationships to the partner identity providers.
SAML 2.0 federation is the correct choice because it enables the supplier portal to trust assertions from multiple external identity providers (IdPs) without creating local passwords. SAML uses XML-based tokens signed by the partner's IdP, allowing the portal to accept authentication claims via a trust relationship, which directly meets the requirement of avoiding separate local credentials for each partner.
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.
✗
Use LDAP directory synchronization for all partner users.
Why it's wrong here
LDAP synchronization copies identities, but it does not provide the browser federation model described.
✓
Use SAML 2.0 federation with trust relationships to the partner identity providers.
Why this is correct
SAML is well suited to browser-based federation and signed assertions from external identity providers.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use NTLM pass-through authentication to each partner account.
Why it's wrong here
NTLM is not a modern federation method and is poorly suited to external partner integrations.
✗
Use PAP over TLS so the portal can collect partner passwords securely.
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse LDAP synchronization (which replicates accounts) with federation (which avoids storing accounts), or mistakenly think NTLM can be extended across organizational boundaries, when in fact NTLM is a legacy challenge-response protocol limited to a single Windows domain.
Detailed technical explanation
How to think about this question
SAML 2.0 federation works by establishing a circle of trust where the service provider (the portal) trusts assertions issued by partner IdPs. Each assertion is digitally signed using the IdP's private key, and the portal validates it with the corresponding public key exchanged during metadata configuration. In real-world deployments, partners often use different IdP products (e.g., Azure AD, Okta, PingFederate), and SAML's standardized metadata format (XML with entityID, certificates, and endpoints) allows seamless interoperability without custom integration per partner.
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 developer is choosing between AES-256 (symmetric) and RSA-2048 (asymmetric) for encrypting a large file that will be sent to a partner. Symmetric encryption is fast but requires key exchange; asymmetric is slower but solves the key distribution problem. A hybrid approach — encrypt the file with AES, encrypt the AES key with RSA — is standard. Questions like this test whether you understand when each approach applies.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this SY0-701 question in full detail.
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 SAML 2.0 federation with trust relationships to the partner identity providers. — SAML 2.0 federation is the correct choice because it enables the supplier portal to trust assertions from multiple external identity providers (IdPs) without creating local passwords. SAML uses XML-based tokens signed by the partner's IdP, allowing the portal to accept authentication claims via a trust relationship, which directly meets the requirement of avoiding separate local credentials for each partner.
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 →
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.
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.