Free Microsoft MB-700 Practice Test Questions MCQs
Stop wondering if you're ready. Our Microsoft MB-700 practice test is designed to identify your exact knowledge gaps. Validate your skills with Microsoft Dynamics 365: Finance and Operations Apps Solution Architect questions that mirror the real exam's format and difficulty. Build a personalized study plan based on your free MB-700 exam questions mcqs performance, focusing your effort where it matters most.
Targeted practice like this helps candidates feel significantly more prepared for Microsoft Dynamics 365: Finance and Operations Apps Solution Architect exam day.
21050+ already prepared
Updated On : 3-Mar-2026105 Questions
Microsoft Dynamics 365: Finance and Operations Apps Solution Architect
4.9/5.0
Topic 1: City Power and Light 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
City Power and Light is a publicly traded electric utility company. The company has a
corporate office, four regional field offices, two subsidiary companies that produce solar
energy, and one wind power subsidiary. City Power and Light has 50 percent ownership in
the solar energy company. The company fully owns the wind power company but operates
it separately from other businesses.
City Power and Light currently operates with varying integrated legacy systems and has
difficulty assembling company financials. Migrating these systems and workloads to a
common platform would improve visibility into the business and inform decision making.
The company plans to implement Dynamics 365.
Legacy systems
• The legacy system does not have audit capability of configurable workflow based on
business logic
• The legacy paper-based purchasing system does not allow parent-child relationships for
vendors. Two signatures are required for purchase requisitions.
• Purchase orders are entered into the system manually based on signed purchase
requisitions printed to PDF and then emailed to the vendor.
• The legacy procurement system does not have a parent-child relationship for master data
management.
Financials
• All financial consolidate up to City Power and Light Holding, LLC.
• The finance department employees are currently able to create as well as pay invoices.
Customers
Sales orders from the website are uploaded into the system manually once a day .
International and domestic customers currently post to the same receivable account. At the
end of the month, these have to be separated into domestic and international receivable
accounts.
Other information
• There are multiple active acquisitions expected during trie implementation timeline.
• The item master data for solar panel configurations has multiple variables and variants.
As a complex.
General
• Flexible implementation approach to support frequently changing business needs and
requirements.
• A phased roll-out is needed due to the complexity of the business.
• Any offsite Travel meals submitted on an expense report without corresponding flight and
hotel expenses need to be reviewed.
• Ten percent of vendor invoices should be reviewed to ensure they meet company policy.
• Testing of business processes needs to be automated.
• Customer surveys must be sent out after email customer service interactions. Surveys
must contain a rating system and a way for customers to add comments.
• Employees require one central tool for internal communication, phone calls, and file
sharing.
• Sales representatives need an enterprise quoting tool for solar panel customers.
Technical
• A cloud-based financial and operational system, accessible on mobile devices.
• The ability to keep a legacy meter reading application with the ability to use the data in
aggregated operating reports.
• Business processes should be tested with different variables for the same process as part
of the testing plan.
Functional
• Establish and document business processes to assist with on-boarding new employees
more efficiently.
• Parent-child relationships need to be established for vendors with regional offices.
Purchasing locations vary from invoicing locations.
• The ability to create automated wire payments.
Requisitions
• All purchase requisitions over $50 need to be approved by a manager.
• All purchase requisitions over $1,000 require senior manager approval.
• Multiple purchase requisitions to the same vendor should be combined.
Sales
The item master data for solar panel configurations have multiple variables and variants.
This leads to complex quoting and sales orders.
Sales representatives must be able to create automated wire payments.
Issues
• A limited number of users are available for testing.
• User1 reports that the date fields are not saving during formula entry with saved variables
functionality in the RSAT tool.
• The purchasing department is seeing duplicate vendor records during data conversion.
• Audit notes from the prior year indicate improvement is needed in roles and
responsibilities related to financial management and security roles.
• User2 reports that parts ordered on P0123 were never received and the vendor has said
they never received the PO.
• User3 provides feedback that important steps during journal entry are being forgotten and
new users need hands-on guidance.
• Service technicians report that they do not always have the appropriate tools or parts with
them requiring multiple service calls.
A company plans to implement Dynamics 365 Supply Chain Management. The company has the following requirements:
Use mobile devices for warehouse activities including cycle counting.
Set up automatic cycle counting work IDs and assign the IDs to workers.
Ensure that workers can group work IDs that are specific to a particular location, zone, or work pool.
Ensure that workers can specify a cycle counting work ID that has a status of Open.
Ensure that workers can count items in a warehouse location at any time.
You need to recommend cycle counting options that meet the company’s requirements.
What should you recommend? To answer, drag the appropriate counting options to the correct requirements. Each counting option 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.
Explanation:
This question tests your knowledge of cycle counting configuration options in Dynamics 365 Supply Chain Management. Cycle counting is a warehouse inventory counting method where specific items or locations are counted on a rotating schedule. The question presents four cycle counting options (User directed, System directed, Cycle count grouping, and Spot cycle count) that need to be matched with five specific requirements for mobile device-based warehouse counting activities.
Correct Option Matching:
Requirement 1: Specify a cycle counting work ID that has a status of Open
Cycle Count Option: User directed
User-directed cycle counting allows workers to specify and select specific cycle count work IDs that have been generated and have an "Open" status. This option gives workers flexibility to choose which counting tasks to perform based on work IDs visible in the system, making it ideal for manually selecting open work IDs from the mobile device.
Requirement 2: Automatically assign a cycle counting work ID to a worker
Cycle Count Option: System directed
System-directed cycle counting automatically assigns cycle count work IDs to workers based on predefined criteria and availability. The system determines the next counting task and directs workers to specific locations, eliminating manual selection and optimizing the counting workflow through automated assignment.
Requirement 3: Group work IDs that are specific to a location, zone, or work pool
Cycle Count Option: Cycle count grouping
Cycle count grouping enables the organization and filtering of cycle count work IDs based on specific criteria such as warehouse location, zone, or work pool. This feature allows efficient management and execution of counts by grouping related work IDs together for streamlined processing.
Requirement 4: Count items in a warehouse location at any time
Cycle Count Option: Spot cycle count
Spot cycle counting allows workers to initiate immediate counts of any warehouse location on demand, without requiring pre-scheduled cycle count work. This flexible option enables ad-hoc counting whenever needed, perfect for addressing immediate inventory verification requirements.
Incorrect Option:
No additional options needed - All four cycle counting options were correctly matched to the five requirements, with "User directed" and "System directed" each assigned to one requirement, and "Cycle count grouping" and "Spot cycle count" each assigned to one requirement.
Reference:
Microsoft Learn: "Set up cycle counting in Warehouse management"
Microsoft Docs: "Cycle counting in Dynamics 365 Supply Chain Management"
Microsoft Learn: "Configure mobile device menu items for cycle counting"
A company is implementing Dynamics 365 Supply Chain Management. The company has 11 legal entities. Each entity uses a separate enterprise resource planning (ERP) system.
A customer may have a unique customer number in each system because the systems are
disconnected. One of the customer numbers will be used as the master number in Dynamics 365.
The company plans to add entities to Supply Chain Management over time. Customer records will continue to be added to the ERP systems throughout the implementation lifecycle and must be kept up to date. The ERP systems will be decommissioned after golive.
You need to create a strategy to migrate the customer data and ensure that new records are automatically mapped.
Which solution should you implement for each requirement? To answer, drag the appropriate solutions to the correct requirements. Each solution 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.
Explanation:
This question tests your knowledge of data migration and integration strategies for Dynamics 365 Supply Chain Management in a complex multi-system environment. The scenario involves 11 separate ERP systems with disconnected customer records that need to be consolidated, with ongoing updates during implementation and eventual decommissioning of legacy systems. You must match the appropriate solutions to three specific requirements.
Correct Option Matching:
Requirement 1: Consolidate on the single master customer number
Solution: Existing ERP system
The existing ERP system that contains the designated master customer number serves as the source of truth for consolidation. During migration, this system's customer numbers will be used as the master identifiers in Dynamics 365, with cross-referencing to maintain relationships with records from other systems.
Requirement 2: Store historical data
Solution: Azure Data Lake
Azure Data Lake provides scalable and cost-effective storage for historical data from all 11 ERP systems. It can store large volumes of raw data in its native format, preserving historical customer information for reporting, analytics, and compliance purposes after the legacy systems are decommissioned.
Requirement 3: Import customer data
Solution: Data Migration Framework
The Data Migration Framework (DMF) in Dynamics 365 Supply Chain Management is specifically designed for importing master data like customers. It supports entity-based import, data validation, transformation, and can handle the complexity of mapping customer records from multiple source systems.
Incorrect Option:
F&O Data Feeds - This solution is not used for any requirement. F&O Data Feeds are typically used for exporting data from Dynamics 365 to external systems for reporting or analytics, not for importing or consolidating customer master data during migration.
Reference:
Microsoft Learn: "Data management and migration in Dynamics 365 Supply Chain Management"
Microsoft Docs: "Data Migration Framework (DMF) architecture and configuration"
Microsoft Learn: "Azure Data Lake integration with Dynamics 365"
Microsoft Learn: "Customer master data management strategies"
| Page 1 out of 11 Pages |