Module 1: Introduction to Visual Studio

Justification:

1. False: This statement is false. A particular Visual Studio project can only belong to one model. However, a model may contain many projects.

Related Lesson: Projects, Models, and Packages

Justification:

1. A visual studio project is not the same thing as a model. A project belongs to a model, and a model may have several different projects.
2. Models are a logical grouping of elements that relate to some specific solution.
3. A model is not used to deploy customizations to a production environment, this would be a package.

Related Lesson: Terminology and Concepts

Justification:

1. The XML file for an element contains metadata, but not only metadata. It also includes the element’s source code.
2. The XML file for an element contains source code, but not only source code. It also include metadata about the element.
3. An element’s XML file contains both metadata and source code.
4. The XML file does not contain information about related elements.

Related Lesson: Projects, Models, and Packages

Justification:

1. A project build will perform a build on only the elements in a project that have changed.
2. A model build will perform a build on only the elements that have changed in particular package where the model resides.
3. Performing a project rebuild will force a build of all elements within the project, regardless of whether they have changed.

Related Lesson: Performing Builds

Justification:

1. Model view cannot be accessed from the View menu
2. To see elements organized by model view, you must open the application explorer and right-click the AOT node to switch between Classic view and Model view.
3. Right-clicking a model only allows for customizing, refreshing, or viewing the model’s properties.
4. The Model view is not accessible from the Dynamics AX menu.

Related Lesson: Navigation

Justification:

• A. Source code: Deployable packages do not include source code. They include metadata, binaries, and models.
• B.

  Metadata: Metadata is included as XML files in a deployable package.

• C. Binaries are included in deployable packages.
• D. Application models are used in the creation of deployable packages.

• SQL Server Reporting Services, or SSRS reports, are available with finance and operations apps.
• Power BI is available in multiple formats in finance and operations apps
• There are many financial reports included in finance and operations apps.

• All answers are correct. finance and operations apps reporting includes SSRS reporting, Power BI reports, and Financial Reports by using the Financial Report Designer.

• A. Incorrect. The Navigation Pane does not generate anything and is not used for business process creation.
• B. Incorrect. The Business Process Modeler is where business process documentation is stored, not created.
• C. Correct. The Task Recorder is used to create task recordings that generate the business process documentation.
• D. Incorrect. User Options is not a location where business process documentation is created.

• A. Correct: Tier 1 environments are for development.

• B. Incorrect: Tier 2 environments are for User acceptance testing and a production environment.
• C. Incorrect: A production environment is your live environment and is not used for development.

• A. Incorrect: Waterfall is best used when all the requirements are defined at the beginning.
• B. Correct: Agile is useful when requirements are undefined and additional requirements are expected throughout the project life cycle.
• C. Incorrect: Spiral is a better methodology for dealing with complex projects that need risk assessment.

Justification:

• A. Incorrect: You should not debug the table code to ensure table changes are synced.
• B. Correct: If your table isn't syncing, you should perform a database synchronization.
• C. Incorrect: Running a code analysis won't synchronize the table metadata.
• D. Incorrect: Creating a deployable package won't update the table.

Justification:

• A. Incorrect: Saving doesn't affect the metadata.
• B. Incorrect: Shelving your changes doesn't create metadata for those changes.
• C. Incorrect: Checking in changes to source control doesn't affect the metadata.
• D. Correct: Building is what creates the metadata to reflect your code, and the metadata is what finance and operations apps uses to define its behaviors.

Justification:

• A. Incorrect: Creating a new entity and copying the properties won't cause your entity to be loaded instead of the original, so your changes won't take effect in the front end.
• B. Correct: Most elements can be modified by extension.
• C. Incorrect: This option was in older versions but was deprecated because it's less supportable than extensions.
• D. Incorrect: VendorInvoiceLineEntity is a locked system entity, so you couldn't do this if you tried.