mediummultiple choiceObjective-mapped

A manufacturer wants partner-company users to access a procurement portal using their own company identities. The manufacturer does not want to create local accounts for each partner user, but it still needs to control what those users can do in the portal. Which approach should be used?

Question 1mediummultiple choice
Full question →

A manufacturer wants partner-company users to access a procurement portal using their own company identities. The manufacturer does not want to create local accounts for each partner user, but it still needs to control what those users can do in the portal. Which approach should be 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

Create one shared partner account for each external company and reuse the same password.

Shared accounts remove individual accountability and make it hard to revoke one person without affecting everyone. They also create audit and least-privilege problems that are unacceptable for partner access.

B

Best answer

Use federated identity with role mapping so the portal trusts each partner’s identity provider.

Federation lets external users authenticate with their own identity provider while the manufacturer still controls authorization inside the portal. Role mapping converts trusted identity assertions into specific portal permissions, which avoids local account sprawl and simplifies offboarding at the partner side.

C

Distractor review

Synchronize every partner user into the manufacturer’s directory and require a separate password change.

Directory synchronization creates local identity copies that the manufacturer must manage. That adds overhead and undermines the goal of avoiding local accounts for external partner users.

D

Distractor review

Store partner passwords in the portal database and use password reset emails for access control.

Storing passwords in the portal is a poor architecture for external identity management. It also does not provide the same trust relationship, centralized authentication, or maintainable partner lifecycle control as federation.

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: Use federated identity with role mapping so the portal trusts each partner’s identity provider. — Federated identity with role mapping is the best fit because the manufacturer wants to trust the partner’s identity provider rather than create and maintain separate local accounts. The portal can accept signed assertions from each partner IdP and then map those identities to the correct privileges. That gives the manufacturer strong control over authorization while reducing account sprawl and simplifying partner onboarding and offboarding. Why others are wrong: Shared accounts break accountability and create major security risks. Synchronizing external identities into the manufacturer directory recreates the same administrative burden the company wants to avoid. Storing partner passwords locally is weak architecture and does not provide the trust and governance benefits of federation.

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.