Dynamics 365 Finance & Operations Technical Consultant

1. Explain the technical architecture of Dynamics 365 Finance & Operations. 2. Explain the role of X++ in D365 development. 3. What are Extensions and Chain of Command? 4. Explain Tables, Forms, Classes, Queries, and Data Entities. 5. What are Event Handlers and when would you use them? 6. Explain Batch Jobs and Batch Groups. 7. What are Data Entities and how are they used in integrations? 8. Explain OData and REST APIs in D365. 9. Explain synchronous and asynchronous processing. 10. How does D365 integrate with external systems and middleware? 11. A custom extension works in DEV but fails in Production. How would you troubleshoot it? 12. A batch job that normally runs for 30 minutes suddenly takes several hours. How would you identify the bottleneck? 13. An integration creates duplicate customer records. How would you prevent duplicate processing? 14. A Purchase Order is created but the expected financial transaction is missing. How would you trace the issue? 15. Inventory and General Ledger values are inconsistent. How would you determine whether the issue is functional or technical? 16. An external WMS intermittently fails to send inventory updates to D365. How would you perform root-cause analysis? 17. A requirement affects Finance, Procurement, Inventory, Sales, and WMS. How would you perform technical impact analysis? 18. How would you choose between configuration, extension, X++ development, and integration? 19. How would you design retry and error-handling logic for a high-volume interface? 20. A critical integration fails during month-end closing. Walk through your incident response and recovery approach. 21. How would you design reconciliation between D365 and an external warehouse system? 22. How would you identify whether a Production issue is caused by application logic, database performance, integration, or configuration? 23. What performance checks would you perform before approving a major D365 customization? 24. Explain how you would coordinate functional, technical, and integration teams during a Sev-1 incident.