mediummulti selectObjective-mapped

A finance portal lets one employee create a payment batch and approve it without review. Management wants to reduce fraud risk while keeping the workflow functional. Which two changes best achieve that goal? Select two.

Question 1mediummulti select
Full question →

A finance portal lets one employee create a payment batch and approve it without review. Management wants to reduce fraud risk while keeping the workflow functional. Which two changes best achieve that goal? 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

Separate the create and approve functions into different roles or groups.

Splitting duties prevents one person from both initiating and authorizing the same financial action. This is a classic role-based control that limits fraud opportunities without removing the workflow itself.

B

Best answer

Require an independent approval step from a different account or manager before release.

A second approval creates a control point that verifies the transaction before funds are released. It preserves productivity while adding an accountability layer and reducing the risk of self-approved payments.

C

Distractor review

Give the same user broader administrative access to avoid delays.

More access increases the damage a mistake or malicious action can cause. The problem is not lack of power; it is the absence of separation and review.

D

Distractor review

Allow the same role to perform both actions but log the activity after the fact.

Logging alone is detective, not preventative. It may help investigation later, but it does not stop an unauthorized or fraudulent payment from being approved in the first place.

E

Distractor review

Remove authentication so the process is faster.

Eliminating authentication would severely weaken accountability and make fraud much easier. Speed is not a valid reason to remove access control from a sensitive financial workflow.

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: Separate the create and approve functions into different roles or groups. — The best controls are role separation and independent approval. Separating create and approve permissions prevents one person from completing the entire transaction alone, which is the core fraud risk. Requiring a different account or manager for approval adds a control point that keeps the process moving while enforcing least privilege and separation of duties. This is a practical access design, not just a policy statement. Why others are wrong: Expanding privileges or relying on logs after the fact does not prevent fraud. Removing authentication would make the system less secure and less accountable. The correct approach is to design the access workflow so no single person can create and approve the same payment without review.

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.