Free Microsoft Dynamics MB-800 Actual Exam Questions - Question 11 Discussion
DRAG DROP A company uses Dynamics 365 Business Central. You need to configure the system to meet the following requirements for a purchasing agent:
• Create and post purchase documents including purchase receipt lines.
• Do not allow agents to read general ledger (G/L) or bank balances.
• Restrict access to view G/L amounts.
• Ensure that purchasing agents can select G/L codes on purchase documents.
You need to restrict access to view G/L amounts. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select. 
I think the key is to first create that permission set that explicitly denies reading G/L info, so the agents can’t see balances but still pick G/L codes when posting. Then you assign this new deny-read permission set to the purchasing agents, which restricts their access properly. Lastly, verifying or testing confirms everything works as intended with those restrictions. This approach ensures they keep posting capabilities without viewing sensitive G/L data. Skipping the deny-read permission set step wouldn't restrict access properly, so that’s a must-do first.
Agree with creating a new deny read G/L permission set first, then assign and verify.
Makes sense to create a new permission set denying G/L read first.
Start by creating a permission set denying G/L read, then assign it, and test access.
I’d start by modifying the existing purchasing permission set to block G/L read access, then assign this updated set to agents, and finally test to ensure purchase docs still allow selecting G/L codes without showing amounts.
I think starting by creating a new permission set makes sense so you don’t mess with existing roles. Then assign it to the agents and finally verify G/L amounts are hidden but G/L codes still selectable on purchase docs.
I’d say first create a new permission set limiting G/L read access, then assign it to purchasing agents, and finally verify they can still select G/L codes on purchase documents without seeing balances. That keeps things tight and functional.
I’d start by assigning a permission set that allows purchase posting but restricts G/L reading. Then, remove or limit access to G/L entries specifically. Trap option is usually giving full finance access-definitely not for this agent.