hardmulti selectObjective-mapped

Exhibit

IAM review notes:
- HR updates job changes in the HR system
- SaaS apps maintain separate local accounts
- Deprovisioning is manual and often delayed
- Users keep permissions from their previous role

After employees transfer departments, they keep access to old SaaS applications because app-specific accounts are removed only after a manual cleanup ticket. Which two changes best close the lifecycle gap? Select two.

Question 1hardmulti select
Full question →

After employees transfer departments, they keep access to old SaaS applications because app-specific accounts are removed only after a manual cleanup ticket. Which two changes best close the lifecycle gap? Select two.

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

Best answer

Use automated provisioning and deprovisioning tied to HR events through SCIM or an equivalent interface.

Automated lifecycle integration reduces delay and human error when employees change roles or leave. When HR events drive account updates, access can be removed or adjusted promptly across connected applications.

B

Distractor review

Keep app accounts manually managed so each app owner can decide independently.

Manual management is slower and often leaves orphaned accounts behind. It also creates inconsistent deprovisioning across applications, which is exactly the problem in the scenario.

C

Best answer

Map entitlements to IdP groups or roles based on job function.

Role-based group mapping makes access easier to update when a person changes jobs. Changing group membership in the IdP can update many downstream permissions at once instead of editing each app separately.

D

Distractor review

Share a generic help desk password for quick access restoration.

Shared credentials destroy accountability and make it impossible to tell who performed a change. They also do not solve the access-lifecycle problem; they only create another risky access path.

E

Distractor review

Require password changes every 30 days for all users.

Password resets do not remove outdated application entitlements or inactive accounts. A user can still keep inappropriate access even after changing a password, so the lifecycle gap remains.

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 automated provisioning and deprovisioning tied to HR events through SCIM or an equivalent interface. — The best fixes are to automate account lifecycle actions from HR and to assign access through role or group membership. SCIM-style automation reduces delay when a person changes departments or leaves. Group-based entitlements let administrators update access centrally instead of adjusting every application separately, which is faster, more consistent, and less likely to leave stale permissions behind. Why others are wrong: Manual app ownership and shared passwords both increase risk rather than reduce it. Password changes do not remove access rights. The key issue is not authentication alone; it is keeping authorization aligned with the user’s current job role and employment status.

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.