mediummulti selectObjective-mapped

A finance workflow currently lets one employee create a payment batch and approve it in the same session. Audit findings say the design increases fraud risk. Which two access architecture changes best reduce that risk while keeping the process functional? Select two.

Question 1mediummulti select
Full question →

A finance workflow currently lets one employee create a payment batch and approve it in the same session. Audit findings say the design increases fraud risk. Which two access architecture changes best reduce that risk while keeping the process functional? 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

Split the workflow into separate creator and approver roles.

Separating creator and approver responsibilities implements separation of duties and prevents one person from completing the full fraud-prone action alone. This preserves the workflow while requiring a second trusted person to review and approve the batch. It is a classic access architecture control for payment and procurement systems.

B

Best answer

Require the approver to be a different authenticated user before release.

A distinct authenticated approver ensures the system verifies that a second person performs the release step. This design supports accountability and makes it much harder for a single insider to both create and authorize a payment. It is practical because the business process still works, but the high-risk step gains independent review.

C

Distractor review

Grant all finance users local administrator rights to speed up exception handling.

Local administrator rights are unrelated to payment approval and would broaden privilege far beyond the business need. This would increase endpoint and application risk without addressing fraud controls. The problem is authorization separation, not lack of desktop permissions.

D

Distractor review

Store the payment password in a shared mailbox so the team can continue when someone is absent.

Sharing passwords or secrets breaks accountability and makes it impossible to know who approved a transaction. It also violates least privilege and creates a single point of compromise. The scenario needs independent approval, not credential sharing.

E

Distractor review

Remove approval steps entirely and rely on log reviews after payment runs.

Detecting fraud after the fact is not a substitute for preventing it through workflow design. Log reviews are useful, but they do not stop an unauthorized payment from being released. The audit finding calls for a structural access change, not a retrospective check only.

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: Split the workflow into separate creator and approver roles. — The correct choices are A and B. Splitting the workflow into creator and approver roles directly implements separation of duties, which is the key control for reducing payment fraud. Requiring a different authenticated user for the release step ensures the system verifies independent approval before money leaves the organization. This keeps the process functional while making misuse much harder. Why others are wrong: C expands privilege without addressing the fraud issue. D introduces shared credentials, which destroys accountability and weakens access control. E is too late in the process; it may help investigations, but it does not prevent an unauthorized transaction from happening.

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.