Microsoft MB-300 Practice Test - Questions Answers, Page 35

Box 1: active periods

Active batch periods

With the release of Platform update 21, an additional level of control over when batch jobs execute is now available. Previously, it was only possible to schedule a batch job to execute every hour for a specified number of hours or until a given date. Administrators can now provide information for an additional active period, such as in the following scenarios:

Specifying time ranges during which jobs within a batch group can start execution.

Selecting to run batch jobs outside of office hours only.

Setting the recurrence for anytime within the active period. For example, you administrator might select to run the batch jobs every hour, but only between the hours of 6:00 PM and 8:00 AM.

Box 2: scheduling priority

In Platform update 31, you can turn on the Batch priority-based scheduling feature in Feature management. Priority-based scheduling decouples batch groups from the batch server and allows you to define priorities for batch groups. It is no longer necessary to assign batch jobs to batch servers. Instead, relative scheduling priorities based on business requirements are used to determine the order in which tasks are run across available batch servers.

Box 3: alerts Alerts form a notification system for critical events in finance and operations. You can use alerts to stay informed about events that you want to track during the workday. You can set up a set of alert rules so that you're alerted when a batch job ends, ends in error, or is canceled. You can select whether the alerts are emailed to you or appear as notifications in the Action center. Alerts can be set up per batch job and per user.

Reference: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/devitpro/sysadmin/activeperiod

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/priority-basedbatch-scheduling

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/alerts

Box 1: Price agreements

Trade agreements (Price/ discount agreement) in Dynamics 365 for Finance and Operations - Setup.

Trade agreements in AX. It is also called as Price/discount agreements.

As the name suggests, it is used to setup the prices (sales prices & purchase prices) and the discounts (Line discounts, Multiline discounts & Total discounts) for the item, customer and Vendor combinations. Once price and discount rules are set up in the trade agreements, the valid prices and/or discounts are fetched and applied to quotations, orders, and invoices in AX.

Box 2: Has changed

There are two kinds of alerts that can be configured by users. These are change-based alerts and due date alerts.

Reference: https://community.dynamics.com/ax/b/abhijeethelestheaxeffect/posts/tradeagreements-price-discount-agreement-in-ax---setup

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/business-events/alertsbusiness-events

Box 1: Associate the country/region to the store.

Associate countries and regions with online stores in Commerce headquarters Countries and regions are associated with online stores (also known as online channels) in Commerce headquarters. When you associate a country or region with an online store, you indicate that customers who reside in that country or region should view the site that is mapped to that online store. You can associate multiple countries and regions with an online store as you require.

To associate countries or regions with an online store, follow these steps.

Go to Retail and Commerce > Channels > Online stores, or search for "online stores" in the search box.

Open the online channel that you want to associate countries or regions with.

On the Countries/Regions FastTab, select Add, and then, in the Country/region field, select the country or region.

Repeat these steps for any other countries or regions that you want to associate with the online channel.

Box 2: Set up geo detection

The geo detection and redirection feature in Dynamics 365 Commerce lets you detect your customers' geographic locations and then use that information to recommend the site that is most appropriate for the country or region where each customer lives.

Reference: https://learn.microsoft.com/en-us/dynamics365/commerce/geo-detection-redirection

Step 1: Configure an Export data project

Set up a data project and recurring data jobs

Create a data project

On the main dashboard, select the Data management tile to open the Data management workspace.

Select the Import or Export tile to create a new data project.

Enter a valid job name, data source, and entity name.

Upload a data file for one or more entities. Make sure that each entity is added, and Note: You can select each entity data card to set up, review, or modify field maps, and to set up XSLT-based transforms that must be applied to inbound dat a. For export data projects, the entity card also shows a filter link, so that you can set up filters to filter data. Currently, all recurring data jobs in a data project use the same filter.that no errors occur.

Select Save.

Step 2: Configure the filter criteria for item group A.

Export only released products assigned to item group A.

Step 3: Create a recurring data job and configure processing recurrent to start immediately.

Create a recurring data job

On the Data project page, select Create recurring data job.

Enter a valid name and a description for the recurring data job.

On the Set up authorization policy tab, enter the application ID that was generated for your application, and mark it as enabled.

Expand Advanced options tab, and specify either File or Data package.

File – Your external integration will push individual files so that they can be processed via this recurring data job. In this case, the format of the file that is expected is the same as the format that was specified when the entity was added to the data project.

Data package – You can push only data package files for processing. A data package is a new format that lets you submit multiple data files as a single unit that can be used in integration jobs.

Process messages in order – You can enable this option to force sequential processing of incoming files in an import scenario. This option is only applicable to files and not data packages.

Select Set processing recurrence, and then, in the Define recurrence dialog box, set up a valid recurrence for your data job.

Optional: Select Set monitoring recurrence, and set up a monitoring recurrence.

Select OK, and then select Yes in the confirmation message box.

Step 4: Add the Released Products entity with a default refresh type set to Incremental push only.

Export only the released product, which has been amended since the previous export.

Export either all the records (full push) or only the records that have changed or been deleted (incremental push).

Reference: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dataentities/recurring-integrations

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/analytics/export-entities-toyour-own-database

Box 1: Use the Copy option

Copy variables to chain test cases

One of the key features of the Regression Suite Automation Tool is the chaining of test cases, that is, the ability of a test to pass values to other tests. Test cases are executed according to their defined order in the Azure DevOps test plan, which can also be updated in the test tool itself. It is important to correctly order the tests if you want to pass variables from one test case to the other.

To save the value of a variable while recording the test in Task Recorder, right-click the field and select Task recorder > Copy, as shown in the following image. Copying will save the variable in the recording file. This variable can be used in subsequent tests.

Box 2: Create a derived test case

Derived test cases

The Regression suite automation tool (RSAT) lets you use the same task recording with multiple test cases, so that you can run a task with different data configurations. Select a test case in the Regression suite automation tool and then select New > Create Derived Test Case. This creates a child test case in Azure DevOps. The resulting derived test case is linked to its parent test case in Azure DevOps. It has an Excel parameters file attached but no recording file. The derived test case will appear in the Regression suite automation tool grid under the same test suite with the Derived column selected. By default, derived test cases are named after their parent test case with a numeric suffix.

Reference: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/perftest/rsat/rsat-chain-test-cases

Box 1: Trace parser

You can diagnose issues and analyze performance by using Trace parser.

You can use the Trace parser to consume traces and analyze performance in your deployment. You can use the Trace Parser to find and diagnose various types of errors. You can also use the tool to visualize execution of X++ methods, as well as the execution call tree.

Box 2: Review X++ calls.

Trace Parser can help identify performance issues including long-running X++ methods, timeconsuming SQL queries, or client server calls. Trace Parser consolidates information from multiple sources, such as remote procedure calls (RPCs) and Microsoft SQL Server, to provide an integrated view of application performance for a process. Trace Parser not only measures code execution, but also provides information about database execution times and may indicate performance issues due to caching.

Reference: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/perf-test/traceparser

https://global.hitachi-solutions.com/blog/erp-monitoring/

Box 1: Tier 1

For evaluation and analysis use Tier 1 sandbox.

Box 2: Tier 1

For Golden Configuration use tier 1 or tier 2.

Box 3: Tier 2

Tier-2 environment: Standard Acceptance Testing – One Standard Acceptance Testing (UAT) instance is provided for the duration of the subscription. This instance is a non-production multi-box instance that customers can use for UAT, integration testing, and training. Additional sandbox/staging instances can be purchased separately as an optional add-on.

Note: User acceptance testing (UAT) can use Tiers 2-5 sandbox.

Reference: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/implifecycle/environment-planning

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/clouddeployment-overview

Box 1: Unit

Unit testing is a software development process in which the smallest testable parts of an application, called units, are individually and independently scrutinized for proper operation. This testing methodology is done during the development process by the software developers and sometimes QA staff.

Box 2: Regression

What is regression testing?

Image result for Dynamics 365 what is regression testing

Regression testing is a software testing practice that ensures an application still functions as expected after any code changes, updates, or improvements. Regression testing is responsible for the overall stability and functionality of the existing features.

Box 3: Functional

FUNCTIONAL TESTING is a type of software testing that validates the software system against the functional requirements/specifications.

Box 4: End to End

End-to-end testing is a methodology that assesses the working order of a complex product in a startto- finish process. End-to-end testing verifies that all components of a system are able to run and perform optimally under real-world scenarios.

Reference: https://www.techtarget.com/searchsoftwarequality/definition/unit-testing

https://katalon.com/resources-center/blog/regression-testing

https://www.guru99.com/functional-testing.html

https://www.techtarget.com/searchsoftwarequality/definition/End-to-end-testing

Box 1: derived

Derived test case

RSAT lets you use the same task recording with multiple test cases, enabling a task to run with different data configurations.

Box 2: chained

Saved variables and chaining of test cases

One of the key features of RSAT is the chaining of test cases, that is, the ability of a test to pass variables to other tests

Reference: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/perftest/rsat/rsat-tutorial