nerdexam
Microsoft

MB-500 · Question #8

Case Study 1 - Wide World Importers Background Wide World Importers sell office supplies, furniture, and fittings to their customers across the United States. The company has the following…

The correct answer is deployable package; existing model; package; deployable package. Dynamics 365 Finance - Vendor Exclusion List: Develop, Test, Deploy The four actions and their correct objects follow the standard D365 Finance development-to-deployment lifecycle. Here's the breakdown: --- Concept Map (Before Diving In) | D365 Artifact | What It Is | |---|---|…

Perform testing, performance monitoring, and ALM

Question

Case Study 1 - Wide World Importers Background Wide World Importers sell office supplies, furniture, and fittings to their customers across the United States. The company has the following locations: a retail store in Seattle a warehouse in Seattle a customer support and call center in Atlanta a team of field workers that provide furniture installation services at customer sites. Wide World Importers plans to implement Dynamics 365 Finance and Microsoft Azure cloud platform features. Current environment Customers may place orders by email, phone, or by using the company's website. The company authorizes and processes credit card transactions by using a web-based application. Customer, inventory, supplier, and other master and transactional data is stored in a legacy database. The company collects feedback from customers by phone or a form on the company's website and maintains the data in a Microsoft Excel workbook. Wide World Importers runs on-premises applications to manage payroll and workers compensation. The company has a set of Microsoft Power BI dashboards that present data from a reporting database. The company creates a Lifecycle Services (LCS) implementation project and completes Dynamics 365 Finance onboarding. The company maintains production, quality assurance (QA), development, user acceptance testing (UAT), and build environments. Requirements General You must configure a cloud-based Dynamics 365 Finance development environment and enable code extension that support updates. You must configure version control and a Build environment. You must migrate all legacy data to the new system. You must implement best practices for X++ coding, the data model, caching, and security. All new code must be unit tested in a development environment and then validated by the QA team before code is added to source control. Business processes You must configure vendor trade agreements. Products must be shipped directly from suppliers to customers depending on customer location to save indirect costs. You must collect customer feedback on products shipped directly from vendors. You must deploy code to a UAT environment for testing before deploying code to production. You must validate all entries for the purchase order creation form. You must develop a web portal that allows customers to browse products, place orders, and check order status. Product data for the web portal must be integrated as periodic batches. Business systems You must install and configure a third-party solution for credit card processing within Dynamics 365 Finance. The third-party company will provide a deployable package. The workers compensation application must be able to call an API to update worker compensation details in Dynamics 365 Finance. You must develop a process to import payroll journals into the system. You must configure the warehouse mobile device portal for warehouse operations. You must install a third-party solution to support web portal integration. The solution is supplied as a source code model file. Vendor exclusion list You must develop a new solution to maintain a Vendor exclusion list for each customer and item combination. The solution must meet the following requirements: Isolate all new vendor exclusion codes as a new assembly by creating a table named VendExclusions. Create an index for the table named PrimaryIdx that uses the following fields: CustAccount, ItemId, VendAccount. Ensure that users can open the Vendor Exclusion list report from the customer master form. The list must display the customer account, Item ID, and Vendor account fields. Implement the Excel integration for the Vendor Exclusion List form. Provide functionality to periodically export the Vendor exclusion list to prepare reports by using standard reporting capabilities of Dynamics 365 Unified Operations. Develop necessary security permissions to view and maintain the new Vendor exclusion list functionality and reporting. Users with maintain rights will be able create, update, and delete the exclusion list. Permissions must be assigned to security roles to match company security model. Maintain referential integrity with other tables. Users must be presented with a warning message before a direct delivery purchase order is created for a vendor in exclusion list. Sales managers must be alerted when a new exclusion record is added to the system. Security You must implement the record level audit feature to identify the users who created the record. Grant specific users rights to maintain the vendor exclusion list by using Excel. You must implement validation to check whether a proposed direct delivery purchase order vendor is on the exclusion list for the customer and product combination. Issues User1 is not able to access many features in the system. You must provide User1 administrator rights. A sales manager suspects a data-related issue in the vendor exclusion list. User1 must identify the user who created the referenced exclusion records. Developer2 joins the company and does not have access to a development environment or source control. User2 reports performance issues when they generate direct delivery purchase orders after current updates are applied. User2 reports that they cannot access new functionality and reports. Drag and Drop Question You need to develop, test, and deploy the Vendor Exclusion list solution. What should you create? To answer, drag the appropriate objects to the correct actions. Each element may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Answer:

Exhibit

MB-500 question #8 exhibit

Answer Area

Drag items

existing modelnew modeldeployable packagepackagemodel fileproject

Correct arrangement

  • deployable package
  • existing model
  • package
  • deployable package

Explanation

Dynamics 365 Finance - Vendor Exclusion List: Develop, Test, Deploy

The four actions and their correct objects follow the standard D365 Finance development-to-deployment lifecycle. Here's the breakdown:


Concept Map (Before Diving In)

D365 ArtifactWhat It Is
ModelLogical container for X++ code/metadata; compiled into a DLL assembly
PackageOne or more models compiled together (e.g., ApplicationSuite)
Deployable PackageBinary bundle applied to cloud environments via LCS
ProjectVisual Studio grouping - dev-time only, never deployed

Action-by-Action Breakdown

Action 1 → deployable package

This covers installing the third-party credit card processing solution. The case study is explicit: "The third-party company will provide a deployable package." You apply it to your environment via LCS - no compilation needed. You don't get source; you get a ready-to-deploy binary.

Common mistake: Choosing model file. A .axmodel is a binary model distribution format, not the mechanism for applying solutions to cloud environments. Deployable packages are what LCS accepts.


Action 2 → existing model

This covers developing the Vendor Exclusion List (the VendExclusions table, PrimaryIdx index, security objects, etc.).

You add this to an existing model rather than creating a new one because:

  • The VendExclusions table references CustAccount, ItemId, and VendAccount - fields that live in existing tables (CustTable, InventTable, VendTable)
  • Referential integrity (explicitly required) depends on those references being resolvable at compile time within the same package/model scope
  • Working in an existing model (e.g., ApplicationSuite or a custom extension model already in your package) gives direct access to existing EDTs and table references

Common mistake: Choosing new model. The requirement says "isolate as a new assembly," which sounds like new model. However, a completely isolated new model with no dependency chain to ApplicationSuite cannot reference CustTable etc. without explicit model dependencies configured - and the exam answer assumes the simpler, integration-safe path of using an existing model.


Action 3 → package

After developing in the model, you build/compile in Visual Studio. The output is a package - the compiled binary set of one or more models. This is your intermediate artifact before deployment.

At this stage you can run unit tests in the dev environment (satisfying the requirement: "All new code must be unit tested in a development environment").

Common mistake: Jumping straight to deployable package. A package is the compiled build output. A deployable package is a separately created distribution artifact wrapping that output for LCS upload.


Action 4 → deployable package

To deploy to UAT (and later Production), you create a deployable package from your compiled package and upload it to LCS. From LCS, it is applied to the UAT environment for QA validation before going to Production.

This satisfies: "You must deploy code to a UAT environment for testing before deploying code to production."

Common mistake: Choosing package. Raw packages cannot be applied to cloud environments directly - LCS only accepts deployable packages. This is the most common confusion on D365 Finance exams.


Summary Table

#ActionCorrect ObjectWhy
1Install third-party credit card processordeployable packageISV provides it ready-to-deploy; apply via LCS
2Develop Vendor Exclusion Listexisting modelReferential integrity requires access to existing tables
3Build/compile for testingpackageCompiled output of the model, used for unit testing
4Deploy to UAT → Productiondeployable packageRequired format for LCS cloud environment deployment

Key Misconceptions to Avoid

  1. new model vs existing model: "New assembly" in the requirements refers to the isolation of logic, but the model still needs to live within a package that can resolve existing table references.
  2. package vs deployable package: These are not interchangeable. Package = compiled output. Deployable package = LCS-ready distribution artifact.
  3. project: Only relevant in Visual Studio during development. Never appears in deployment workflows.
  4. model file (.axmodel): Used for distributing model binaries between developers, not for deploying to cloud environments.

Topics

#deployable package#models#solution deployment#ALM

Community Discussion

No community discussion yet for this question.

Full MB-500 Practice