nerdexam
Microsoft

MB-500 · Question #316

A company is using Dynamics 365 finance and operations apps. A user reports that a custom report does not provide the expected results. After updating the report, you receive an alert that there are…

The correct answer is B. A developer rolled back the changeset at the same time you were working on the report. C. You did not perform a Get Latest Version from source control prior to working on the report. B: A Team Foundation Version Control (TFVC) changeset is a permanent part of the history of your version-controlled items and can't be undone or removed. However, you can roll back the effects of one or more changesets. C: Synchronize models from source control In this section…

Apply developer tools

Question

A company is using Dynamics 365 finance and operations apps. A user reports that a custom report does not provide the expected results. After updating the report, you receive an alert that there are conflicting changes to the report when checking it in to source control. You need to troubleshoot the cause of the conflict. What are two causes of the conflict? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.

Options

  • AYou created an annotation on a prior version of the report in source control.
  • BA developer rolled back the changeset at the same time you were working on the report.
  • CYou did not perform a Get Latest Version from source control prior to working on the report.
  • DA developer requested a code review of the prior report changeset which was approved by a
  • EA developer modified the report at the same time and created a shelveset of their changes.

How the community answered

(25 responses)
  • A
    12% (3)
  • B
    80% (20)
  • D
    4% (1)
  • E
    4% (1)

Explanation

B: A Team Foundation Version Control (TFVC) changeset is a permanent part of the history of your version-controlled items and can't be undone or removed. However, you can roll back the effects of one or more changesets. C: Synchronize models from source control In this section, you'll synchronize existing models and model elements from your Azure DevOps project. Synchronization is relevant in the following cases: 1) You've migrated your code from a previous version via Lifecycle Services, or 2) another developer has checked in a new model or new model elements, and you want to synchronize them to your development environment. In Source Control Explorer, right-click on Metadata and select Get Latest Version. Getting the latest version will synchronize your local packages folder with the latest code. https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/version-control- metadata-navigation https://learn.microsoft.com/en-us/azure/devops/repos/tfvc/roll-back-changesets

Topics

#source control conflicts#Azure DevOps#version control#code check-in

Community Discussion

No community discussion yet for this question.

Full MB-500 Practice