Practice assessments

These questions test understanding. They are self-assessments, not a controlled examination or professional certification.

Foundation questions

1. An item was created successfully, but its warehouse stock is zero. What should you investigate?
2. A field has no maxLength declaration in the interface. Can you promise it accepts unlimited text?
3. Why might a cashier see fewer screens than an administrator?
4. A customer paid, but an invoice remains open. What distinction should you check?
5. A company has configured periods, but the journal date is outside all of them. What does the reviewed guard do?
6. What is the difference between blank Discount on MRP and a value of zero?
7. Does choosing Hold approve a document?
8. Does leaving the till close the register?
9. Does posting payroll prove the employees have been paid?
10. Why should an AI answer include the source page and product version?

Model explanations

1. Creating the master does not receive stock. Check the receipt/opening workflow, stock-tracking choice, company, warehouse, and posting/movement result.
2. No. Server validation, storage, and request-size limits can differ. The reference should say that no explicit interface maximum was found.
3. Menu visibility depends on permissions and relevant configuration. Action permissions remain separately enforced.
4. A receipt and its allocation to an invoice are separate records of business meaning. Check the partner, currency, and allocation result.
5. It refuses posting when a configured calendar has no period covering the date. An entirely unconfigured calendar is handled differently.
6. Blank means no configured MRP-discount pricing choice. Zero is an explicit zero-percent discount; it can therefore select a different pricing path.
7. No. Hold leaves the request open and blocking. Ask and Watch also do not make an approval decision.
8. No. Leave keeps the shift open. End shift and close register is a separate action with counting/reconciliation.
9. No. Calculation, approval, posting, and actual payment are separate facts.
10. Software behavior changes, and the academy distinguishes verified details from extracted or unresolved content. A source lets the reader check the claim.

Practical assessment rubric

Criterion	Evidence required
Correct context	Company, period, role, and relevant master records identified
Correct entry	Inputs and units match the intended demonstration event
Controlled action	Required approval/status/posting sequence followed
Result verification	Saved document and applicable report effects inspected
Exception handling	Failure or discrepancy recorded without inventing success
Explanation	Learner explains why the result occurred

An assessor should review evidence rather than awarding completion for clicking through pages. Future formal assessment needs controlled question banks, versioned rubrics, identity checks, appeals, and a credential policy.