Microsoft MB-500 Practice Test - Questions Answers, Page 14

To open the Performance timer, open your webpage with the added parameter debug=develop: https://yoursite.cloud.test.dynamics.com/en/?cmp=USMF&debug=develop

Reference: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/perf-test/performance-timer

Optimistic Concurrency only locks records from the time when the actual update is performed.

Following are the advantages of using OCC:

Records remain available for other processes to update if they have been selected from the database but haven't yet been updated.

Records are locked for a shorter length of time.

Fewer resources are used to hold the locks during the update process.

Incorrect Answers:

A: Pessimistic Concurrency Control locks records as soon as they are fetched from the database for an update.

E: One record can be selected for update by two different processes at the same time when using OCC.

Reference:

https://docs.microsoft.com/en-us/dynamicsax-2012/developer/optimistic-concurrency-control

The following illustration shows the elements of role-based security and their relationships.

Reference:

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/role-based-security

Step 1: Create a new user role and add required privileges.

Individual security permissions are combined into privileges, and privileges are combined into duties. The administrator grants security roles access to the program by assigning duties and privileges to those roles.

Step 2: Assign the newly created role to the user.

Step 3: Define the list of constrained tables.

Add the constrained tables and views.

Step 4: Define the context of the rule.

Set the context.

Set the ContextType property to one of the following:

ContextString – Set the property to this value if a global context is to be used to determine whether the policy should be applied. When required, this context string needs to be set by the application using the XDS::SetContext API.

RoleName – Set the property to this value if the policy should be applied only if a user in a specific role accesses the constrained tables.

RoleProperty – Set the property to this value if the policy is to be applied only if the user is a member of any one of a set of roles that have the ContextString property set to the same value.

Reference:

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/security-architecture

https://community.dynamics.com/365/b/exploringdynamics365/posts/extensible-data-security-in-d365

Box 1: Entire table

In Microsoft Dynamics AX, groups of records can be cached all at once with set-based caching. Set-based caching can be implemented in two ways:

At design time, by setting the table's CacheLookup property to EntireTable.

In code, by using the RecordViewCache class.

Box 2: Found

Record caching is enabled for a table when all the following statements are true:

The CacheLookup property on the table is enabled by setting it to one of the following values:

NotInTTS, Found, FoundAndEmpty.

The record buffer disableCache method has not been called with a parameter of true.

Reference:

https://docs.microsoft.com/en-us/dynamicsax-2012/developer/set-based-caching

https://docs.microsoft.com/en-us/dynamicsax-2012/developer/single-record-caching

Box 1: FoundAndEmpty

All selects on caching keys are cached, including selects that are not returning data.

All caching key selects are returned from caching if the record exists there, or the record is marked as nonexistent in the cache. A select forUpdate in a transaction forces reading from the database and replaces the record in the cache.

An example of FoundAndEmpty record caching is in the Discount table in the Microsoft Dynamics AX standard application. By default, the Discount table has no records. By using a FoundAndEmpty cache on this table, the keys that are queried for but not found are stored in the cache. Subsequent queries for these same non-existent records can be answered from the cache without a round trip to the database.

Box 2: NotInTTS

All successful caching key selects are cached.

When in a transaction (after ttsBegin), no caches made outside the transaction are used. When inside a transaction, the record is read once from the database and subsequently from the cache. The record is select-locked when reading in a transaction, which ensures that the record cached is not updated while the transaction is active.

A typical example of the NotInTTS property is on the CustTable in the Microsoft Dynamics AX application. It is acceptable to read outdated data from the cache outside a transaction, but when data is used for validation or creating references, it is ensured that the data is real-time.

Box 3: EntireTable Creates a set-based cache on the server. The entire table is cached as soon as at least one record is selected from the table. An EntireTable cahce is flushed whenever an insert, update or delete is made to the table. So first select read all records from DB for the selected company and all the further selects will take data from the cache instead of DB calls.

Box 4: Found All successful caching key selects are cached. All caching key selects are returned from the cache if the record exists there. A select forUpdate in a transaction forces reading from the database and replaces the record in the cache.

This is typically used for static (lookup) tables, such as Unit, where the record usually exists.

Reference:

http://gautamax.blogspot.com/2017/01/cache-lookup-property-of-table-in-ax.html

Step 1: Add the form object to the entry point node of a new privilege.

Your desired security privilege you can either directly set form control permissions or Entry Points.

For the Entry point method you need first need to add new entry point and set its object type and object name properties or for existing ones select desired entry point and click on drop down arrow and on controls right click and select new control, and now set its grant and name properties to desired control and its access rights.

Step 2: Add the privilege to a new duty

You need to assign this privilege in desired security role and security duty.

Step 3: Add the duty to the security role for sales managers.

Reference:

https://www.cloudfronts.com/set-form-control-access-via-security-role-in-d365-finance/