MB-310 Implement Financial Management Practice Question
A company is implementing a new Chart of Accounts (COA) and wants to ensure that specific main accounts cannot be used for direct manual entries. Which configuration should you use?
⚠ Common exam trap
Candidates often look for a security role restriction or a journal-level setting, failing to realize that the 'Do not allow manual entry' flag is a property of the Main Account itself.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable the 'Do not allow manual entry' option on the Main account.
By utilizing the 'Do not allow manual entry' checkbox on the Main account record, organizations can prevent users from directly coding journals to sensitive accounts, such as system-generated control accounts. This ensures that balances in accounts like Accounts Payable or Accounts Receivable are only updated through sub-ledger modules, maintaining a clear audit trail and preventing reconciliation discrepancies between sub-ledgers and the general ledger, which is vital for financial accuracy.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set the main account type to 'Total'.
Why it's wrong here
Account types defined as 'Total' are used for reporting aggregation in financial statements. While they do not accept direct postings, they are not the correct configuration to block manual entry for functional accounts that are otherwise active and used in sub-ledger processes.
- ✓
Enable the 'Do not allow manual entry' option on the Main account.
Why this is correct
This configuration specifically blocks direct manual journals to the account while allowing the system to post via sub-ledger integrations. It is the standard method for protecting control accounts from manual interference, which helps maintain the integrity of sub-ledger to general ledger reconciliation.
- ✗
Restrict the account via the Account structure setup.
Why it's wrong here
Account structures define which financial dimensions can be used with specific main accounts. While they can restrict usage, they do not differentiate between manual journals and sub-ledger postings. To specifically block manual entry, the setting on the main account record is required.
- ✗
Assign the account to a blank 'Legal entity override'.
Why it's wrong here
Legal entity overrides are used to configure account specific attributes like currency or validation rules per company. Leaving an override blank does not prevent manual postings; it simply applies the default settings to the account, which usually allows manual journal entries.
About these practice questions
This MB-310 question is part of Courseiva's 211-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This MB-310 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MB-310 exam.