An organization is planning a new Dynamics 365 Finance + Operations (on-premises) implementation. The business process demands a huge volume of transactions to be imported during peak hours. Users…

Question

Options

• Auser profile management
• Bbusiness process optimization
• Cdeadlock log evaluation
• Dcrash dump analysis
• Etransaction characterization

• A
  71% (32)
• B
  4% (2)
• C
  18% (8)
• D
  7% (3)

Explanation

Hardware sizing for D365 F&O on-premises depends on understanding the workload the hardware must support. User Profile Management (A) is critical because it defines how many concurrent users exist, what roles they perform, and how frequently they interact with the system - this directly determines CPU, memory, and network requirements. Transaction Characterization (E) involves profiling the types, complexity, and volume of transactions (especially during peak import hours) to determine AOS server capacity, database throughput, and storage IOPS requirements. Business process optimization (B) is a functional improvement activity, not a sizing input. Deadlock log evaluation (C) and crash dump analysis (D) are post-deployment troubleshooting techniques, not pre-implementation sizing factors.

No community discussion yet for this question.