Explanation:
The requirement is to expose Business Central data for consumption by Power BI. The core step is to make the data accessible via a standard API that Power BI can connect to. While setting up a user account is part of the connection process, it is not the primary action for exposing the data itself.

Correct Option:

A. Enable the Power BI Embedded service.

Explanation:
This is the most direct and complete action. Power BI Embedded is a service in the Business Central admin center. Enabling it automatically creates and publishes a set of default OData web services (APIs) optimized for Power BI, making Business Central data directly available for Power BI to connect to and consume.

Incorrect Options:

B. Publish the OData web services for the required entities:
This is technically correct as a method, but it is a manual, developer-focused task. The standard, recommended administrative method to achieve this in the context of Power BI integration is to Enable the Power BI Embedded service (Option A), which handles this publishing automatically.

C. Select the Share action in Business Central:
The Share action in Business Central is used to share links to specific pages or reports within Business Central or via email. It does not expose data APIs for external consumption by Power BI.

D. Create a user account in Business Central for Power BI access:
While Power BI needs authentication (often via a service account), creating a user account is a prerequisite for connecting, not for exposing the data. The data must first be exposed as a service (via OData) before a user account can access it from Power BI.

Reference:
Microsoft Learn documentation "Enable Power BI Integration in Business Central Online." The standard procedure is to enable the Power BI Embedded service in the admin center, which automatically configures the necessary web services and environment settings for Power BI reporting.

Explanation:
To correct an incorrectly posted purchase receipt while keeping the purchase order open for further processing, you use the Undo Receipt function. The process involves locating the posted receipt from the related order and then performing the undo action. You do not need to change the order's status first.

Correct Option Sequence:

The correct sequence to undo a posted purchase receipt is:
Open the purchase order that is with the receipt. (Navigate to the original purchase order from which the receipt was posted.)

Choose Receipts and then open the incorrectly posted receipts. (From the purchase order, go to Related > Order > Receipts to view the list of posted receipts for that order.)

Select a line to be cancelled from the posted purchase receipt. (Open the specific posted receipt document and select the line(s) you need to undo.)

Select Undo Receipt. (With the receipt line selected, choose the Undo Receipt action. This creates a negative purchase receipt to reverse the original, and the purchase order's Quantity Received is reduced.)

Incorrect Options:

Change the status of the purchase order from Release to Open:
This is not a required step. You can undo a receipt from a released purchase order without changing its status.

Select Cancel:
The Cancel action is for voiding an entire unpaid posted invoice, not for reversing a posted receipt. The correct action for reversing a receipt is Undo Receipt.

Reference:
Microsoft Learn documentation "Undo Purchase Receipts." The documented process is to find the posted receipt from the purchase order and use the Undo Receipt action to reverse it, returning the items to a "not received" status on the order.

Explanation:
Transferring opening balances, such as G/L account balances, customer/vendor ledger entries, and inventory values, is a standard data migration task. Business Central supports importing data through CSV files, typically by using the Configuration Worksheet or RapidStart implementation tools, which allow for data mapping and import of master and transactional data, including opening balances.

Correct Option:

A. Yes

Explanation:
Using CSV files is a valid and common method to transfer opening balances into Business Central. This is typically done via the Configuration Packages feature, where you prepare CSV templates, map fields, and import the data. It is a standard data migration approach for initial setup.

Incorrect Option:

B. No:
This is incorrect because importing via CSV is a supported and documented method for data migration. While other methods exist (like the Copy Company function or manual journals), the CSV import via configuration packages is a flexible and effective solution for transferring opening balance data.

Reference:
Microsoft Learn documentation on using "Configuration Packages" to migrate data. Configuration packages use Excel/CSV files to import data for tables, including the General Ledger Entry and Customer/Vendor Ledger Entry tables, which is how opening balances are brought into the system.

Explanation:
To ensure a G/L account balance matches the sum of related sub-ledger balances (reconciliation), you must prevent transactions from being posted directly to the G/L account. This forces all entries to flow through the sub-ledger (e.g., Customer Ledger), ensuring the G/L account (Accounts Receivable) is only updated via posting groups from those sub-ledger entries.

Correct Option:

B. Disallow direct posting.

Explanation:
On the G/L Account Card, setting the Direct Posting field to No prevents users from posting journal entries directly to that account (e.g., Account 1200 - Accounts Receivable). All postings to the account must come from sub-ledger transactions (like sales invoices and payments) via the Customer Posting Group. This guarantees the receivables control account always equals the sum of detailed customer ledger balances.

Incorrect Options:

A. Configure Totaling:
The Totaling field is used to create a header account that shows the sum of a range of sub-accounts (e.g., account 1110 totals 1111..1119). It does not enforce reconciliation with sub-ledgers.

C. Configure the account type:
The Account Type (e.g., Posting, Heading, Total) defines the account's purpose but does not control how postings are made or enforce reconciliation.

D. Block the account card:
There is no "Block" action for an account card. Even if an account is marked as Blocked, it prevents any postings (including from sub-ledgers), which would break the accounting system, not reconcile it.

Reference:
Microsoft Learn documentation on "Reconcile the Bank Account" and setting up G/L accounts. To maintain reconciliation between a control account (like Accounts Receivable) and its sub-ledger, a standard practice is to disallow direct posting to the control account in the G/L.

Explanation:
To restrict specific dimension value combinations, you must first define the overall interaction rule between the two dimensions involved. Then, you define the specific allowed or blocked combinations for their respective values. The process flows from general dimension-level rules to specific value-level rules.

Correct Option Sequence:

The correct order to set up restricted dimension combinations is:
Open the Dimensions Combinations page. (Navigate to Dimensions > Dimension Combinations to set the high-level rule between two dimensions, e.g., Department and Project.)

Select the dimensions combination and set the option to Limited. (For the chosen dimension pair, set the Combination field to Limited. This enables the definition of specific allowed value combinations; all others become blocked.)

Open the Dimension Value Combinations page. (With the dimension pair set to Limited, you can now access the Dimension Value Combinations page to define the specific allowed pairings.)

Select the dimension value combinations and set the option to Blocked. (On the Dimension Value Combinations page, you select the specific value pairings (e.g., Department=A, Project=X) and mark them as Blocked to disallow them, or conversely, mark others as Allowed.)

Incorrect Options:
Any sequence that attempts to configure Dimension Value Combinations before setting the parent dimensions' combination to Limited on the Dimensions Combinations page is incorrect. The Limited setting is the prerequisite that unlocks the ability to define specific value-level restrictions.

Reference:
Microsoft Learn documentation "Set Up Dimension Combinations." The process is: 1) On Dimension Combinations, select two dimensions and choose a restriction level (No Limit, Same Code, Limited). 2) If Limited is chosen, proceed to Dimension Value Combinations to define the specific allowed or blocked pairings.

Explanation:
The requirement is to control the display of decimal places for monetary amounts in the local currency. This is a formatting rule for how amounts appear in fields and reports, not a rule for rounding calculations during posting.

Correct Option:

A. Set the value of Amount Decimal Places to 3:3

Explanation:
In General Ledger Setup, the Amount Decimal Places field controls the number of decimal places displayed for amounts in the local currency. The format x:y means minimumx and maximumy decimals. Setting it to 3:3 forces amounts to always show exactly three decimal places (e.g., 100.000).

Incorrect Options:

B. Set the value of Unit-Amount Decimal Places to 3:3:
This field controls decimal display for unit amounts (like item prices), not for general monetary amounts in the local currency.

C. Set the value of Inv. Rounding Precision to 0.001:
This field determines the smallest rounding unit for invoice totals (e.g., rounds to the nearest 0.01). It affects calculation rounding, not display formatting.

D. Set the value of Unit-Amount Rounding Precision to 0.001:
This determines the rounding precision for unit prices, not for display formatting of general monetary amounts.

E. Set the value of Amount Rounding Precision to 0.001:
This field sets the rounding precision for individual amounts in journal lines and documents. It affects how figures are rounded during posting, not how they are displayed on screen.

Reference:
Microsoft Learn documentation for "General Ledger Setup." The Amount Decimal Places field is explicitly described as defining how many decimal places to display for amounts in the LCY. The other fields control rounding precision for calculations, not display.