mediummultiple choiceObjective-mapped

Employees sign in once to the corporate portal and then open email, the ticketing system, and an HR application without entering credentials again. The external SaaS providers should trust the company's identity provider rather than creating separate user databases. What architecture is being used?

Question 1mediummultiple choice
Full question →

Employees sign in once to the corporate portal and then open email, the ticketing system, and an HR application without entering credentials again. The external SaaS providers should trust the company's identity provider rather than creating separate user databases. What architecture is being used?

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

Local authentication on each application with synchronized passwords

This still requires each application to maintain its own identity store, even if passwords are synchronized. It does not create a shared trust relationship with the corporate identity provider.

B

Best answer

Federation with single sign-on using the corporate identity provider

Federation allows one organization to trust authentication performed by another identity provider. When combined with single sign-on, the user signs in once and then accesses multiple applications without repeated logins. This is exactly what the scenario describes, especially across separate SaaS services.

C

Distractor review

Network access control using 802.1X authentication

Network access control can verify device or user identity at the network edge, but it does not provide the application-level trust relationship described here. It also does not by itself create SSO across SaaS apps.

D

Distractor review

Role-based access control on the file server

RBAC controls what authenticated users can access, but it does not define how different applications trust one login event. The question is about authentication architecture, not authorization alone.

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: Federation with single sign-on using the corporate identity provider — Federation with SSO is the right answer because the company wants one authentication event to be accepted across multiple separate services. The corporate identity provider authenticates the user, and the SaaS applications trust that assertion instead of requiring their own separate logins. This reduces password sprawl and improves the user experience while still centralizing identity control. Why others are wrong: Option A still relies on multiple application-specific identity stores. Option C is a network admission control technology, not an application federation model. Option D affects authorization after login, but it does not explain the single sign-on trust relationship between the corporate identity provider and the SaaS platforms.

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.