Difficulty: Hard
What does an ERP cutover control total help detect?
A Unapproved screen colors
B Slow staff onboarding
C Unassigned office space
D Missing or duplicated records
Answer: D. Missing or duplicated records. Control totals help reconcile record counts and financial amounts across migration.
Why test custom ERP changes after an upgrade?
A Catch regressions in workflows
B Avoid user review
C Remove standard controls
D Increase code volume
Answer: A. Catch regressions in workflows. Regression testing checks whether existing functions still work after change.
When one ERP role can create and pay suppliers, what risk exists?
A Forecasting bias
B Segregation-of-duties conflict
C Data compression error
D Inventory valuation mismatch
Answer: B. Segregation-of-duties conflict. Combining vendor setup and payment creates a control conflict.
Which control verifies a purchase before supplier payment?
A Single sign-on
B Cycle count
C Three-way match
D Data masking
Answer: C. Three-way match. A three-way match compares the order, receipt, and invoice.
What risk reduction can a phased rollout offer?
A Skip pilot feedback
B Remove rollback plans
C Switch every site together
D Limit initial scope and learn
Answer: D. Limit initial scope and learn. A phased rollout limits early exposure and allows lessons to guide later stages.
Why is big-bang cutover demanding?
A Many functions change simultaneously
B Old systems remain active forever
C Only one module is tested
D No data moves at once
Answer: A. Many functions change simultaneously. A big-bang cutover concentrates transition risk across many functions at once.
What must multi-country ERP localization handle?
A Only logo preferences
B Local tax and currency rules
C One global language always
D Identical labor laws everywhere
Answer: B. Local tax and currency rules. Localization addresses jurisdiction-specific requirements such as tax and currency.
Under SaaS ERP, who usually manages cloud infrastructure security?
A Customer’s delivery driver
B Public website visitor
C Cloud provider
D Every end user
Answer: C. Cloud provider. The provider generally secures the underlying infrastructure, while the customer retains other responsibilities.
Which recovery targets guide ERP continuity planning?
A BOM and MRP
B KPI and ROI
C SQL and HTML
D RTO and RPO
Answer: D. RTO and RPO. RTO and RPO describe recovery time and acceptable data loss.
What makes an ERP exit plan useful?
A Portable data and transition steps
B Proprietary formats only
C No export testing
D Permanent provider dependence
Answer: A. Portable data and transition steps. Exit planning addresses data export, transition, and replacement dependencies.
Why should an integration retry be idempotent?
A Skip authorization checks
B Avoid duplicate business effects
C Hide failed messages
D Increase duplicate invoices
Answer: B. Avoid duplicate business effects. Idempotency lets a repeated request avoid repeating the same transaction effect.
How should an ERP workflow handle an approval timeout?
A Ignore the waiting task
B Approve automatically without review
C Escalate through a defined route
D Delete the transaction
Answer: C. Escalate through a defined route. A timeout path makes overdue work visible to an authorized reviewer.
In MRP, which source error can create incorrect purchase plans?
A Accurate stock counts
B Verified lead times
C Approved production schedule
D Inaccurate bill of materials
Answer: D. Inaccurate bill of materials. Incorrect BOM quantities distort calculated component requirements.
Which process protects a shared master record from unauthorized edits?
A Master-data change approval
B Shared admin account
C Anonymous supplier login
D Unrestricted spreadsheet export
Answer: A. Master-data change approval. Approval controls ensure authorized changes to core shared data.
Stale ERP analytics mislead managers in what way?
A They prevent business delays
B Reports lag current transactions
C They guarantee real-time status
D They remove reconciliation needs
Answer: B. Reports lag current transactions. Analytics based on delayed extracts may not reflect current operations.
What can process mining reveal after ERP go-live?
A Only system font choices
B Employee intentions
C Actual workflow variants
D Unrecorded future plans
Answer: C. Actual workflow variants. Event logs can show how ERP processes actually execute.
Which cost is often overlooked in ERP total cost estimates?
A Unrelated office décor
B Customer gift cards
C Software logo design
D Data cleanup and migration
Answer: D. Data cleanup and migration. Data cleansing and migration can require substantial project effort.
What safeguards service continuity during an ERP outage?
A Tested recovery procedures
B Shared passwords
C Unapproved workarounds
D Deleted backups
Answer: A. Tested recovery procedures. Tested procedures clarify how service and data can be restored.
Why assess change impact before altering an ERP module?
A Modules never share data
B Connected processes may be affected
C Users cannot depend on ERP
D Reporting is unrelated
Answer: B. Connected processes may be affected. Integrated modules can create downstream effects when one component changes.
What risk grows when custom ERP code accumulates?
A Role clarity
B Upgrade simplicity
C Technical debt
D Data accuracy
Answer: C. Technical debt. Custom code can increase future maintenance and upgrade effort.
After ERP deployment, which review checks promised business benefits?
A Vendor newsletter review
B Screen layout inspection
C Password rotation report
D Benefits realization review
Answer: D. Benefits realization review. A benefits review compares actual performance with the business case.
What can master-data stewardship improve in ERP operations?
A Maintain consistent shared records
B Create untracked local copies
C Allow duplicate supplier IDs
D Bypass validation rules
Answer: A. Maintain consistent shared records. Stewardship keeps common records accurate and consistent across processes.
What should happen when an ERP interface field changes?
A Delete downstream validation
B Coordinate versioned integration updates
C Reuse old mappings blindly
D Change it without notice
Answer: B. Coordinate versioned integration updates. Coordinated version changes protect connected integrations from breaking.
Which approval practice helps prevent duplicate supplier payments?
A Removing payment logs
B Open vendor permissions
C Invoice duplicate detection
D Untracked manual posting
Answer: C. Invoice duplicate detection. Duplicate invoice controls flag repeated supplier invoices before payment.
How should ERP customization value be judged?
A Count lines of code
B Prefer every requested feature
C Ignore upgrade impacts
D Compare benefits with lifecycle cost
Answer: D. Compare benefits with lifecycle cost. A customization should justify its costs across implementation, support, and upgrades.