mediummultiple choiceObjective-mapped

A company wants employees to sign in once to access several SaaS applications, but it also wants to require MFA only when users connect from unmanaged devices or outside the corporate network. Which architecture best supports this goal?

Question 1mediummultiple choice
Full question →

A company wants employees to sign in once to access several SaaS applications, but it also wants to require MFA only when users connect from unmanaged devices or outside the corporate network. Which architecture best supports this goal?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Create separate usernames and passwords for each SaaS application and disable browser-based token sharing.

This increases password sprawl and user friction. It does not provide single sign-on or conditional access based on device trust or location.

B

Best answer

Implement federated identity with single sign-on and conditional access policies tied to device posture and network location.

Federation lets the organization use one identity provider for multiple SaaS applications, which enables single sign-on. Conditional access then adds policy-based decisions such as requiring MFA for unmanaged devices or external access. This combination is both more secure and more user-friendly than separate credentials or blanket MFA for every sign-in.

C

Distractor review

Use local accounts in each SaaS application and rotate passwords every 30 days.

Local accounts prevent centralized identity control and make lifecycle management harder. Password rotation alone does not deliver SSO or adaptive access controls.

D

Distractor review

Grant all employees the same access role to simplify authentication and reduce support tickets.

A single broad role violates least privilege and does not address access policy based on device trust, location, or application need.

Common exam trap

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Technical deep dive

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SY0-701 question test?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: Implement federated identity with single sign-on and conditional access policies tied to device posture and network location. — Federated identity with SSO is the right architectural fit because it centralizes authentication while allowing SaaS applications to trust the organization’s identity provider. Conditional access adds context-aware enforcement, such as prompting for MFA when the sign-in comes from an unmanaged device or an outside network. That combination reduces password fatigue, improves administration, and gives the security team a consistent control point for policy enforcement. Why others are wrong: Option A creates fragmented authentication and does not support unified policy enforcement. Option C is operationally expensive and weak from a governance standpoint because every application becomes its own identity silo. Option D sacrifices least privilege and still fails to meet the required conditional access behavior. The selected architecture is the only one that satisfies both usability and security goals.

What should I do if I get this SY0-701 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.