Exam Nuts & Bolts
- Multiple choice with only one answer correct (option buttons)
- Multiple choice with multiple possible correct answers
Topic Area Overview
- Business Units. Business units can be deleted in CRM 2011 under certain conditions, so be sure you know what those are. Make sure you are familiar with default teams for business units.
- Architecture Concepts, where and how to customize Dynamics CRM. Understand which customization options are different between Dynamics CRM Online and on-premise.
- System Settings. Understand the new system settings, such as currency precision, auditing, goals. Understand how Language settings work (on the Administration page), and how Currencies and Fiscal Year settings work (both on the Business Management page).
- Solutions. This is a big topic – I’ll cover it below.
- Security roles themselves work essentially the same in CRM 2011 as in CRM 4.0. But…there are so many new things to secure in CRM 2011 that there are a lot more options! For example, you can understand how the entity-based and task-based privilege model works, but if you don’t understand how in Dynamics CRM 2011 it’s applied to things like who can manage solutions, and who and how you can control access to charts and dashboards, and all the other new stuff, you’ll have a hard time with a lot of the questions on the test!
- Append and Append to. Just remember: if you don’t have append privilege on an entity you can’t append it to anything; if you don’t have append to you can’t append anything to it.
- Teams are a full-fledged security principal in CRM 2011. This is one of the most important improvements in the security model, and it’s well represented on the test. Make sure you know how to maintain teams, add users to teams, assign security roles to teams, when teams can be deleted and what the implications are, and so forth.
- Field Security is an important new feature and again well represented. Know what kinds of fields it can be applied to (custom fields only!), how it’s done, and who can do it.
- Maintaining user accounts is reasonably similar to how it was in CRM 4.0. Make sure you know what’s required to add users (e.g. you can add a user without a security role but not without a business unit), whether you can delete users (no), what happens to users if their business unit is disabled (they can’t access CRM but they still take up a license!), what happens to records owned by a user whose account is disabled (pretty much nothing), how to bulk reassign records, and the like.
- Option sets get a lot of coverage, and make sure you understand global option sets. For example, work through what happens if you use a global option set on forms for two different entities and change it from one of them.
- Make sure you have detailed knowledge of the different data types available for custom fields, and which field properties can be changed after saving a field.
- When you create a custom entity, which settings can be changed after saving and which cannot? If you define a new entity as an activity entity can you change your mind about that or about whether it’s displayed in the Activity Menus? (no and no). Can you change your mind about support for Notes, Activities, Connections, Sending e-mail, Mail-merge, Document Management or Queues? (no, no, no, no, yes, yes, no). How about Duplicate detection or Auditing? (yes and yes).
- Make sure you really understand the ins and outs and N:N relationships, especially the differences between native N:N’s and manual N:N’s using an intersection entity.
- Understand how Connections implement N:N relationships. (Connections are new in CRM 2011)
- Understand how you can access relationship properties (e.g., through form navigation – this is new in CRM 2011) and what you can customize once you get there (the difference between Parental, Referential, Referential (Restrict Delete) and Configurable Cascading – this is the same as in CRM 4.0)
- Know what mapping does and doesn’t do.
- Who can configure auditing?
- How do you configure audit partitions? Which ones can be deleted and when?
- What version of SQL Server (on-premise, of course!) do you need to configure audit partitions?
- Can auditing be turned on and off for an entity? If it’s on, which fields are audited by default? If it’s on, are schema customizations audited? (yes, all of them, and yes)
- How do you create multiple forms for an entity and what can they be used for? How are they assigned to security roles?
- What’s the difference between system-defined and public views? (same as in 4.0) Can public views be deactivated? (yes, new in 2011)
- Make sure you know the ins and outs of lookup, associated and quick find views.
- Can you export a chart’s XML definition file, modify it, and then import it? (yes) If so, what is that good for? (CRM can display multi-series charts, but the chart designer can’t create them, for example)
- Can you create a personal chart, export its XML definition file, and then import that as a system chart? (yes) If so, what’s that good for?
Implementing a Solution (13 percent)
When you consider that you get questions on this in other topic areas, it really means it accounts for more than 13% of the total questions. Plus it’s all new, so make sure you’re up to speed on topics like these:
- What are all the different components that can be part of a solution? Which of those components are form-enabled?
- What are the differences between managed and unmanaged solutions?
- When do you create a managed solution? (when you export it)
- What happens if you import several managed solutions on top of each other? How does conflict resolution work?
- How do solution versions work? What happens when you import a new version of an existing managed solution?
- What are managed properties for and where do you configure them? (they control whether somebody can customize components of a managed solution, but they are configured in the unmanaged solution!)
- You need drill-down detail knowledge about what the managed property options are for different components (e.g., entities, forms, views, fields and so forth), as well as for the differences between system entities and custom entities. Here’s an informal treatment of the subject: