Microsoft Dynamics 365 test (Intermediate)

Sample questions

5 sample questions from the Microsoft Dynamics 365 test, with the answers. Samples are taken out of the live test, so you will not meet these when you sit it.

1. A developer is trying to set up a custom entity hierarchy in Dynamics 365, but the child entity is not inheriting the correct data or access rights from the parent entity. What is the most likely cause of the issue?

   1. The entity hierarchy is not properly configured, and the child entity's ownership is set to 'User or Team Owned' instead of 'Organization Owned'.
   2. The entity hierarchy is not properly configured, and the child entity's ownership is set to 'Organization Owned' instead of 'User or Team Owned'.
   3. The entity hierarchy is not properly configured, and the parent entity's ownership is set to 'User or Team Owned' instead of 'Organization Owned'.
   4. The entity hierarchy is not properly configured, and the parent entity's ownership is set to 'Organization Owned' instead of 'User or Team Owned'.

   Answer: A. The entity hierarchy is not properly configured, and the child entity's ownership is set to 'User or Team Owned' instead of 'Organization Owned'.

   In Dynamics 365, when setting up entity hierarchies, the child entity must be marked as 'Organization Owned' to ensure proper inheritance and access control. If it is 'User or Team Owned', it may restrict access and break the hierarchy functionality.

2. You are tasked with customizing a form for the 'Account' entity in Dynamics 365 Customer Engagement. The form needs to be deployed to both test and production environments, and it must not be directly editable in these environments. What is the correct approach to achieve this?

   1. Use a managed solution to deploy the custom form to test and production environments, ensuring it is not directly editable.
   2. Use JavaScript web resources to build the form and deploy it as a separate component.
   3. Customize the form using Power Automate and deploy it through a cloud flow.
   4. Create the form directly in the test environment and manually copy it to production.

   Answer: A. Use a managed solution to deploy the custom form to test and production environments, ensuring it is not directly editable.

   In Dynamics 365, managed solutions are used for deploying customizations to test and production environments. This ensures that the customizations are not directly editable in those environments, which is a best practice. Unmanaged solutions are used during development, and custom forms should be created within a solution to maintain consistency and control.

3. In Microsoft Dynamics 365, how are one-to-many relationships implemented in the data model?

   1. The lookup column on the one side of the relationship.
   2. A separate intersect table used to link the entities.
   3. The lookup column on the many side of the relationship.
   4. A foreign key column defined on both entities.

   Answer: C. The lookup column on the many side of the relationship.

   In Dynamics 365, one-to-many relationships are implemented by adding a lookup column on the many side of the relationship. This lookup column points to the primary entity (the one side), enabling the relationship to be maintained within the data model. Many-to-one relationships are essentially the same as one-to-many, just viewed from the opposite side. Many-to-many relationships require an intersect table to link the two entities, and cascade behavior is configured per relationship.

4. A custom view is created in Dynamics 365 Customer Engagement to display the 'Account' table with the 'Primary Contact' field included. No filters are applied. What will the view display?

   1. The view will display only the 'Primary Contact' field and not the 'Account Name' field.
   2. The view will display all account records, and the 'Primary Contact' field will show the contact name associated with each account.
   3. The view will display only the 'Account Name' and 'Primary Contact' fields, but not the 'Account Number' field.
   4. The view will display all account records, but the 'Primary Contact' field will show the contact email instead of the contact name.

   Answer: B. The view will display all account records, and the 'Primary Contact' field will show the contact name associated with each account.

   When a custom view is created in Dynamics 365 Customer Engagement, it defines how data is displayed based on the configuration of fields, filters, and relationships. In this case, the view is set to display the 'Account' table, and the 'Primary Contact' field is included. The 'Primary Contact' field is a lookup field that references the 'Contact' table, and it will display the name of the contact associated with each account. Since no filters are applied, the view will display all account records, and the 'Primary Contact' field will show the associated contact name. Other options suggest different behaviors, such as displaying only specific fields, filtering records, or showing related data in a different format, which are not supported by the given configuration.

5. A support team has configured an SLA policy with a warning threshold of 2 hours and no escalation threshold. What will happen when the case reaches the 2-hour warning threshold?

   1. The SLA policy will trigger a warning and not escalate the case automatically.
   2. The SLA policy will not trigger any action unless the escalation threshold is reached.
   3. The SLA policy will automatically escalate the case when the warning threshold is reached.
   4. The SLA policy will trigger both a warning and an escalation when the warning threshold is reached.

   Answer: A. The SLA policy will trigger a warning and not escalate the case automatically.

   When an SLA policy is configured with a warning threshold but no escalation threshold, it will only trigger a warning (such as an email or in-app notification) when the warning threshold is reached. However, the case will not be escalated automatically unless the escalation threshold is also met. The SLA policy needs both a warning and an escalation threshold to trigger escalation.