MB2-716 Microsoft Dynamics 365 Customization and Configuration Flashcards
81059AE: Customization in Microsoft Dynamics 365 for Sales and Customer Service; 81060AE: Configuration in Microsoft Dynamics 365 for Sales and Customer Service
Which of the following would be considered an unsupported customization?
Answers:
Adding a custom entity using the Dynamics 365 user interface.
Creating a new form for entering data.
Editing an existing view in the application.
Deleting a field directly from the SQL database.
Creating a dashboard containing multiple objects.
Which of the following would be considered an unsupported customization?
Answers:
Adding a custom entity using the Dynamics 365 user interface.
Creating a new form for entering data.
Editing an existing view in the application.
- Deleting a field directly from the SQL database.
Creating a dashboard containing multiple objects.
Correct. You are not under any circumstances allowed to modify the Dynamics 365 databases directly. All customizations must be done through the Dynamics 365 user interface.
Which of the following is not a Dynamics 365 process?
Answers:
Workflows
Custom Actions
Dialogs
Business Process Flows
Plugin
Which of the following is not a Dynamics 365 process?
Answers: Answers:
Workflows
Custom Actions
Dialogs
Business Process Flows
- Plugin
Correct. Dynamics 365 provides the ability to create several different types of processes including Workflows, Custom Actions, Dialogs, and Business Process Flows.
Which of the following statements about the Dynamics 365 Client for Outlook is not true?
Answers:
You must always be connected to Dynamics 365 (no offline capabilities).
Dynamics 365 contacts can be synchronized with Outlook contacts.
You can work with Dynamics 365 lists, forms, and other items directly from within Outlook.
You can track e-mails as Dynamics 365 activities.
Which of the following statements about the Dynamics 365 Client for Outlook is not true?
Answers:
- You must always be connected to Dynamics 365 (no offline capabilities).
Dynamics 365 contacts can be synchronized with Outlook contacts.
You can work with Dynamics 365 lists, forms, and other items directly from within Outlook.
You can track e-mails as Dynamics 365 activities.
Correct. The Dynamics 365 Client for Outlook provides the ability to synchronize Dynamics 365 contacts, tasks, and appointments with Outlook, as well as direct access to Dynamics 365 lists and forms. It also provides the ability to track emails received in Outlook as Dynamics 365 activities. Organizations can install the Outlook Client with offline access to provide users the ability to work offline.
You accidentally imported an unmanaged solution into your environment that contains a custom entity, a process, and a custom security role. The solution and all of its components need to be deleted. How would you do this?
Answers:
Delete the solution which will remove all the components.
Remove the components from the solution.
Unmanaged solutions cannot be deleted.
Delete the solution then manually remove each of the three components.
You accidentally imported an unmanaged solution into your environment that contains a custom entity, a process, and a custom security role. The solution and all of its components need to be deleted. How would you do this?
Answers:
Delete the solution which will remove all the components.
Remove the components from the solution.
Unmanaged solutions cannot be deleted.
*Delete the solution then manually remove each of the three components.
Correct. Removing a component from the solutions does not delete them from the system. It only removes them from the solution container. When you import an unmanaged solution, all the components in the solution are added to the new organization. When you remove an unmanaged solution you are only removing the container. All the components in the solution must be manually deleted individually.
Which of the following statements about Managed solutions are true? (Mark all that apply)
Answers:
All solutions start as managed.
Managed solutions can NOT be modified directly.
Managed solutions cannot be exported.
When removed all components items included are removed.
Which of the following statements about Managed solutions are true? (Mark all that apply)
Answers:
All solutions start as managed.
- Managed solutions can NOT be modified directly.
- Managed solutions cannot be exported.
- When removed all components items included are removed.
Every solution starts out as an unmanaged solution, it does not become a managed solution until it is specifically exported as a Managed solution.
Which of the following statements are true about entity Assets? (Mark all that apply)
Answers:
Assets can only be added when you first add an entity to a solution.
System entities will have all assets selected by default.
Assets can be added to an entity at any time.
Custom entities will have all assets selected by default.
Which of the following statements are true about entity Assets? (Mark all that apply)
Answers:
Assets can only be added when you first add an entity to a solution.
System entities will have all assets selected by default.
- Assets can be added to an entity at any time.
- Custom entities will have all assets selected by default.
Entity Assets allow you to only include the specific items needed for your solution to function. They help to prevent accidently overriding customizations made by other people. You can add assets to any entity at any time and custom entities will include all Assets by default, where system entities, will not include any assets and you will have to manually specify the assets to include.
What field requirement should you configure on a field to ensure that a user must enter a value?
Answers:
Mandatory
Compulsory
Business Recommended
Business Required
Audited
What field requirement should you configure on a field to ensure that a user must enter a value?
Answers:
Mandatory
Compulsory
Business Recommended
- Business Required
Audited
The field requirement field controls the requirement level of a field. Fields can be set to Optional, Business Recommended, or Business Required.
Which of the following properties cannot be changed after you save a field?
Answers:
Field Security
Display Name
Data Type
Auditing
Which of the following properties cannot be changed after you save a field?
Answers:
Field Security
Display Name
- Data Type
Auditing
After a field is saved for the first time, you are unable to modify the field’s name, data type, or field type. You can change things like the Display Name, Field Security, and Auditing at any time.
You created a custom entity with forms and views, and published all your customizations. You can see it but no other users can. Which of the following is most likely the cause?
Answers:
You forgot to set the managed properties.
You did not configure relationships.
You did not set security roles to allow access to the entity.
You set ownership to organization owned instead of user/team owned.
You created a custom entity with forms and views, and published all your customizations. You can see it but no other users can. Which of the following is most likely the cause?
Answers:
You forgot to set the managed properties.
You did not configure relationships.
- You did not set security roles to allow access to the entity.
You set ownership to organization owned instead of user/team owned.
By default, only the System Administrator security role has access to a custom entity when it is created. You must individually define the necessary privileges and access levels for every security role that will require access to the entity.
Which of the following entity properties cannot be turned off once they have been enabled?
Answers:
Access Teams
Document Management
Queues
Allow for Quick Create.
Which of the following entity properties cannot be turned off once they have been enabled?
Answers:
Access Teams
Document Management
- Queues
Allow for Quick Create.
Many entity properties can be turned on and off as needed, however there are specific entities properties that cannot be disabled after they have been enabled. These include Queues, Connections, Activities, and Business Process Flows.
You create a simple field called total value. It multiple two fields on the entity together. You want to the field populate the value automatically. How can you do this?
Answers:
Change the field type from simple to calculated.
Delete the field and recreate it as calculated.
Change the field type from simple to rollups.
Delete the field and recreate it as rollup.
You create a simple field called total value. It multiple two fields on the entity together. You want to the field populate the value automatically. How can you do this?
Answers:
Change the field type from simple to calculated.
- Delete the field and recreate it as calculated.
Change the field type from simple to rollups.
Delete the field and recreate it as rollup.
There is no way to convert an existing simple field to a calculated field. You can only define a field as calculated when you create it. They only way you could make an existing field calculated would be to first delete the field and recreate it as a calculated field.
Which of the following is not a field security permission that can be granted?
Answers:
Read
Append
Create
Update
Which of the following is not a field security permission that can be granted?
Answers:
Read
- Append
Create
Update
Append is an entity permission not a field security permission. The available privileges for field security are Read, Create, and Update. They can each be defined independently.
Which of the following statements about rollup fields in Dynamics 365 are true? (Mark all that apply.)
Answers:
You can have a maximum of 10 rollups per entity.
Rollups fields values can be Audited.
Rollup fields can’t be included in other rollup fields.
Rollup fields can’t include Hierarchy Data.
Which of the following statements about rollup fields in Dynamics 365 are true? (Mark all that apply.)
Answers:
- You can have a maximum of 10 rollups per entity.
Rollups fields values can be Audited.
- Rollup fields can’t be included in other rollup fields.
Rollup fields can’t include Hierarchy Data.
You are limited to a maximum of 10 Rollup fields per Entity and a Maximum of 100 per organization. On Premise deployments can modify this but online cannot. A roll up field cannot include other rollups.
Which of the following is true about Status and Status Reason fields for a custom entity?
Answers:
The Status field is added by default, you must add a Status Reason field if you want to use it.
You can customize the Status labels and add more options to meet your requirements.
Status and Status Reason fields are only used with system entities.
You can customize the Status Reason labels and add more options to meet your requirements.
You can add more options to the Status Reason but you cannot modify the default options.
Which of the following is true about Status and Status Reason fields for a custom entity?
Answers:
The Status field is added by default, you must add a Status Reason field if you want to use it.
You can customize the Status labels and add more options to meet your requirements.
Status and Status Reason fields are only used with system entities.
- You can customize the Status Reason labels and add more options to meet your requirements.
You can add more options to the Status Reason but you cannot modify the default options.
Each entity system and custom entity will have a Status and a Status Reason field. The Status field cannot be customized, but the Status Reason field can be customized including the ability to add and edit Status Reasons associated with specific statuses.
Which of the following is not a supported relationship type in Microsoft Dynamics 365?
Answers:
One to many
Many to one
Any to any
Many to many
Which of the following is not a supported relationship type in Microsoft Dynamics 365?
Answers:
One to many
Many to one
- Any to any
Many to many
Dynamics 365 supports two relationship types. One to many and Many to Many. A Many to One relationship is a One to Many relationship viewed from the other side which Dynamics 365 does allow you to do.
If you have a 1:N relationship between two entities – Event and Booking – and need all Bookings to be deleted automatically when an Event is deleted, which relationship behavior must you choose?
Answers:
Parental
Referential
Referential, Restrict Delete
Delete Child
If you have a 1:N relationship between two entities – Event and Booking – and need all Bookings to be deleted automatically when an Event is deleted, which relationship behavior must you choose?
Answers:
- Parental
Referential
Referential, Restrict Delete
Delete Child
Parental sets all the cascading rules to Cascade all. In this case it would delete all Bookings that are attached to specific event.
You have created a custom entity called Events. From a parent event, you want to view Hierarchical data (sub-events) associated with the parent. Which of the following items are required to view Hierarchical (Mark all that apply)
Answers:
Create a self-referential relationship on the Event entity
Enable hierarchy relationships on the Event entity properties
Define the hierarchy in the event entity’s hierarchy settings
Mark the relationship as hierarchical
You have created a custom entity called Events. From a parent event, you want to view Hierarchical data (sub-events) associated with the parent. Which of the following items are required to view Hierarchical (Mark all that apply)
Answers:
- Create a self-referential relationship on the Event entity
Enable hierarchy relationships on the Event entity properties
- Define the hierarchy in the event entity’s hierarchy settings
- Mark the relationship as hierarchical
When you want to work with hierarchical data, you much first create a self- referential relationship on the entity you want. That relationship needs to be defined as a hierarchical relationship (Check Box on the relationship). You then must define the details about the hierarchy in the Entities’ hierarchy settings.