mediummultiple choiceObjective-mapped

An organization is redesigning access for a finance application. Employees should be able to approve expense reports only within their assigned job roles, and every approval must be traceable to the individual user who performed it. Which access model best fits this requirement?

Question 1mediummultiple choice
Full question →

An organization is redesigning access for a finance application. Employees should be able to approve expense reports only within their assigned job roles, and every approval must be traceable to the individual user who performed it. Which access model best fits this requirement?

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

Mandatory access control, because a central authority labels each expense report by sensitivity.

MAC is driven by centrally assigned labels, but the scenario is about business roles and auditability, not classification labels.

B

Best answer

Role-based access control, because permissions are assigned by job function and tied to named users.

RBAC matches a finance workflow where users inherit permissions based on job roles such as approver, reviewer, or auditor. It is easy to administer, supports least privilege, and works well when access should be consistent for groups with similar duties. The requirement to trace approvals to individuals is also satisfied when each person uses a unique account and actions are logged.

C

Distractor review

Discretionary access control, because individual employees decide who can approve expenses.

DAC lets resource owners share permissions at their discretion, which is less controlled than the role-driven model described.

D

Distractor review

Rule-based access control, because approval rights are determined only by the time of day.

Rule-based access can enforce conditions, but the question focuses on job-based assignment rather than conditional timing rules.

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: Role-based access control, because permissions are assigned by job function and tied to named users. — Role-based access control is the best fit because the organization wants permissions tied to job function rather than to individual discretion or data labels. In a finance application, roles such as requester, approver, and auditor can each receive only the access they need. Unique user accounts and logging then provide accountability for each approval action, which satisfies the traceability requirement without granting unnecessary privileges. Why others are wrong: MAC is for centrally labeled data and is not the best match for job-based permissions. DAC gives individual owners too much freedom to share access informally. Rule-based access can enforce conditions, but time or location rules are not the main need here. The core requirement is predictable permissions based on employee role, which points directly to RBAC.

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.