MB-920 · Question #153
A company implements Dynamics 365 Finance. You need to recommend a database logging strategy. Which two types of tables can you recommend for logging changes? Each correct answer presents a complete s
The correct answer is B. Transactional C. Document. Database logging in Dynamics 365 Finance is recommended for transactional and document tables because they hold business-critical records that require change auditing.
Question
Options
- AParameter
- BTransactional
- CDocument
- DBase Setup
How the community answered
(33 responses)- A3% (1)
- B91% (30)
- D6% (2)
Why each option
Database logging in Dynamics 365 Finance is recommended for transactional and document tables because they hold business-critical records that require change auditing.
Parameter tables hold system configuration settings that change infrequently, and enabling database logging on them generates excessive storage and performance overhead with minimal audit benefit.
Transactional tables store active business transaction records such as journal entries and purchase orders, and logging changes to them provides a complete audit trail of financial activity required for compliance and internal controls.
Document tables store business documents like invoices and contracts, and logging changes captures modifications to key business artifacts where traceability is essential for regulatory and operational audit purposes.
Base Setup tables contain foundational reference data that rarely changes and is not considered business-critical transactional activity, making database logging on these tables an inefficient use of logging resources.
Concept tested: Dynamics 365 Finance database logging table type selection
Source: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/configure-manage-database-log
Topics
Community Discussion
No community discussion yet for this question.