2026 Fast2test最新的MB-820 PDF版考試題庫和MB-820考試問題和答案免費分享：https://drive.google.com/open?id=1H3Zil3Ik4edAeci74Dv5Fpjhb1XrHgoI
如果你覺得你購買Fast2test Microsoft的MB-820考試培訓資料利用它來準備考試是一場冒險，那麼整個生命就是一場冒險，走得最遠的人常常就是願意去做願意去冒險的人。更何況Fast2test Microsoft的MB-820考試培訓資料是由眾多考生用實踐證明了，它帶給每位考生的成功也是真實有效的，成功有夢想和希望固然重要，但更重要的是去實踐和證明，Fast2test Microsoft的MB-820考試培訓資料是被證明一定會成功的，選擇了它，你還有什麼理由不成功呢！
| Certification Vendor: | Microsoft |
|---|---|
| Exam Name: | Microsoft Dynamics 365 Business Central Developer |
| Exam Number: | MB-820 |
| Exam Duration: | 120 minutes |
| Exam Format: | Multiple choice, Case study, Multiple select, Drag and drop |
| Available Languages: | English, Portuguese (Brazil), Arabic (Saudi Arabia), Chinese (Simplified), Chinese (Traditional), German, French, Japanese, Korean, Spanish, Italian |
| Related Certifications: | Microsoft Certified: Dynamics 365 Business Central Functional Consultant Associate |
| Real Exam Qty: | 40-60 |
| Passing Score: | 700 |
| Exam Price: | $165 USD |
| Certificate Validity Period: | None |
| Sample Questions: | Microsoft MB-820 Sample Questions |
| Exam Way: | Online (proctored) or In-person at a Pearson VUE testing center |
| Official Syllabus URL: | https://learn.microsoft.com/en-us/credentials/certifications/exams/mb-820/ |
眾所周知，MB-820認證在IT認證中有很大的影響力，近年來，該認證已經成為許多成功IT公司的“進門”標準。想快速通過認證考試，可以選擇我們的Microsoft MB-820考古題。選擇我們Fast2test網站，您不僅可以通過熱門的MB-820考試，而且還可以享受我們提供的一年免費更新服務。擁有Microsoft MB-820認證可以幫助在IT領域找工作的人獲得更好的就業機會，也將會為成功的IT事業做好鋪墊。
| 主題 | 簡介 |
|---|---|
| 主題 1 |
|
| 主題 2 |
|
| 主題 3 |
|
| 主題 4 |
|
| 主題 5 |
|
問題 #95
You need to determine why the extension does not appear in the tenant.
What are two possible reasons for the disappearance? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
答案：C,D
解題說明：
In the context of Microsoft Dynamics 365 Business Central, an extension may not appear in the tenant for several reasons, particularly after an upgrade to a new major version.
Option A suggests that the extension was published as a DEV extension, which typically would not cause it to disappear after an upgrade because DEV extensions are intended for development and testing within sandbox environments.
Option B indicates that the extension was not compatible with the new version within 60 days of the first notification. This is a likely reason because Microsoft enforces compatibility rules, and extensions that are not made compatible within the specified timeframe might be removed or disabled.
Option C refers to the extension being published as a PTE (Per-Tenant Extension) and mentions the Platform parameter not being updated. This could cause issues, but not specifically the disappearance of the extension after an upgrade.
Option D expands on Option C by adding that both the Platform and Runtime parameters were not updated in the application file. This is a critical aspect because if these parameters are not correctly set to indicate compatibility with the new version of Business Central, the extension could be disabled or removed.
Option E is similar to Option B but mentions a 90-day period. This option does not align with standard Business Central practices for version compatibility requirements.
Therefore, the two possible reasons for the disappearance of the extension in the tenant after an upgrade are that the extension was not compatible with the new version within the required timeframe (Option B) and that the extension was published as a PTE without the Platform and Runtime parameters being updated (Option D).
問題 #96
You ate creating a view for a Business Central app.
The view requires a custom layout that displays only customer records with a balance greater than 500 in local currency.
You need to configure the view to specify that it has a custom layout.
Which property combination should you use?
答案：C
解題說明：
SharedLayout = true allows for the layout to be shared across views, and it is often used when defining a custom layout that should follow specific filtering conditions.
The Filters property specifies the exact filter criteria for the view, in this case, filtering on Balance > 500 and the Currency Code = LCY (local currency).
A uses incorrect filter syntax and shareLayout = false, which doesn't allow the layout to be shared, so it's not ideal for this use case.
C and D both have issues with the filter syntax and do not use proper Currency Code filtering or share layout settings.
For more details, check Creating Views in Business Central.
問題 #97
You need to parse the API JSON response and retrieve each order no. in the response body.
How should you complete the code segment? To answer select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
答案：
解題說明：
問題 #98
You need to define the XML file properties for the accounting department.
How should you complete the code segment? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
答案：
解題說明：
問題 #99
You need to handle the removal of the Description field and the Clone procedure without breaking other extensions.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select.
答案：
解題說明：
Explanation:
In Business Central, when you need to handle the removal of fields and procedures to ensure that other extensions are not affected by these changes, you typically follow a two-step deprecation process. This allows other developers and users to adapt to the changes before they are fully enforced. Here are the steps to handle the removal:
* Mark as Obsolete: In the first version where the decision to remove the field or procedure is made, you set the ObsoleteState to Pending and provide an ObsoleteReason. This doesn't remove the feature but indicates to users and developers that it will be removed in the future. This step is crucial for backward compatibility.
* Removal: In a subsequent version, after users have had time to adapt to the deprecation warning, you can then remove the field or procedure or set the ObsoleteState to Removed.
Based on these guidelines, here are the three actions you should perform in sequence:
* Set the Description field as ObsoleteState = Pending and ObsoleteReason = 'Not in use' in version
2.0.0.0.
* Set the Clone procedure as ObsoleteState = Pending and ObsoleteReason = 'Not in use' in version
2.0.0.0.
* Remove the Description field from the Issue table in version 2.0.0.1.
These steps will ensure that anyone using the Description field or Clone procedure will receive a warning about the pending deprecation before it is actually removed, thereby minimizing the impact on other extensions and providing a clear path for migration.
When handling the removal of fields and procedures in Microsoft Dynamics 365 Business Central, the process should be carried out in a way that allows other extensions or dependent features to adapt to the changes without causing immediate failures.
* Set Obsolete State and Reason for Description Field (Version 2.0.0.0): The first step involves marking the Description field as obsolete by setting the ObsoleteState to 'Pending'. This is a non-breaking change, signaling to other developers and users that the field is planned for removal in a future version.
An ObsoleteReason should also be provided to explain why the field is being deprecated.
* Set Obsolete State and Reason for Clone Procedure (Version 2.0.0.0): Similarly, the Clone procedure should be marked as obsolete with the ObsoleteState set to 'Pending'. This indicates that the procedure is no longer in use and will be removed in the future. Providing an ObsoleteReason is best practice as it explains the rationale behind the decision.
* Remove the Description Field (Version 2.0.0.1): In the subsequent version, after the developers and users have been given time to adapt to the deprecation notice, the Description field can be safely removed from the Issue table. This is considered a breaking change, hence it is done after the field has been marked as obsolete in a previous version.
The reason for not removing the Description field and Clone procedure immediately in version 2.0.0.0 is to avoid causing runtime errors for any extensions or integrations that may depend on these components. By following this sequence, you provide a clear deprecation path that helps maintain the stability of the overall system while evolving the schema.
Topic 2, Case Study Alpine Ski House
Alpine Ski House is a company that owns and operates hotels, restaurants, and stores. Currently, the company uses the following software and interlace:
* Property management software (PMS) to manage hotel rooms
* On-premises accounting software to generate sales invoices and create purchase orders
* An API that allows restaurants and stores to obtain necessary information Restaurants and stores use standalone software for point of sale (POS) devices. Each day, the POS terminals generate a text file of sales data and save the files in a serval folder. An account assistant must manually import the files to the current software tables to be processed by the system.
The general manager receives several reports monthly from department managers. The reports take too much time to prepare.
The company is moving from a different system to Business Central online to manage the whole company.
The company plans to increase efficiency in every department by using APIs to obtain or share information between the different systems.
Each department involved in purchasing must be able to make purchase requests automatically and easily.
The departments do not need access to the full ERP management system.
Alpine Ski House requires the development of several extensions for the planned improvements. Business Central design patterns must be used to develop all extensions.
Alpine Ski House must develop the following pages:
* Pages that provide multiple configurations in a multistep dialog, like a wizard, to provide required information when the extensions are first installed
* Department-specific Role Center pages to show relevant information and pages with additional information The IT department plans to use Power 61 to analyze departmental information. The database must be configured to provide optimal performance.
The housekeeping department requires the following to increase efficiency and help avoid data entry errors:
* A Housekeeping Role Center to minimize navigation to relevant areas In Business Central online and to show relevant information in it
* Pages to embed into a new Room page to show additional information about the Room entity
* A table named Room Incident for the housekeeping team to enter room issue information
* A Housekeeping canvas app that connects to an extension
The department requires the development of an extension with a new API page named RoomsAPI.
* The housekeeping team will use RoomsAPI to publish room details, update when work is complete, or provide repair notifications from the canvas app.
* This custom API page must expose a custom table named Rooms and have an ID 50000. The table must be able to update from the PMS. The PMS team must know the end to connect to the custom API.
* A developer provides the following details for the API page:
APIPublisher = 'alpine';
APIGroup - 'integration';
APIVersion - 'v2.6';
fntityName # 'room';
EntitySetName = 'rooms';
* The extension must be published in Business Central online and include a list page named Room List that includes all hotel rooms.
* Installation or updates to this extension must meet the following requirements:
o Some web services must be published automatically.
o The version of the specified application's metadata must be obtained in AL language.
o The code required to perform tasks cannot be accessible from other parts of the application.
The Room Incident table information must include the following fields:
* Incident entry: An incremental number
* Room No.: A room from the Room table
* Incident Date: The work date
o The table definition in the Room Incident table must autofill the Incident Date when the housekeeping team inserts a new record, o The value for Incident Date must be the work date configured in the Business Central online client.
* Status: Includes the following options lo identify the status of the incident:
o Open: When the Room Incident is created
o In Progress: When someone starts repair work
o Closed: When the incident is solved
* Incident Closing Date: Auto-updating field (when the status passes to Closed, the field will update with the work date)
* Incident Description: Text
* Image. Media data type
o The stored picture must be downloadable from a menu action.
o A Room Incident page must be developed to contain the download action.
To increase efficiency, the new system must manage the generated data from the restaurants and stores directly by using the API on the POS terminals.
* The company requires a code unit called from a job queue to read the information from the POS terminal APIs.
* The POS terminal information must be stored in a table named POS Information, have an ID 50100. and be editable on a page.
* The account manager requires an option on the menu of the page to run the process manually.
To analyze the information received from the POS terminals, the company requires:
* A custom API named ticketAPI to export the information to Power BI
* Use of the Read Scale-Out feature to improve database performance
The purchasing department requites a new entity in Business Central online to log non-conformities of goods received from vendors. The entity must be set up as follows:
* The non-conformity entity must have two tables:
o a header with common information
o one or more lines with the detailed received items that are non-conforming
* The entity requires a page named Non-conformity and a subpage named Non-Conformity Lines to store the information.
When a purchase order with incorrect quantity 01 quality issues is received, the entity must create a non- conformity document in the system. The following information must be nick the document:
* Non-conformity Number: must use the No. Series table from Business Central online to manage this field and use these features:
o Alphanumeric values
o Number format that includes "NO and the year as part of the number: for example, NC24-001
* Non-conformity Date: stores only the creation date
* Vendor No.: stores the number of the vendor that sent the items; only vendors from the company must be included
* Owner: code of an employee defined in the company
* Receipt No.: must meet the following conditions:
o Be an existing receipt No.
o Be received from the vendor indicated in the Vendor No. field
* Comments: can include comments with rich text and pictures to illustrate quality problems
* Status: includes nonconformity statuses, such as:
o Open
o Notified
o Closed
* Lines must contain the following details:
o Item No.: item received (for existing inventory items only)
o Description: item description
0 Quantity: non-conforming quantity
0 Non-conformity Type:
# Quality
# Quantity
# Delivery date
The serial numbers of the non-conformities and the period in which they can be created must be in a configuration table and its corresponding page to allow them to be modified for the users.
問題 #100
......
MB-820證照指南: https://tw.fast2test.com/MB-820-premium-file.html
從Google Drive中免費下載最新的Fast2test MB-820 PDF版考試題庫：https://drive.google.com/open?id=1H3Zil3Ik4edAeci74Dv5Fpjhb1XrHgoI