Q: 3
Note: This question is part of a series of questions that present the same scenario. Each question in
the series contains a unique solution that might meet the stated goals. Some question sets might
have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these
questions will not appear in the review screen.
You need to transfer opening balances data into the system.
Solution: Import the data by using comma-separated values (CSV) files.
Does the solution meet the goal?
Options
Discussion
A. Practice tests and the official Dynamics docs mention CSV imports for this. Pretty sure A is fine here.
A imo. The trap is thinking you need something more automated, but CSV imports are standard for uploading opening balances in Dynamics. Unless they mention automation or extra validation, A's fine.
I don’t think it’s B. A is fine-CSV imports are a basic way to get opening balances into Dynamics and meet the requirement here. Not the only possible method, but it does work. Anyone see a reason it wouldn’t?
B doesn’t fit, A. . Official practice tests cover this, and the Dynamics user guide says CSV imports are fine for opening balances.
Option A
A tbh. Sometimes B looks tempting if thinking about automation, but importing opening balances via CSV is definitely supported here.
Makes sense to me, that's A. Importing opening balances with CSV files is supported in Dynamics 365, and it's a standard way for data migration like this. Pretty sure that's what MS recommends too. Let me know if you see a problem with this approach.
Probably A. Importing via CSV files is a standard method for bringing opening balances into Dynamics, and as long as the format matches, it usually works without extra tools. I think that's all they're asking for here, unless there's a hidden requirement I'm missing. Anyone see a reason why B would be better?
I think it's A. CSV import is the go-to for uploading opening balances in Dynamics, nothing fancy needed here. Unless the scenario calls for scheduled or automated imports, this covers it. Anyone disagree?
A or B? Pretty sure it's A, since importing opening balances thru CSV is basic Dynamics functionality, but B might look tempting if you're overthinking security. Not seeing any reason why a plain CSV wouldn't meet the goal in this scenario.
Be respectful. No spam.
