OpenID Connect is the correct choice for token-based mobile authentication because it is built on OAuth 2.0, providing ID tokens (JWTs) and access tokens that mobile apps can validate without browser redirects, while allowing employees to sign in with corporate credentials through a corporate identity provider. This eliminates separate app passwords and works seamlessly with modern REST APIs, making it ideal for mobile app scenarios where SAML’s browser-based redirects would break the user experience. On the Security+ SY0-701 exam, this question tests your understanding of federation protocols: SAML relies on XML-based assertions and browser redirects, whereas OpenID Connect is lightweight, JSON-based, and designed for mobile and API environments. A common trap is choosing SAML because it is older and more familiar, but remember that SAML requires a full browser session and does not natively issue access tokens for APIs. Memory tip: “OIDC for mobile, SAML for browser”—think of OIDC as the modern, token-friendly cousin of SAML.
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 SaaS vendor supports both browser access and a mobile app. The company wants employees to sign in with corporate credentials, avoid separate passwords for each app, and use token-based authentication that works well with modern APIs. Which integration should the architect choose?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
OpenID Connect federation with the corporate identity provider.
OpenID Connect (OIDC) is the correct choice because it is an identity layer built on top of OAuth 2.0, designed for token-based authentication that works seamlessly with modern REST APIs and mobile apps. It allows employees to sign in with corporate credentials via the corporate identity provider (IdP), eliminates separate app passwords, and issues ID tokens (JWT) and access tokens that the SaaS vendor can validate without browser redirects.
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.
✗
SAML federation to the SaaS vendor using browser assertions only.
Why it's wrong here
SAML is common for browser sign-in, but it is less aligned with modern API and mobile token flows.
✓
OpenID Connect federation with the corporate identity provider.
Why this is correct
OpenID Connect is built on modern token-based authentication and works well for browser, mobile, and API-driven applications.
Related concept
Read the scenario before looking for a memorised answer.
✗
LDAP bind authentication directly against each SaaS application.
Why it's wrong here
LDAP is not a modern SaaS federation method and would create separate authentication paths for each application.
✗
Kerberos tickets issued directly by the SaaS vendor.
Why it's wrong here
Kerberos is typically used in internal domain environments and is not the usual choice for external SaaS federation.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse SAML (which is browser-based) with OpenID Connect, assuming SAML can handle mobile apps and API tokens just as easily, but SAML lacks native support for token-based API authentication without complex extensions.
Detailed technical explanation
How to think about this question
OpenID Connect uses the authorization code flow with PKCE (Proof Key for Code Exchange) for mobile apps, ensuring secure token exchange without exposing client secrets. The ID token is a signed JWT containing claims like sub, iss, and aud, which the SaaS vendor can verify using the IdP's public keys (JWKS endpoint). In a real-world scenario, the mobile app redirects to the corporate IdP, the user authenticates, and the IdP returns an authorization code that the app exchanges for tokens, enabling seamless SSO without separate passwords.
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.
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: OpenID Connect federation with the corporate identity provider. — OpenID Connect (OIDC) is the correct choice because it is an identity layer built on top of OAuth 2.0, designed for token-based authentication that works seamlessly with modern REST APIs and mobile apps. It allows employees to sign in with corporate credentials via the corporate identity provider (IdP), eliminates separate app passwords, and issues ID tokens (JWT) and access tokens that the SaaS vendor can validate without browser redirects.
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.
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.