View MB-820 Exam Questions

Q: 1

HOTSPOT You need to create the codeunit to read the POS terminal APIs. How should you complete the code segment? To answer, select the appropriate options in the answer area. NOTE; Each correct selection is worth one point.

Your Answer

Discussion

CarefulNeteng2505 Feb 25, 2026 11:25 pm

Why not ACCESS = PUBLIC for Box 1? Pretty sure that's a common trap, but in this extension context, INTERNAL is correct.

Anita U. Feb 28, 2026 10:37 am

Super clear visual here, makes it easy to spot the right segment. ACCESS = INTERNAL and PROCEDURE READAPI().

Liam J. Feb 21, 2026 3:24 am

ACCESS = INTERNAL and PROCEDURE READAPI() match the usual extension practice. Keeping access internal stops other extensions from using your codeunit by accident, and the procedure needs to fit that OnRun call signature. Pretty sure that fits what the exam expects.

Meera V. Mar 1, 2026 10:08 pm

Practice test questions and the official MB-820 docs always suggest ACCESS = INTERNAL for scoped codeunits, plus procedure readAPI() matches the call signature. These two show up on practice a lot, so pretty sure that's right.

Meera I. Feb 22, 2026 8:12 pm

Isn’t PUBLIC the better pick for Access in box 1 if we want to call it from other places? The procedure maybe needs a parameter too. I saw something similar in an official practice test.

Morgan D. Feb 24, 2026 1:11 pm

ACCESS = INTERNAL and procedure readAPI() fit here. Makes sense because extension scope is internal, and the OnRun calls without params. I’m pretty sure about both picks but open if anyone else spots a catch.

Ben K. Feb 15, 2026 1:09 pm

Seen similar on practice, so for codeunit API handling it's ACCESS = INTERNAL and procedure readAPI().

QuietSec8757 Feb 16, 2026 1:03 pm

Had something like this in a mock. in some practice sets, and I went with ACCESS = INTERNAL for box 1 and procedure readAPI() for box 2. The call from OnRun doesn’t pass any params so keeping it simple lines up. Not 100 percent sure, but fits the pattern I’ve seen, someone let me know if you see another tweak here.

Meera S. Mar 6, 2026 6:43 am

ACCESS = INTERNAL and procedure readAPI() are the best choices. Keeps the codeunit internal to the extension and the procedure matches what's called in OnRun. Pretty confident but let me know if I missed something obvious.

Ishaan E. Feb 24, 2026 11:56 am

Totally see why some pick PUBLIC, but in this use case I'm sticking with ACCESS = INTERNAL.

Be respectful. No spam.

Q: 2

DRAG DROP A company is implementing Business Central. The company has the following requirements for a report: • The report must be loaded for users in a specific location only. • Data entered in the request page must be validated before any further processing. • A filter must be defined for users based on the Department field defined in user setup. You need to implement the given requirements. Which triggers should you use? To answer, move the appropriate triggers to the correct requirements. You may use each trigger once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point.

Drag & Drop

Enable JavaScript to use the Drag & Drop feature.

OnAfterGetRecord
OnlnitReport
OnPreDataItem
OnPreReport

Discussion

Luna H. Feb 27, 2026 10:23 am

Yeah, this matches what I’ve seen in practice sets: Load the report for location = OnInitReport, Validate data = OnPreReport, filter by department = OnPreDataItem. The trap is mixing up when you need request page input vs system-level checks. Pretty sure this is right but open to debate!

SeanA Mar 4, 2026 7:39 am

Ugh, these trigger mapping questions are always awkward.
Load the report for users in a specific location → OnInitReport, Validate data before processing → OnPreReport, Filter based on Department field → OnPreDataItem. Pretty standard as per exam reports-filters tied to data items always go OnPreDataItem. Disagree?

Jordan B. Mar 5, 2026 7:37 am

OnInitReport → Load the report for users in a specific location, OnPreReport → Validate data before processing, OnPreDataItem → Filter by Department field. Confident on this one.

Sean S. Feb 19, 2026 12:04 am

OnInitReport → Load the report for users in a specific location, OnPreReport → Validate data before processing, OnPreDataItem → Filter by Department. I’m pretty sure this covers the intent, but location vs request page can be a trap sometimes!

Noah G. Feb 25, 2026 7:32 pm

Totally agree with the mapping here: OnInitReport for location (checks before the request page), OnPreReport to validate data after user input, and OnPreDataItem for applying the department filter per user. That’s how most exam scenarios break down these triggers. Pretty confident but always worth double-checking if your setup pulls location from user context!

Sam Mar 5, 2026 4:08 am

Load the report for users in a specific location: OnInitReport, Validate data before processing: OnPreReport, Department filter: OnPreDataItem

Ethan Feb 25, 2026 11:17 am

OnInitReport → Load the report for users in a specific location
OnPreReport → Validate data before processing
OnPreDataItem → Filter by Department

I’d map them this way since OnInitReport is your spot to check location or permissions before anything else, OnPreReport gives you a chance to validate what the user entered after the request page, and OnPreDataItem is standard for filtering each user based on something like Department. Pretty sure this is what MS expects-trap is mixing up PreReport and Init if you focus too much on when validations run. Disagree?

Daniel N. Feb 14, 2026 6:55 am

OnInitReport → Load the report for users in a specific location
OnPreReport → Validate data before processing
OnPreDataItem → Filter by Department
Pretty standard mapping seen in most official guides and labs. OnInitReport is best for access checks before any UI, PreReport catches validation right after request page, and PreDataItem is classic for dynamic filtering. I think this matches what exam practice sets expect (feel free to argue if anyone saw different on the exam!).

Jordan Z. Feb 16, 2026 4:34 pm

These drag/drop trigger questions make me crazy.Load location control -> OnInitReport, validate inputs -> OnPreReport, filter by department -> OnPreDataItem.

Arjun H. Feb 17, 2026 5:48 pm

Brings up an edge case: if the location was set dynamically after request page, you’d need OnPreReport, not OnInitReport, for checking.

Be respectful. No spam.

Q: 3

HOTSPOT You create a query that contains a procedure to display the top customers. The procedure breaks at runtime. You need to fix the code. For each of the following statements, select Yes if the statement is true. Otherwise, select No. NOTE: Each correct selection is worth one point.

Your Answer

Discussion

RaviJ Feb 27, 2026 10:12 am

Open() after SetFilter is the fix, not before. Lot of folks miss that trap. Had a similar question, picked the same way.

Priya C. Feb 27, 2026 1:16 pm

Yeah, you need to run Open() after SetFilter because in AL the filter only affects records before opening the query. Replacing with SetRange or wrapping with BEGIN..END wouldn't fix it. Pretty sure that's all the question wants, but open to correction.

Ivy Mar 2, 2026 4:05 am

Why wouldn't Open() before SetFilter work though? Isn't that a common mistake on this type of AL query question?

Alex Q. Mar 5, 2026 12:20 am

Open() after SetFilter is the only fix, based on official docs and practice tests.

CarefulNeteng1578 Feb 20, 2026 10:17 pm

Microsoft loves to trick us with these order-of-operations questions. The only thing that actually fixes the runtime break here is adding Open() after you set the filter, not before. Everything else is a classic distractor. Pretty sure that's what they're after, but open to debate if someone sees differently.

Logan W. Feb 17, 2026 4:37 am

Open() has to be after SetFilter, not before. Filters only take effect if set before opening the query, that's a key AL quirk. So only the option to add Open() right after SetFilter (not before) will actually fix things. Pretty sure this is the intent here, correct me if I missed something obvious.

Owen M. Feb 28, 2026 11:45 pm

Add Open() before SetFilter. That's what I did, figured the runtime break was from not opening the query first.

Sean T. Mar 5, 2026 1:29 pm

Add Open() after SetFilter, not before. Saw a similar trick in another practice. The trap is thinking you need to enclose with BEGIN..END or swap SetFilter for SetRange, but those don’t apply here.

Jordan Y. Feb 26, 2026 11:40 am

Always some weird trick question. I picked add Open() before SetFilter since I figured you need to open the query first, then apply stuff. Might be off though if AL does it differently.

PriyaS Mar 4, 2026 9:15 pm

So with AL queries, you have to apply SetFilter before calling Open() or the filter won't work as expected. I think that's why adding Open() after SetFilter fixes the runtime issue here. Not totally sure about the BEGIN..END part but it looks unnecessary to me. Someone else try this and see the same result?

Be respectful. No spam.

Q: 4

HOTSPOT A company plans to customize its per tenant extension reports. The company has the following requirements for the customization: • Child data items must not be displayed on the request page for some master detail reports. • Selecting key filter fields takes users too much time. The customization must decrease the amount of time to select the fields. You need to optimize the report request page. Which actions should you configure? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

Your Answer

Discussion

Grace V. Mar 5, 2026 5:13 pm

Pretty sure the right steps are set DataItemLinkReference and specify RequestFilterFields, saw similar logic pop up on a practice test.

Nathan Feb 15, 2026 10:06 pm

Set the DataItemLinkReference property and specify RequestFilterFields. Saw this on a similar practice exam, matches what was expected.

Skyler V. Feb 21, 2026 11:18 am

Set DataItemLinkReference on child, and use RequestFilterFields. Saw similar in some MB-820 practice reports.

SharpAnalyst9693 Feb 19, 2026 6:00 pm

Set DataItemLinkReference for the child and configure RequestFilterFields. DataItemLinkReference hides the child from the request page, while RequestFilterFields preselects key filter fields for users. Pretty sure this matches what’s needed for Dynamics report customization, anyone disagree?

Maya X. Feb 23, 2026 8:22 am

Really clear scenario. For hiding child data items on the request page, setting DataItemLinkReference on the child to point to the parent is key, it makes the child tab disappear. For faster field selection, use RequestFilterFields, it lets you pick default filters so users don't have to waste time digging for them. I think these are the best ways to handle both requirements. Anyone see another approach?

Hannah M. Mar 3, 2026 11:47 pm

Set DataItemLinkReference, set RequestFilterFields.

Emma V. Feb 21, 2026 3:42 am

For the first requirement, do you just need to set DataItemLinkReference on the child to its parent so that tab gets hidden on the request page? Also, for reducing filter field selection time, would using RequestFilterFields auto-pick what shows up by default? Or is there another property I'm missing here?

Sam Mar 1, 2026 4:11 am

Set DataItemLinkReference and specify RequestFilterFields. Hiding child data item fully is a trap here, this only targets the request page setup.

Anita F. Feb 16, 2026 9:29 am

Set DataItemLinkReference on the child, and specify RequestFilterFields. That way, the child data item doesn't show up as a separate tab on the request page, and users aren't stuck searching for filter fields. Pretty sure that matches what the question wants, but open to corrections.

Luke B. Feb 23, 2026 4:18 am

Makes sense to just remove the child data item from the report definition. That should hide it. For filter selection, set SelectAllFields.

Be respectful. No spam.

Q: 5

DRAG DROP You need to configure telemetry for the SaaS tenant and test whether the ingested signals are displayed. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Drag & Drop

Enable JavaScript to use the Drag & Drop feature.

Select the Application Insights instance, select Logs and then inspect the Traces table.
Select the environment in the Admin Center and place the connection string in the Application Insights Connection String field.
Create an Azure Application Insights instance by using the Azure Portal in the Partner's subscription.
Create an Azure Application Insights instance by using the Azure Portal in the Customer's subscription.
Select the Application Insights instance, select Events, and then inspect the Traces table.
Select the Sessions menu and then select Restart Environment.

Discussion

Arjun Feb 21, 2026 10:19 pm

Customer's App Insights -> Enter connection string in Admin Center -> Logs, check Traces table

Priya O. Feb 19, 2026 11:02 pm

Create App Insights in customer subscription → set connection string in Admin Center → inspect Logs/Traces. That's the right flow for this scenario if telemetry data stays with the customer. Swap to partner's sub only if ownership required, I think.

Sofia V. Mar 5, 2026 1:27 am

Nah, I don’t think it’s the partner’s subscription. Create in customer’s subscription, set connection string, then inspect Logs table.

AvaS Feb 14, 2026 11:36 am

Create Azure Application Insights in the customer's subscription → set connection string in Admin Center → inspect Logs/Traces table. That's the right order for customer-owned telemetry, pretty sure. Disagree if you think partner's subscription comes first?

Quinn M. Mar 1, 2026 10:08 pm

This one matches official doc steps: Customer's subscription, connect in Admin Center, then Logs Traces table. Practice test covered this too.

Ava U. Feb 21, 2026 2:23 am

I think it's Partner's subscription first, then set the connection string in Admin Center, and finally check the Traces table. Trap is using Customer's subscription right away, but I saw some practice questions use Partner.

Leo P. Feb 17, 2026 12:38 pm

Create Application Insights (partner's subscription), set connection string in Admin Center, then inspect Traces table. Pretty sure this matches what you'd do if the customer didn't specifically require data ownership-the partner setup is a usual trap here. Saw a similar question where just swapping the first step based on ownership changed the answer, so let me know if you read it differently.

Be respectful. No spam.

Correct Answer:

Steps to configure telemetry Bucket 1: D. Create an Azure Application Insights instance by using the Azure Portal in the Customer's subscription. Bucket 2: B. Select the environment in the Admin Center and place the connection string in the Application Insights Connection String field. Bucket 3: A. Select the Application Insights instance, select Logs and then inspect the Traces table.

Explanation

To enable telemetry for a Business Central SaaS tenant, you must first provision an Application Insights resource in the Azure portal. Microsoft best practices recommend using the customer's subscription for data sovereignty. Once created, you copy the Connection String (formerly the Instrumentation Key) and paste it into the specific environment settings within the Business Central Admin Center. This establishes the link. Finally, to verify that signals are being ingested, you navigate to the Logs section of the Application Insights resource and query the traces table, where Business Central telemetry data is stored.

References

Microsoft Learn: Monitoring and Analyzing Telemetry - Enable Application Insights. [Section: "To enable Application Insights on an environment"]. It specifies using the Admin Center to add the Connection String.

Microsoft Learn: Business Central Telemetry Overview. [Section: "Azure Application Insights"]. Explains that telemetry data is sent to the traces table in Application Insights.

Microsoft Learn: Telemetry FAQ. [Section: "Which Azure subscription should I use?"]. Confirms the recommendation to use the customer's subscription for SaaS environments.

Microsoft Dynamics 365 Business Central Documentation: Environment Management - Telemetry. Detailed steps on configuring the connection string via the Business Central Administration Center.

Q: 6

HOTSPOT You need to create the API page according to the requirements. How should you complete the code segment? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

Your Answer

Discussion

Ben T. Feb 14, 2026 7:19 am

Looks like DATAACCESSINTENT = READONLY and EDITABLE = FALSE is correct. DATAACCESSINTENT tells Business Central to use the read-only replica and EDITABLE disables all modifications, not just inserts. Pretty sure that's what Microsoft expects here but open to corrections.

Taylor Mar 2, 2026 7:58 pm

DATAACCESSINTENT = READONLY, EDITABLE = FALSE

LiamY Feb 27, 2026 12:43 pm

Looks right to me, DATAACCESSINTENT = READONLY, EDITABLE = FALSE.

Jordan K. Mar 3, 2026 11:20 am

DATAACCESSINTENT = READONLY, EDITABLE = FALSE. Not InsertAllowed here, that's a common trap when folks mix up insert restriction with full read-only. Pretty sure this matches what MS wants for the API page.

Nathan G. Feb 25, 2026 4:19 pm

Pretty sure I ran into a similar one in exam. on a practice test and the right combo is DATAACCESSINTENT = READONLY and EDITABLE = FALSE. Setting EDITABLE = FALSE is what truly locks the page in read-only mode, not just inserts but all edits. Pretty sure that's what Microsoft expects for this scenario.

PreciseSec5329 Feb 28, 2026 12:24 pm

Would setting Editable = false alone make the API page fully read-only, or do we still need to set InsertAllowed or ModifyAllowed separately?

Ivy P. Feb 16, 2026 5:55 pm

Practice labs and the official docs nail this: DATAACCESSINTENT = READONLY, EDITABLE = FALSE.

KevinG Feb 19, 2026 6:30 am

Totally agree with DATAACCESSINTENT = READONLY, EDITABLE = FALSE for strict read-only. InsertAllowed trips people up here.

Owen Z. Mar 1, 2026 2:41 pm

Yeah, Editable = false is what you want for fully read-only API pages. InsertAllowed just stops new records but doesn't block updates to existing ones. DataAccessIntent = ReadOnly points the page at the replica, helps performance too. Pretty sure that's what's expected unless they ask about inserts only.

Owen Feb 15, 2026 7:17 am

Looks like it should be DataAccessIntent = ReadOnly and Editable = false. That covers both the API page using a read-only replica and blocking all data changes. InsertAllowed isn’t needed if you want the whole thing non-editable, pretty sure on this.

Be respectful. No spam.

Q: 7

You need to define the tables used for the non-conformity entity. What should you use?

Options

Discussion

Arjun A. Feb 14, 2026 8:41 am

B, not C

Robin H. Feb 14, 2026 6:58 pm

Its B. This is where you define the main entity in Dynamics, not the details/history. Makes sense based on data structure here.

ReeseA Feb 25, 2026 8:47 am

Probably B. The question says entity, so it's got to be the document table, not supplemental (that's more for line details). A is just a distractor about history.

Hannah Feb 19, 2026 5:01 am

That lines up for me, definitely B. Document table defines the entity itself, not just the history or lines.

Emma E. Feb 23, 2026 10:17 am

Had something like this in a mock, went with B since document table is for the main entity.

NinaX Feb 26, 2026 6:26 am

B tbh

Ajay P. Feb 15, 2026 7:21 pm

Honestly not 100% but I'd go for B here. The entity itself usually means document table in Dynamics setups, right? C feels more for lines/details. Correct me if I'm off.

Owen Feb 21, 2026 4:28 pm

I think it's C here. The supplemental table feels like the right choice for handling non-conformity since you sometimes need those extra lines. Maybe I'm missing something, but B seems more for documents, not this case. Agree?

Nora M. Feb 17, 2026 7:37 pm

My pick: it's B. In Dynamics, the document table is what you use to define and introduce the main entity like non-conformities. The others are more for details or history. I've seen similar logic in the official docs and some practice tests. Someone correct me if supplemental ever works for the core entity?

HannahU Feb 21, 2026 1:54 pm

Option B makes more sense to me. The document table sets up the core entity definition, not just the history. A is a trap since document history is about tracking changes, not introducing the entity. If I’m misunderstanding the role of the supplemental table though, let me know.

Be respectful. No spam.

Correct Answer:

Explanation

In the data architecture of Dynamics 365 Supply Chain Management, transactional entities such as non-conformances are defined using a standard pattern. The primary table, which holds the main header information for each unique non-conformance record (e.g., non-conformance ID, date, problem type, status), is referred to as a document table. This table serves as the foundation for the non-conformity entity. While other tables may store related details like corrections or logged history, the document table is the essential component used to introduce and define the core entity.

Why Incorrect

A: A document history table is designed to store posted, finalized transactions for archival and auditing purposes, not to define active, in-process entities like a new non-conformity.

C: While a non-conformity can have related details, the term "supplemental table for lines" is not the standard architectural component for defining the main entity itself; it would hold subordinate detail records.

References

1. Microsoft Learn. "Create and process a nonconformance." Dynamics 365 Supply Chain Management Documentation. This document outlines the process of creating a new non-conformance, which involves creating a new record in the main header table (InventQualityOrderTable), demonstrating the role of a central document table in defining the entity.

2. Microsoft Learn. "Tables in finance and operations apps." Finance and Operations apps development Documentation. This article discusses table properties, including the TableGroup property. The primary table for non-conformances (InventQualityOrderTable) belongs to the Transaction group, which is characteristic of document tables that hold the main records for business events.

Q: 8

You are customizing Business Central by using Visual Studio Code. You create a project that will extend Business Central. The AL extension contains JSON files, which are automatically generated and are used to store configuration data For testing purposes, you plan to add the following changes to the files: • Specify that page 21 must be opened after publishing. • Enable debugging • Disable the capability to download the source code You need to add the configurations to the JSON files. Which two configurations should you add? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.

Options

Discussion

Alex B. Feb 14, 2026 6:05 pm

C and E imo. The startupObjectId and resourceExposurePolicy settings controlling debugging/source download are meant to be in app.json, not launch.json. Launch.json is more for session-specific stuff, so these config changes have a lasting effect in app.json. Pretty sure that's what MS docs say too, but open to other views.

Meera Feb 19, 2026 4:02 pm

Always get confused by where these resourceExposurePolicy configs go. Pretty sure C and E this time.

Chloe G. Feb 15, 2026 11:07 am

Maybe B and C. Launch.json is usually where you set up startup object and enable debugging when testing in VS Code, so I thought you'd configure those there. The resourceExposurePolicy can appear in both, so that's why I'm not 100% sure. Official docs or some hands-on lab would help clarify this one for me. Disagree?

Luke J. Feb 21, 2026 6:24 am

B , because launch.json also handles debugging and object to start, but maybe I'm missing something with where resourceExposurePolicy is used.

Aisha N. Feb 19, 2026 1:40 pm

Nah, not B. The resource exposure policy with allowDebugging and allowDownloadingSource set goes in app.json, so C and E.

Quinn Y. Feb 21, 2026 6:21 pm

Its B and D

Leo G. Feb 25, 2026 8:39 am

I don't think it's B. C and E are correct since only app.json controls both startupObjectId and resourceExposurePolicy in a deployed extension. Launch.json is just for debugging configs, easy trap.

Meera Feb 20, 2026 9:42 am

C/E. Only app.json controls startupObjectId and resourceExposurePolicy for live extensions, not launch.json. Pretty sure that's what they're after here.

Hannah Mar 4, 2026 10:45 am

I’d say C and E, since only app.json stores those persistent extension settings. Launch.json's configs would be ignored for these requirements.

OliviaT Feb 22, 2026 12:28 am

I don’t think it’s B. C and E since launch.json is just for local debug, not real config.

Be respectful. No spam.

Correct Answer:

C, E

Explanation

The app.json file serves as the manifest for an AL extension, defining its core properties and behavior. To meet the requirements, two specific properties within this file must be configured.

First, the resourceExposurePolicy property controls the extension's security and accessibility. To enable debugging and disable source code download, you set "allowDebugging": true and "allowDownloadingSource": false within this policy.

Second, the startupObjectId property in app.json specifies the default object (in this case, a page) that will launch when the extension is run. This sets the desired startup page for testing and general use. Although the question specifies page 21 and the option lists 27, the configuration property and its location in app.json are correct for the stated purpose.

Why Incorrect

A. While startupObjectId can be set in launch.json, this file is for developer-specific launch configurations and overrides the app.json manifest setting only during a debugging session from VS Code.

B. The resourceExposurePolicy property is not valid for the launch.json file; it belongs exclusively in the app.json manifest. Also, "at low Debugging" is not a valid property name.

D. This option incorrectly sets allowDownloadingSource to true, which contradicts the requirement to disable the capability to download the source code.

References

1. Microsoft Learn: App.json file. This document details the properties of the extension manifest file.

Section: resourceExposurePolicy Property: "Specifies the exposure policy for the resources of the extension." It lists allowDebugging and allowDownloadingSource as valid keys.

Section: startupObjectId Property: "The ID of the object to run on startup."

2. Microsoft Learn: Launch.json file. This document explains the launch configuration file for debugging.

Section: startupObjectId Property: "Specifies the ID of the object to run for the startup company. This setting will override the startupObjectId property in the app.json file." This confirms that launch.json is an override, while app.json is the primary manifest setting.

Q: 9

DRAG DROP A company plans to deploy Business Central. The company has the following deployment requirements: • Use the company hardware architecture to run the deployment. • Use sandbox environments to develop extensions. • Allow tenants to connect to Shopify with the standard connector. • Use Microsoft Power Automate to create a workflow that calls a business event. You need to identify the deployment type for each requirement. Which deployment types should you use? To answer, move the appropriate deployment types to the correct requirements. You may use each deployment type once, more than once, or not at all.

Drag & Drop

Enable JavaScript to use the Drag & Drop feature.

On-premises
Online

Discussion

PracticalDev8468 Mar 4, 2026 7:27 pm

Run on company hardware: On-premises, rest all: Online. Confident based on Business Central features.

LunaD Mar 1, 2026 11:01 am

Run on company hardware: On-premises, rest all: Online. No doubt for these mappings imo.

Aaron Feb 24, 2026 10:28 am

Sandbox, Shopify, and workflow only work right in Online, company hardware is On-premises. One tricky part is sandboxes-On-premises has test setups but not true sandboxes like Online. Disagree if I missed a detail.

Priya Feb 18, 2026 4:01 am

Run on company hardware: On-premises, rest go Online. Shopify connector and workflow features are only built into Online as standard, saw people get tripped up thinking sandbox might work with On-prem but that's not default. Pretty sure this is the intended mapping, anyone disagree?

Piya A. Feb 13, 2026 6:52 pm

Yeah this matches what I’ve seen on similar questions. On-premises is the only way to meet the hardware requirement, but sandbox, Shopify connector, and Power Automate workflows are all standard features in Online. Easy to miss the Shopify trap here!

Run on company hardware: On-premises
Sandbox envs/extensions: Online
Shopify connect: Online
Workflow: Online

Arjun M. Mar 3, 2026 9:15 am

Had something like this in a mock. My mapping: Run on company hardware is On-premises, the rest go with Online. Sandboxes, Shopify connector, and Power Automate workflows are all fully available only in the Online deployment, not On-prem. Pretty sure this matches how MS expects you to sort it out (but open to correction if anyone knows otherwise).

Arjun D. Feb 21, 2026 1:59 pm

Run on the company hardware: On-premises, rest: Online. Confident this is what MS expects.

Olivia Feb 25, 2026 7:42 am

Run on company hardware: On-premises, rest: Online. Shopify is a trap for On-prem, only fully supported in Online I think.

Adam W. Feb 25, 2026 6:21 am

Run on the company hardware: On-premises, rest go to Online (sandbox, Shopify, workflow). The trap is thinking sandboxes or Shopify are supported on-prem but they're really SaaS features. Seen this mapping in similar questions. Disagree if I'm off.

Cameron P. Mar 6, 2026 5:17 am

Run on company hardware: On-premises, sandbox environments: On-premises, Shopify connection: On-premises, workflow: Online. Saw similar mapping on a practice exam.

Be respectful. No spam.

Q: 10

HOTSPOT You create a 'Contoso Post" procedure to send an http POST request in JSON format. You publish the procedure to your environment. You write the following procedure code: The procedure does not work as expected. You need to find and fix all errors in HTTP class usage. For each of the following statements, select Yes if the statement is true. Otherwise, select No. NOTE: Each correct selection is worth one point.

Your Answer

Discussion

Piya Feb 26, 2026 10:23 pm

Yep that matches the official pattern. Yes, Yes, No.

Ivy Z. Mar 5, 2026 8:17 am

Should line 16 actually be ResponseMessage.Content.ReadAs(ResponseText)? Not sure if ReadAs used directly on ResponseMessage ever works in AL. Anyone seen this behave differently?

Zoe B. Mar 1, 2026 10:56 am

Makes a difference if you know that ReadAs isn't on the HttpResponseMessage itself. No for line 16.

Morgan C. Feb 24, 2026 9:54 am

Bit of an edge case here: if they specified a custom response object that had ReadAs directly, line 16 would be Yes. With standard AL though, it's Yes, Yes, No.

FriendlyOps2334 Feb 20, 2026 7:45 pm

Yes for line 10 and line 11, No for line 16. WriteFrom and GetHeaders are used right in the AL HTTP classes, but ReadAs can't be called straight off ResponseMessage. That's usually where people get tripped up if coming from a C# background.

Sam X. Feb 24, 2026 11:08 am

If the response variable was already the content, would ReadAs work on line 16? I think it's only a problem if you skip ResponseMessage.Content, right?

Daniel Mar 1, 2026 2:12 pm

Wasn't this in a mock recently? It's Yes for line 10 and 11, No for line 16.

Sanjay F. Feb 14, 2026 6:31 pm

Yes, Yes, No. Had something like this in a mock and that's how it was keyed.

Drew H. Feb 24, 2026 2:31 pm

Yes, Yes, No. Official docs and practice questions always treat ReadAs as a method on the content, not the response. If you want to be sure for exam day, reviewing some real AL HTTP class code samples helps a ton.

Logan B. Feb 18, 2026 6:01 pm

Official docs and lab walkthroughs back this answer: Yes, Yes, No.

Be respectful. No spam.

Question 1 of 20 · Page 1 / 2

Premium Access Includes

✓ Quiz Simulator
✓ Exam Mode
✓ Progress Tracking
✓ Question Saving
✓ Flash Cards
✓ Drag & Drops
✓ 3 Months Access
✓ PDF Downloads

Get Premium Access

📖 About this Domain

🎓 What You Will Learn

🛠️ Skills You Will Build

💡 Top Tips to Prepare

📖 About this Domain

🎓 What You Will Learn

🛠️ Skills You Will Build

💡 Top Tips to Prepare

📖 About this Domain

🎓 What You Will Learn

🛠️ Skills You Will Build

💡 Top Tips to Prepare

Premium Access Includes

FLASH OFFER

avail 10% DISCOUNT on YOUR PURCHASE