Module 16: Security Basics

Justification:

1. A system administrator is a role. Therefore, being a system administrator does not represent a privilege.
2. Canceling a payment represents permission to perform a specific task in the system. This is a privilege.
3. Managing system security represents a duty. It encompasses many permissions or tasks.
4. Processing deposits also represents a specific task. Permission to perform this task is defined by a privilege.

Related Lesson: Security Architecture Overview

Justification:

1. True: This statement is true. Every user needs at least one security role assigned to them in order to access Dynamics AX. For example, system user. A user may have multiple roles assigned to them as well.

Related Lesson: Security Architecture Overview

Justification:

1. The needed permissions property is hierarchy, with read being the weakest and delete being the strongest. Each level encompasses the permissions below it; therefore, create access implies more than only create.
2. The needed permissions property is hierarchy, with read being the weakest and delete being the strongest. Each level encompasses the permissions below it. In order to create, you must also have access to update.
3. The needed permissions property is hierarchy, with read being the weakest and delete being the strongest. Each level encompasses the permissions below it; therefore, create access also implies read and update access.
4. The Create permissions does not allow Delete. The Delete permission is higher in the hierarchy.

Related Lesson: Security Architecture Overview

Justification:

1. False: This statement is false. Roles are not specific to a company or organization. The administrator can still specify a company or organization context for a particular user in a role, however.

Related Lesson: Security Architecture Overview

Justification:

1. A role can be assigned privileges, which are permissions to perform certain tasks. For example, a system administrator role can have a permission to add users.
2. Roles cannot be assigned to roles. However, a user may have multiple roles.
3. Configuration Keys are not assigned to a role; they are used to enable or disable certain features for all users.
4. A duty can also be assigned to a role. A duty corresponds to a business process and can also contain privileges.

Related Lesson: Security Architecture Overview