200+ Interview QA
SURE SUCCESS
Sanjaya Prakash Pradhan (MCT)
Softchief Learn
1
,1. Tell me about yourself.
I am a Microsoft Dynamics 365 Consultant and having 3 years of experience working in Dynamics 365 Customer
Engagement Platform. I have worked in many areas of Dynamics 365 such as modules like Sales, Services and
Marketing with Configurations and Customization.
NOTE: If you have more experience modify the statement. Specify some related technologies if you have worked on
such as C#.NET, SQL, Power BI etc.
2. Which project you have worked last and what was your role?
My last project was a Dynamics 365 CE implementation where we have implemented all required business process
of Student Management System. In this project my role was Techno-functional consultant and I have configured
Workflows, Business Process Flows, Customized Existing and Created New Entities. Also configured Business Rules,
Charts, Dashboards, Forms, Views etc.
NOTE: If you have practically worked on explain more.
3. What you know about Azure and explain a bit how it works in context of Dynamics 365?
Microsoft Azure, commonly referred to as Azure, is a cloud computing service created by Microsoft for building,
testing, deploying, and managing applications and services through Microsoft-managed data centers. We can
create Logic Apps, Web-hooks and Azure functions that can be called from Dynamics 365 Application. We can also
provide authentication for Dynamics 365 to communicate with Azure by creating Client ID by registering the
application.
NOTE: If you have practically worked on explain more otherwise tell that you have not practically worked on Azure
areas.
4. What is a Logic app in Azure for Dynamic 365?
Azure Logic Apps is a cloud service that helps you schedule, automate, and orchestrate tasks, business processes,
and workflows when you need to integrate apps, data, systems, and services across enterprises or organizations.
Logic Apps simplifies how we design and build scalable solutions for app integration, data integration, system
integration, enterprise application integration (EAI), and business-to-business (B2B) communication, whether in the
cloud, on premises, or both. We write Logic Apps to communicate Data from other data sources with Dynamics 365.
NOTE: If you have practically worked on explain more otherwise tell that you have not practically worked on this
area.
5. Explain Dynamics 365 CE/ CRM Data Migration Steps and Challenges
Dynamics 365 Migration involves many steps to ensure consistent data migration.
Let’s have a look about all the steps below.
Evaluate: This is the first step of the process where we evaluate the intent of data migration and define a Scope for
the data we are trying to migrate.
Plan & Analyze: defining the strategy for data migration is the key to the migration to be successful.
2
, Extract: define and perform the Data Extraction from different data sources, you may or may not use a Staging
Database.
Clean: data cleanup is a continuous process and while it should be happening in parallel with all other steps, this
stage is the last opportunity to clean the data before loading it in D365.
Load: In this stage, we execute the process to move the data into Dynamics 365, This requires a lot of planning and
prep to minimize the impact on the users and maintain business continuity.
Verify: like cleanup, data validation is a continuous process as well, validation is required when data is being
extracted to ensure all the requisite data is accounted for, validation is required during cleanup to ensure relevant
data is not being removed and at the end, validation is required to ensure data has been loaded correctly.
Regarding the challenges, you can explain if you have faced any challenges otherwise you can tell you have not
faced any challenges.
6. How Integrations works in CRM and how to send data to external systems and how to consume external
data in Dynamics 365 CRM system.
Dynamics 365 allows integrations with a number of native and external third party applications. Using Data
Connectors in Power Automate we can easily synchronize data between Dynamics 365 with many other external
applications such as LinkedIn, Salesforce etc. Custom web applications can be registered in Azure with Client ID for
reading the online Dynamics 365 Data using Web API technology. We can also create custom components by using
Dynamics 365 assemblies to communicate with the D365 Data. Azure provides Logic Apps by using which we can
integrate other business applications data with Dynamics.
NOTE: If you have practically worked on explain more.
7. What are Dynamics 365 Portals?
Using Dynamics 365 Portals we can extend Dynamics 365 interaction to external and internal audiences such as
customers, partners, and employees. We normally use portals to set up an interactive, web-based sales, services,
support, and social engagement application platform to connect with customers, engage with communities,
manage site content, and empower business channel partners. It empowers anyone inside or outside your
organization to interact with Common Data Service or Dynamics 365 data by using portals.
NOTE: If you have practically worked on explain more.
8. How to hide buttons in D365 Portals?
In Dynamics 365 Portals we can show/hide buttons from navigation by making changes on the Web links
component of Dynamics 365 Portal App. Open Portal App and go to Web links and do the changes with the links,
you can add new or update existing links.
NOTE: If you have practically worked on explain more.
9. Explain life-cycle of Sales, Marketing, Services, Field Service(FS), Project Service Automation(PSA)
The Life cycle of all explained below with all standpoints that you can explain to the interviewer. Normally
interviewer ask to explain a single module life cycle.
Sales Life Cycle:
The Sales Life cycle starts with Lead and Ends with Invoice. The diagram represents the entities.
3
, Marketing module life cycle
Marketing module life cycle starts with a marketing list and ends with response activities.
Services module life cycle
Services module life cycle starts with a case or incident and ends with case resolution through entitlement, SLA,
queues etc.
4