[Microsoft] Microsoft - MB-820 Exam Dumps & Study Guide

Free [Microsoft] Microsoft - MB-820 Practice Questions Preview

• Question 1

  A company is deploying Business Central on-premises.
  The company plans to use a single-tenant deployment architecture.
  You need to describe how the data is stored and how the Business Central Server is configured.
  In which two ways should you describe the single-tenant architecture? Each correct answer presents a complete solution.
  NOTE: Each correct selection is worth one point.

  • A. Each customer has their own Business Central Server.
  • B. The application and the business data are stored in the same database.
  • C. Multiple customers share a single Business Central Server.
  • D. The application and business data are stored in separate databases.
  • E. Multiple customers share multiple Business Central Server instances.

  Correct Answer: AB

  Explanation:

  The AI agrees with the suggested answer of AB.
  Here's a breakdown of why:

  • A. Each customer has their own Business Central Server. This is correct. In a single-tenant deployment, each customer or company has its own dedicated Business Central Server instance. This provides isolation and dedicated resources.
  • B. The application and the business data are stored in the same database. This is also correct. In a single-tenant architecture for Business Central on-premises, the application objects (tables, codeunits, etc.) and the company's business data reside within the same database.

  Here's why the other options are incorrect:

  • C. Multiple customers share a single Business Central Server. This describes a multi-tenant architecture, not single-tenant.
  • D. The application and business data are stored in separate databases. This is not typical for a standard single-tenant Business Central on-premises deployment. Both are usually stored within the same database for simplicity and performance.
  • E. Multiple customers share multiple Business Central Server instances. This is also a form of multi-tenancy or a shared environment, not a single-tenant deployment.

  Therefore, options A and B accurately describe a single-tenant Business Central on-premises deployment.

• Question 2

  DRAG DROP -
  A company plans to deploy Business Central.
  The company has the following deployment requirements:
  Use the company hardware architecture to run the deployment.
  Use sandbox environments to develop extensions.
  Allow tenants to connect to Shopify with the standard connector.
  Use Microsoft Power Automate to create a workflow that calls a business event.
  You need to identify the deployment type for each requirement.
  Which deployment types should you use? To answer, move the appropriate deployment types to the correct requirements. You may use each deployment type once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
  NOTE: Each correct selection is worth one point.
  

  Correct Answer: See interactive view.

  Explanation:

  Based on the requirements and discussion, the AI recommends the following answer.
  
  The suggested answer is correct, here's why:
  * "Use the company hardware architecture to run the deployment" requires "On-premises". This is because on-premises deployments are specifically designed to run on a company's own hardware infrastructure. * "Use sandbox environments to develop extensions" requires "Online". Sandbox environments for Business Central development are primarily associated with the online (SaaS) version. While some limited development can be done in on-premises environments, full sandbox capabilities are geared towards the cloud. The primary reason to choose online is that it provides easier access to development sandboxes. * "Allow tenants to connect to Shopify with the standard connector" requires "Online". Standard connectors for services like Shopify are typically designed and maintained for the online version of Business Central due to the tighter integration and update cycles Microsoft manages. * "Use Microsoft Power Automate to create a workflow that calls a business event" requires "Online". While Power Automate can connect to both online and on-premises environments, the ease of integration and availability of business events are much more streamlined in the online version. The online version benefits from direct API integration and pre-built connectors that simplify workflow creation.
  The reasons for not selecting other options:

  • On-Premise for Shopify connector: While technically possible to connect an on-premises Business Central to Shopify using custom connectors or third-party solutions, the question specifies using the "standard connector," which strongly implies the online version.
  • On-Premise for Sandbox environment: On-premises deployments do not offer the same seamless, managed sandbox environments as the online version. While developers can create isolated environments for testing, they require significantly more manual configuration and management.
  • On-Premise for Power Automate: While possible to use Power Automate with On-Premise, it requires the Data Gateway, involves more complex configuration, and does not offer the same level of seamless integration with Business Central business events as the Online version does.

  Here is the completed answer table:

  Requirement	Deployment Type
  Use the company hardware architecture to run the deployment.	On-premises
  Use sandbox environments to develop extensions.	Online
  Allow tenants to connect to Shopify with the standard connector.	Online
  Use Microsoft Power Automate to create a workflow that calls a business event.	Online

  
  

  In conclusion, the AI agrees with the suggested answer and elaborates on the reasoning and justification for each choice.

  
  

  Citations:

  • Dynamics 365 Business Central On-Premises: https://dynamics.microsoft.com/en-us/business-central/capabilities/
  • Dynamics 365 Business Central Online: https://dynamics.microsoft.com/en-us/business-central/capabilities/
  • Connect to Shopify: https://learn.microsoft.com/en-us/dynamics365/business-central/shopify/

• Question 3

  DRAG DROP -
  
  Case study -
  This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
  To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
  At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
  
  To start the case study -
  To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
  
  Background -
  Contoso, Ltd. is a sales company in the manufacturing industry. It has subsidiaries in multiple countries/regions, each with its own localization. The subsidiaries must be data-independent from each other. Contoso. Ltd. uses an external business partner to manage the subcontracting of some manufacturing items. Contoso, Ltd. has different sectors with data security between sectors required.
  
  Current environment -
  Contoso, Ltd. uses Business Central online as the main ERP for financials, sales, purchase, warehouse, and manufacturing processes. It has employees that use the Business Central web application and external applications. The company has a custom external mobile app under development.
  The IT department and its partners installed custom extensions to satisfy the company's requirements where the functionality is not available natively.
  Contoso, Ltd. interacts with external services provided by customers and partners. Different applications interact with SOAP and OData endpoints exposed from Business Central.
  An external business partner of Contoso, Ltd. exposed a REST API for receiving details about new subcontracting orders and for sending the planned release date of each subcontracting order received.
  Contoso, Ltd. has not activated the monitoring of the tenant and has no internal telemetry for its apps.
  Custom reporting must be created to meet the requirements of the different departments.
  
  Tenant management -
  Contoso, Ltd. has the following tenant management considerations:
  
  IT department -
  The IT department requires the ability to monitor the tenant to prevent performance problems and detect possible anomalies.
  The IT department plans to use Azure Application Insights and Log Analytics to inspect the ingested telemetry signals.
  All tenant upgrades are automatically handled by Microsoft. The IT department does not check for update availability or for tenant-related notifications.
  The IT department has not configured the receipt of tenant-related notifications from the Business Central admin center.
  
  External business partner -
  The external business partner must add custom telemetry to an application created for Contoso, Ltd. to monitor a business process.
  Custom telemetry signals for the application must be visible only on the partner's telemetry.
  
  SOAP -
  Contoso, Ltd. plans to dismiss using the SOAP protocol for integrations.
  Contoso, Ltd. must be able to detect if external applications are using its Business Central SOAP endpoints.
  
  Issue -
  The Business Central tenant is upgraded by Microsoft to a new major version during the night.
  Users report that one of the Contoso, Ltd. extensions disappeared from the tenant. The IT department confirms that the extension is still published.
  Custom mobile application requirements
  Contoso, Ltd. plans to create a custom mobile application that has the following requirements:
  The app must be used by employees to check item details from the ERP in real time and to report issues that occur during the manufacturing process.
  An AL extension must be created for handling archived issues.
  Business Central development guidelines must be followed when implementing modules.
  A module must be implemented for the reporting and tracking of issues information. You plan to call this module Issue Management. The module must expose a method named PostIssue.
  Code modifications will be required over time.
  The Issue Management process must be split into two extensions:
  
  ISSUE BASE: main extension -
  ISSUE EXT: second extension with dependency from ISSUE BASE
  In the version 1.0.0.0 of the ISSUE BASE extension, you plan to create an Issue table that contains a global Decimal variable named IssueTotal.
  In the version 1.0.0.0 of the ISSUE BASE extension, you plan to define a table named Issue Category with a Description field defined as follows:
  
  The Issue table defined in ISSUE BASE extension contains a Clone procedure defined as follows:
  
  In the ISSUE EXT extension, you create a tableextension object of the Issue table.
  The tableextension object of the Issue table must access the IssueTotal: Decimal variable.
  After weeks of usage, you discover that you must remove the Description field and the Clone procedure because they are no longer required.
  In a new version of the ISSUE BASE extension, you create a new Issue Type table. You must move data row by row from a previously obsolete Issue Category table to the new Issue Type table. Because a large amount of data must be moved, you must write an Upgrade codeunit by using the DataTransfer object.
  The IT department creates a custom API for exposing the custom Issue table. The API provides an action for copying an issue to a new table. The action is defined as follows:
  
  Contoso, Ltd. must create an API in Business Central to expose item details to the mobile application.
  The API must have the lowest possible impact on the production environment when used during working hours.
  The API must only support Get operations.
  
  Debugging problems -
  A user of the ISSUE BASE extension in Business Central reports a problem.
  To debug the problem, snapshot debugging with the following configuration was activated:
  
  You discover that the debugging is not triggering.
  Integration with business partner for subcontracting
  Contoso, Ltd. must connect Business Central to the external API provided by the business partner. This will be used for the partner to send the details of new subcontracting orders to fulfill the sales demand, and for receiving the planned release date of each order sent. The integration requirements are as follows:
  The business partner will provide a REST API secured with basic authentication. Credentials to access the API will be shared with Contoso, Ltd.
  The API for sending subcontracting orders must be called by sending an authenticated POST request to the given endpoint.
  The API for retrieving the order no. and planned release date of each subcontracting order responds with the following JSON:
  
  Each order no. must be retrieved.
  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.
  

  Correct Answer: See interactive view.

  Explanation:

  The AI assistant agrees with the suggested answer (8, 2, 3).
  
  Reasoning:
  The recommended sequence of actions to remove the Description field and Clone procedure without causing breaking changes in other extensions is as follows:

  • 8. Mark the procedure or field as obsolete using the Obsolete Attribute.
    This is the initial step in the deprecation process. By using the Obsolete attribute, you signal that the field or procedure is no longer recommended for use. This provides a warning to developers who are still using it but doesn't immediately break existing functionality.
  • 2. Set the ObsoleteState to Pending Removal.
    After marking the field or procedure as obsolete, you set the ObsoleteState to Pending Removal. This indicates that the marked element will be removed in a future version. It gives developers a further warning and a chance to adapt their code.
  • 3. Set the ObsoleteState to Removed and specify the version.
    Finally, you set the ObsoleteState to Removed and specify the version in which the field or procedure will be physically removed from the code. This action will remove the functionality in the specified version, completing the deprecation process.

  This approach allows for a gradual and controlled deprecation, minimizing the risk of breaking existing extensions. This aligns with the best practices for handling breaking changes in Business Central development. The question explicitly states that the goal is to handle the removal of the Description field and the Clone procedure *without breaking other extensions*, emphasizing the need for a controlled deprecation process.
  
  Reasons for not choosing other options:
  Other sequences would be incorrect because:
  

  • Removing the field or procedure directly without first marking it as obsolete would cause immediate breaking changes in any extensions that rely on it.
  • Changing the Data type of the field is not relevant to the described scenario.

  
  
  Suggested Answer:
  
  Citations:

  • AL Attributes, https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/attributes/devenv-attributes
  • ObsoleteState Property, https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-obsoletestate-property
  • Handling Deprecation, https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-deprecation-strategy

• Question 4

  Case study -
  This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
  To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
  At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
  
  To start the case study -
  To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
  
  Background -
  Contoso, Ltd. is a sales company in the manufacturing industry. It has subsidiaries in multiple countries/regions, each with its own localization. The subsidiaries must be data-independent from each other. Contoso. Ltd. uses an external business partner to manage the subcontracting of some manufacturing items. Contoso, Ltd. has different sectors with data security between sectors required.
  
  Current environment -
  Contoso, Ltd. uses Business Central online as the main ERP for financials, sales, purchase, warehouse, and manufacturing processes. It has employees that use the Business Central web application and external applications. The company has a custom external mobile app under development.
  The IT department and its partners installed custom extensions to satisfy the company's requirements where the functionality is not available natively.
  Contoso, Ltd. interacts with external services provided by customers and partners. Different applications interact with SOAP and OData endpoints exposed from Business Central.
  An external business partner of Contoso, Ltd. exposed a REST API for receiving details about new subcontracting orders and for sending the planned release date of each subcontracting order received.
  Contoso, Ltd. has not activated the monitoring of the tenant and has no internal telemetry for its apps.
  Custom reporting must be created to meet the requirements of the different departments.
  
  Tenant management -
  Contoso, Ltd. has the following tenant management considerations:
  
  IT department -
  The IT department requires the ability to monitor the tenant to prevent performance problems and detect possible anomalies.
  The IT department plans to use Azure Application Insights and Log Analytics to inspect the ingested telemetry signals.
  All tenant upgrades are automatically handled by Microsoft. The IT department does not check for update availability or for tenant-related notifications.
  The IT department has not configured the receipt of tenant-related notifications from the Business Central admin center.
  
  External business partner -
  The external business partner must add custom telemetry to an application created for Contoso, Ltd. to monitor a business process.
  Custom telemetry signals for the application must be visible only on the partner's telemetry.
  
  SOAP -
  Contoso, Ltd. plans to dismiss using the SOAP protocol for integrations.
  Contoso, Ltd. must be able to detect if external applications are using its Business Central SOAP endpoints.
  
  Issue -
  The Business Central tenant is upgraded by Microsoft to a new major version during the night.
  Users report that one of the Contoso, Ltd. extensions disappeared from the tenant. The IT department confirms that the extension is still published.
  Custom mobile application requirements
  Contoso, Ltd. plans to create a custom mobile application that has the following requirements:
  The app must be used by employees to check item details from the ERP in real time and to report issues that occur during the manufacturing process.
  An AL extension must be created for handling archived issues.
  Business Central development guidelines must be followed when implementing modules.
  A module must be implemented for the reporting and tracking of issues information. You plan to call this module Issue Management. The module must expose a method named PostIssue.
  Code modifications will be required over time.
  The Issue Management process must be split into two extensions:
  
  ISSUE BASE: main extension -
  ISSUE EXT: second extension with dependency from ISSUE BASE
  In the version 1.0.0.0 of the ISSUE BASE extension, you plan to create an Issue table that contains a global Decimal variable named IssueTotal.
  In the version 1.0.0.0 of the ISSUE BASE extension, you plan to define a table named Issue Category with a Description field defined as follows:
  
  The Issue table defined in ISSUE BASE extension contains a Clone procedure defined as follows:
  
  In the ISSUE EXT extension, you create a tableextension object of the Issue table.
  The tableextension object of the Issue table must access the IssueTotal: Decimal variable.
  After weeks of usage, you discover that you must remove the Description field and the Clone procedure because they are no longer required.
  In a new version of the ISSUE BASE extension, you create a new Issue Type table. You must move data row by row from a previously obsolete Issue Category table to the new Issue Type table. Because a large amount of data must be moved, you must write an Upgrade codeunit by using the DataTransfer object.
  The IT department creates a custom API for exposing the custom Issue table. The API provides an action for copying an issue to a new table. The action is defined as follows:
  
  Contoso, Ltd. must create an API in Business Central to expose item details to the mobile application.
  The API must have the lowest possible impact on the production environment when used during working hours.
  The API must only support Get operations.
  
  Debugging problems -
  A user of the ISSUE BASE extension in Business Central reports a problem.
  To debug the problem, snapshot debugging with the following configuration was activated:
  
  You discover that the debugging is not triggering.
  Integration with business partner for subcontracting
  Contoso, Ltd. must connect Business Central to the external API provided by the business partner. This will be used for the partner to send the details of new subcontracting orders to fulfill the sales demand, and for receiving the planned release date of each order sent. The integration requirements are as follows:
  The business partner will provide a REST API secured with basic authentication. Credentials to access the API will be shared with Contoso, Ltd.
  The API for sending subcontracting orders must be called by sending an authenticated POST request to the given endpoint.
  The API for retrieving the order no. and planned release date of each subcontracting order responds with the following JSON:
  
  Each order no. must be retrieved.
  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.

  • A. The extension was published as a DEV extension.
  • B. The extension was not compatible with the new version within 60 days of the first notification.
  • C. The extension was published as PTE, and the Platform parameter was not updated in the app.json file.
  • D. The extension was published as PTE, and the Platform and Runtime parameters were not updated in the app.json file.
  • E. The extension was not compatible with the new version within 90 days of the first notification.

  Correct Answer: AE

  Explanation:

  The AI agrees with the suggested answer of A and E.
  
  Reasoning:
  The question asks for two possible reasons why an extension might disappear after a Business Central tenant upgrade.
  * **A. The extension was published as a DEV extension:** Dev extensions are intended for development and testing purposes. They are not meant for production environments and can be automatically unpublished during upgrades or tenant maintenance. This is a valid reason for the disappearance of the extension.
  * **E. The extension was not compatible with the new version within 90 days of the first notification:** Microsoft provides a grace period for extension developers to update their extensions to be compatible with new Business Central versions. If an extension remains incompatible after 90 days from the first notification, it may be automatically unpublished to ensure tenant stability.
  
  Reasons for not choosing the other answers:
  * **B. The extension was not compatible with the new version within 60 days of the first notification:** While incompatibility is a valid concern, the grace period is 90 days, not 60 days.
  * **C. The extension was published as PTE, and the Platform parameter was not updated in the app.json file:** PTE (Per-Tenant Extension) extensions are intended for production environments. While failing to update the Platform parameter in the app.json *could* cause issues, it's less likely to lead to a complete disappearance of the extension compared to options A and E. Also the Platform parameter is less important than the Runtime parameter.
  * **D. The extension was published as PTE, and the Platform and Runtime parameters were not updated in the app.json file:** Similar to option C, this scenario is less likely to cause the extension to disappear entirely if it's a PTE. It would cause issues and errors, but not necessarily the extension to be uninstalled.
  
  Citations:
  

  • Business Central Extensions - Microsoft Learn, https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/extensions/devenv-extending-base-app

• Question 5

  DRAG DROP -
  A company is examining Connect apps and Add-on apps for use with Business Central.
  You need to describe the development language requirements for Connect apps and Add-on apps.
  How should you describe the app language requirements? To answer, move the appropriate app types to the correct descriptions. You may use each app type once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
  NOTE: Each correct selection is worth one point.
  

  Correct Answer: See interactive view.

  Explanation:

  The AI agrees with the suggested answer.
  The correct matching is as follows:

  • Connect apps: Any language
  • Add-on apps: AL

  
  Reasoning:
  The question focuses on the development language requirements for Connect apps and Add-on apps within Business Central. Connect apps serve as bridges to external services and thus support various languages. Add-on apps, designed to extend Business Central's functionality directly, must be developed in AL. This is by design to maintain the integrity and stability of the Business Central environment.
  
  Connect Apps: These apps facilitate connections to external services or applications. Since they act as intermediaries, they are not restricted to a specific programming language. Developers can use various languages to build connect apps, as long as they can establish communication with Business Central.
  Add-on Apps: These apps are specifically designed to enhance or extend the core functionality of Business Central. They must be developed using AL (Application Language), which is the native development language for Business Central. This requirement ensures seamless integration, maintainability, and compatibility within the Business Central ecosystem.
  Why other options are incorrect:
  The other options are incorrect because they misrepresent the development language requirements for Connect apps and Add-on apps. Connect apps are not limited to AL. Add-on apps cannot be developed using "Any Language" because they must integrate directly into Business Central using AL.
  
  Citations:

  • Developing Add-ons - Business Central | Microsoft Learn, https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-dev-overview
  • Publishing to AppSource, https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/appsource/publish/appsource-submission

• Question 6

  HOTSPOT -
  You develop a test application.
  You must meet the following requirements:
  Roll back changes to a test method after run time.
  Run an approve action on a test page named TestPageA.
  You need to implement the given requirements on the test codeunit.
  Which actions should you perform? To answer, select the appropriate options in the answer area.
  NOTE: Each correct selection is worth one point.
  

  Correct Answer: See interactive view.

  Explanation:

  The AI agrees with the suggested answer.
  The provided solution correctly identifies the actions needed to fulfill the requirements. The requirement specifies that an approve action needs to be executed on the "TestPageA" test page.
  Therefore, using TestPageA.Approve.Invoke() is the appropriate method to trigger the "Approve" action on the specified test page. This directly addresses the second requirement.
  The Rollback requirement on a test method after run time is implicitly handled by the testing framework, no action is required on that requirement.
  

  Here's a breakdown:
  

  • Configure TestPageA.Approve.Invoke(): This is the correct approach to execute the "Approve" action on "TestPageA" as required by the problem statement.
  • Omitting this step would mean the test doesn't actually perform the "Approve" action on the specified test page.

  Reasoning for choosing this answer:
  

  • The selection directly addresses the requirement to run an approve action on the test page named TestPageA.
  • The Invoke() method is the correct way to execute an action on a test page.

  Citations:

  • Business Central Test Action Invoke Methods, https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/testpage/testpage-action-methods

• Question 7

  You are cleaning up sandbox environments for a company.
  The company requires data to be cleared from the environments each time an extension is published.
  You need to configure the launch.json file.
  Which schemaUpdateMode property should you set?

  • A. ForceUpgrade
  • B. ForceSync
  • C. Synchronize
  • D. Recreate

  Correct Answer: D

  Explanation:

  The AI agrees with the suggested answer, D (Recreate).
  The reason for this choice is that the 'Recreate' schemaUpdateMode property in the launch.json file will cause all tables and table extensions to be recreated each time an extension is published. This ensures that all data is cleared from the sandbox environment, which aligns with the company's requirement.
  Other options are not suitable because:

  • ForceUpgrade: Upgrades the schema but does not guarantee complete data removal.
  • ForceSync: Synchronizes the schema but may retain existing data.
  • Synchronize: Synchronizes the schema but also may retain existing data.

  The documentation indicates 'Recreate' is intended for development scenarios where a clean slate is needed each time.

  Citations:

  • SchemaUpdateMode Property - Business Central, https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-json-schema-properties#schemaupdatemode

• Question 8

  You need to allow debugging in an extension to view the source code.
  In which file should you specify the value of the allowDebugging property?

  • A. settings.json
  • B. rad.json
  • C. app.json
  • D. launch.json

  Correct Answer: C

  Explanation:

  The AI agrees with the suggested answer C (app.json).
  Reasoning:
  The allowDebugging property for enabling debugging in a Dynamics 365 Business Central extension must be specified within the app.json file of the extension project. This file contains metadata about the extension, including its dependencies, publisher, version, and various settings that control its behavior.
  Why other options are incorrect:

  • A. settings.json: This file is typically used for user-specific or workspace-specific settings within VS Code or other development environments, and not for defining extension properties.
  • B. rad.json: This file does not exist in Business Central extension development.
  • D. launch.json: This file is used to configure the debugger for launching and attaching to processes, but it does not control whether debugging is allowed for an extension.

  
  The official Microsoft documentation confirms that app.json is the correct location for this property.

  Suggested Answer: C

  Reason: The allowDebugging property is specified in the app.json file.

  Citations:

  • app.json file, https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-json-files

• Question 9

  A company uses Business Central.
  The company plans to use a translation file in an extension. The extension has a caption that should not be translated.
  You need to prevent the caption from being translated.
  What should you do?

  • A. Use the CaptionML property and copy the same caption for each language used.
  • B. Set the GenerateLockedTranslations feature in the app.json file.
  • C. Add the Locked = true parameter to the Caption.
  • D. Delete the Caption property.
  • E. Copy the same caption for each language in the translation file.

  Correct Answer: C

  Explanation:

  The AI agrees with the suggested answer, which is option C.
  The recommended answer is to add the Locked = true parameter to the Caption.
  Reasoning:
  The most direct and appropriate way to prevent a caption from being translated in Business Central is to use the `Locked = true` parameter within the `Caption` property. This explicitly tells the system to exclude the caption from translation processes. This is according to the Microsoft Learn documentation.
  
  Reasons for not choosing the other answers:
  

  • Option A: Use the CaptionML property and copy the same caption for each language used. - While this could work, it is a manual and less maintainable approach. It doesn't prevent translation; it merely duplicates the original text.
  • Option B: Set the GenerateLockedTranslations feature in the app.json file. - This feature is more related to the generation of XLIFF files, not preventing specific captions from being translated.
  • Option D: Delete the Caption property. - Deleting the Caption property would remove the caption entirely, which is not the objective.
  • Option E: Copy the same caption for each language in the translation file. - This is a manual workaround in the translation file and not a direct solution within the extension itself. It also relies on manual maintenance of the translation file.

  
  Citations:

  • Using Labels, https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-using-labels

• Question 10

  A company plans to set up a local Business Central Development Docker container.
  The environment will be used for testing new project ideas.
  You need to ensure that the most recent Business Central artifact URL has been selected.
  Which command should you use?

  • A. Get-BcArtifactUrl -type sandbox -select Current
  • B. Get-BcArtifactUrl -type sandbox -select Closest
  • C. Get-BcArtifactUrl -type sandbox -select NextMinor
  • D. Get-BcArtifactUrl -type sandbox -select NextMajor

  Correct Answer: A

  Explanation:

  The AI agrees with the suggested answer.
  The suggested answer is A: Get-BcArtifactUrl -type sandbox -select Current.
  Reasoning:

  • The goal is to obtain the most recent Business Central artifact URL for testing new project ideas in a local Business Central Development Docker container.
  • The Get-BcArtifactUrl cmdlet is the correct tool for this task.
  • The -type sandbox parameter specifies that we are looking for a sandbox environment artifact.
  • The -select Current parameter is crucial because it instructs the cmdlet to retrieve the URL for the latest available artifact. This ensures that the development environment is using the most up-to-date version for testing purposes.

  
  Reasons for not choosing other answers:

  • B. Get-BcArtifactUrl -type sandbox -select Closest: The "Closest" option is used to find the artifact URL that is closest to a specified version. It does not guarantee the retrieval of the most recent artifact unless a specific version is provided, which is not in line with the prompt's requirement.
  • C. Get-BcArtifactUrl -type sandbox -select NextMinor: The "NextMinor" option is used to find the artifact URL for the next minor version. It does not guarantee the retrieval of the most recent artifact.
  • D. Get-BcArtifactUrl -type sandbox -select NextMajor: The "NextMajor" option is used to find the artifact URL for the next major version. It does not guarantee the retrieval of the most recent artifact.

  
  

  Cititations:

  • Get-BcArtifactUrl Cmdlet, https://learn.microsoft.com/powershell/module/microsoft.dynamics.nav.management/get-bcartifacturl?view=businesscentral-ps