Are you preparing for an LS Central (LS Retail) developer or technical consultant interview? Then this is the resource you need. This post gathers 105 LS Central technical interview questions with clear, interview-ready answers, drawn from my 18+ years of building and reviewing LS Nav, LS Central, and Business Central AL solutions for retail and hospitality clients.
Moreover, the questions are grouped into three experience levels so you can jump straight to your band. In addition, there is a free online mock exam at the end. Best of all, the exam rotates its questions, so each retake shows you a fresh set instead of the same 15 every time.
📝 Note: Click any question to expand the answer. However, treat these as concise reference answers. In a real interview, you should expand them with code and customizations you have actually shipped on retail projects.
🚨 Caution: LS Central is an AL app on top of Business Central, so technical interviews blend both. Therefore, revise core AL too: 105 Business Central technical interview questions. For the functional side of retail, see 105 LS Central functional interview questions.
🟢 Beginner
0–2 Years · Q1–Q40 🟠 Experienced
2–6 Years · Q41–Q75 🔴 Expert
6+ Years · Q76–Q105 🎯 Mock Exam
15 MCQs · Rotating
0–2 Years · Q1–Q40 🟠 Experienced
2–6 Years · Q41–Q75 🔴 Expert
6+ Years · Q76–Q105 🎯 Mock Exam
15 MCQs · Rotating
Table of Contents
🟢 Beginner LS Central Technical Interview Questions (0–2 Years)
These beginner-level LS Central technical interview questions cover the LS Central architecture, POS objects, and core retail data model. If you are new to LS Retail development or coming from plain Business Central AL, you should therefore master all 40 before your interview. Furthermore, these basics come up in almost every screening round.
1. What is LS Central from a technical standpoint?
Technically, LS Central is a collection of AL extensions (an app) published on top of Microsoft Dynamics 365 Business Central. It adds retail/hospitality tables, pages, codeunits, and its own POS engine, while reusing the Business Central platform and Dataverse-free AL runtime.
2. How is LS Central packaged and installed?
It ships as one or more signed .app extension packages with dependencies declared in
app.json. You install it into a Business Central environment like any other app, respecting version and platform compatibility.3. What language do you use to customize LS Central?
AL in Visual Studio Code, the same language used for Business Central. Older LS Nav used C/AL, so legacy code may still exist that needs conversion to AL for LS Central.
4. How do you extend LS Central without breaking upgrades?
You build a separate extension that depends on the LS Central app and use events, table/page extensions, and interfaces. Consequently, you never modify LS Central objects directly, keeping your customization upgrade-safe.
5. What object ID range should your LS Central customization use?
Your custom extension uses the 50000–99999 range (or an assigned AppSource range). Importantly, you must avoid the ID ranges reserved by LS Central and Microsoft to prevent conflicts.
6. How do you declare a dependency on the LS Central app?
In
app.json, add the LS Central app to the dependencies array with its id, name, publisher, and minimum version. As a result, your extension can reference LS Central objects and events.7. What is the POS in LS Central architecturally?
The POS is a page-based application driven by POS commands and a menu/panel model. Buttons trigger POS commands (functions) that run AL logic, so the register UI is highly configurable through data, not hardcoded screens.
8. What is a POS Command?
A POS Command is a named action bound to a POS button (e.g., PAY, ITEM, VOID, MEMBER). Each command maps to logic in the POS engine. You can add custom commands via extension for bespoke functions.
LS Central Technical Interview Questions on the Data Model
9. Which core tables store retail item data in LS Central?
The base is the Business Central Item table, extended with LS Central retail data such as Barcodes, Item Variants, Retail hierarchy links, and price/offer tables. Retail attributes are added via table extensions and related tables.
10. How are POS transactions stored?
POS sales are held in Transaction header and line tables (sale lines, payment/tender lines, discount lines, infocode lines). These raw transactions are later consumed by the statement posting process.
11. What is the difference between a Transaction table and Item Ledger Entry?
The POS Transaction tables hold the raw register data. Item Ledger Entries are the Business Central inventory entries created later when the statement posts. Therefore, POS data and ledger data are separate stages.
12. How does a barcode resolve to an item at the POS?
The scanned code is looked up in the Barcode table, which maps to the item number, variant, and unit of measure. The POS then loads the item, price, and tax for that resolved combination.
13. How is the retail hierarchy modeled?
Through hierarchy and hierarchy node tables linking divisions, item categories, product groups, and items. This structure drives POS navigation, offers, and reporting. It is a common beginner LS Central technical interview question.
14. What tables drive pricing and offers?
Price is stored in Price tables (by store, price group, currency), and offers in Offer/Discount tables (Multibuy, Mix & Match, etc.) with validation and line tables. The POS calculation engine reads these at sale time.
15. What is a Retail Setup / functionality profile technically?
Profiles are configuration records (functionality, hardware, interface/menu) stored in setup tables and referenced by terminals. The POS reads them at startup, so behavior and layout come from data, not code.
16. How are members and loyalty stored?
In Member, Member Card, Member Account, and Point Entry tables. The POS links a sale to the member, and point entries record earning/redemption, all readable for reporting and cross-channel loyalty.
17. How do you find which table or field a POS value comes from?
Use the Page Inspection (Ctrl+Alt+F1) and table/field references in VS Code, plus the LS Central object documentation. Consequently, you can trace a POS value back to its source table reliably.
18. What is the difference between master data and transaction data replication?
Master data (items, prices, offers, profiles) is pushed out to stores. Transaction data (POS sales) flows back to head office. The Scheduler/replication jobs move both in the correct direction and sequence.
Development Environment and Tooling Questions
19. What tools do you need to develop for LS Central?
VS Code with the AL Language extension, the LS Central symbols (from the installed app), a development sandbox environment, and the LS Central and Business Central documentation. Additionally, source control (Git) is standard.
20. How do you get LS Central symbols to reference its objects?
Download symbols from the environment where LS Central is installed (
AL: Download Symbols), and declare LS Central in app.json dependencies. As a result, IntelliSense exposes LS Central objects and events.21. How do you publish and test a customization against LS Central?
Publish your extension (F5) to a sandbox that already has LS Central installed. Then test on a configured POS terminal and back office, since retail behavior only shows correctly with the full LS setup.
22. What is a POS unit / terminal from a testing perspective?
A configured terminal record with store, hardware, functionality, and interface profiles. You need a working terminal to test POS commands, receipts, tenders, and offers realistically.
23. How do you debug POS logic?
Attach the AL debugger and set breakpoints in the POS command handlers/events you are extending. Then run the action on the terminal to step through the logic and inspect variables.
24. What is Snapshot debugging useful for in retail?
It captures a running (even production) session for later replay, which is invaluable for reproducing intermittent POS or statement issues that only occur under real store conditions.
25. How do you version and source-control LS Central customizations?
Store the AL project in Git, use semantic versioning in
app.json, branch per feature, and ideally automate builds. Consequently, changes are traceable and releases are repeatable.26. What is the difference between extending LS Central and extending Business Central?
Technically both use AL. However, LS Central adds retail objects and its own event/command model, so you often subscribe to LS Central events and extend LS tables rather than only base BC objects.
POS Extensibility Basics Interview Questions
27. How do you add a custom button to the POS?
Configure a POS menu button that calls a POS command, then bind logic to that command (standard or custom). Simple additions are configuration; custom behavior needs an extension subscribing to the command.
28. How do you create a custom POS command?
Register a new POS command via LS Central’s extensibility (command registration event) and implement its handler in a codeunit. The button then invokes your AL logic when pressed.
29. What is an Infocode technically?
An infocode is a configurable prompt record triggered on items, tenders, or actions to capture extra data. The captured values are stored on infocode lines linked to the transaction.
30. How do you customize a POS receipt?
Modify the print/receipt template (sections and fields) and, for logic, subscribe to receipt/print events. As a result, you can add logos, tax breakdowns, loyalty messages, or custom lines.
31. How do you add a field to the POS view?
Extend the relevant POS data table and the panel/grid configuration, and subscribe to the events that populate the view. The POS then displays your custom field.
32. How do you extend the retail item card?
Use a tableextension on the item (and pageextension on the retail item card) to add fields, and populate/validate them via triggers or events. This is a very common LS Central technical interview question.
33. What is the difference between a report and a POS-driven print?
A report is a standard AL report object for back-office documents. A POS print uses the receipt/print template engine optimized for thermal printers at the register.
34. How do you localize LS Central text (labels/captions)?
Use AL Label/TextConst with translations (XLIFF files) and set the target languages. LS Central also has its own captions; translations are managed per language for POS and back office.
35. How are permissions handled for POS staff technically?
Through permission sets plus LS Central staff/role configuration. The functionality profile and staff permissions control which POS commands each user can run, enforced at the terminal.
36. What is a Number Series in the LS Central context?
Standard BC No. Series assigned to terminals, stores, and documents so receipts, transactions, and statements get unique numbers. Terminal-specific series prevent collisions across registers.
37. How do you handle multiple units of measure and barcodes in code?
Read the barcode-to-UoM mapping and the item unit-of-measure setup, then apply the correct quantity/price. Extensions must respect UoM conversion to avoid pricing errors at the POS.
38. How do you capture custom data during a sale?
Use infocodes for prompts or subscribe to sale-line events to write to a custom table linked to the transaction. Then include that data in statement posting or reporting as needed.
39. What is the Scheduler (replication) technically?
A set of jobs and subjobs defining tables/filters to replicate between head office and stores, with dependencies and sequencing. Developers configure and sometimes extend these to include custom tables.
40. How do you include a custom table in replication?
Add the custom table to the relevant replication job/subjob with the correct direction and filters, ensuring keys and dependencies are respected so stores receive or return the data correctly.
💡 Tip: For beginner LS Central technical interview questions, be ready to add a field to the retail item and surface it on the POS. Therefore, practice a small end-to-end extension (table extension + POS view change) on a demo terminal.
🟠 Experienced LS Central Technical Interview Questions (2–6 Years)
These mid-level LS Central technical interview questions test the POS engine, events, statement posting internals, replication design, and integrations. Furthermore, expect coding scenarios: “how would you extend this POS behavior or posting step without modifying LS Central?” If you have shipped 2+ retail extensions, you should handle all of these.
POS Engine and Events Interview Questions
41. Explain the LS Central POS command/event model.
The POS runs on a command-driven engine: buttons raise POS commands, which fire events at defined points (before/after command, on sale line insert, on payment). You extend behavior by subscribing to these events, never by editing LS objects.
42. How do you register and handle a custom POS command end to end?
Subscribe to the command registration event to declare your command, then subscribe to the command execution event to run your AL logic. Finally, bind a menu button to the command in configuration.
43. How do you influence the POS sale line as it is added?
Subscribe to the sale line insert/modify events to adjust price, quantity, discounts, or custom fields. However, respect the calculation order so your changes are not overwritten by later engine steps.
44. How does the POS price and discount calculation flow work?
The engine resolves base price → price groups → offers/discounts → totals in a defined sequence. Understanding this order is essential to inject custom pricing at the right event without breaking existing offers.
45. How do you extend tender/payment processing?
Subscribe to tender/payment events or add a custom tender type with a handler. For card/EFT, integrate through the certified payment connector rather than reimplementing authorization.
46. How do you handle offline POS and data synchronization technically?
In distributed/offline models, the terminal buffers transactions locally and syncs when connectivity returns. Your customizations must be sync-aware, avoiding assumptions that head-office data is always reachable in real time.
47. How do you add a custom panel or view to the POS screen?
Extend the POS view/panel configuration and data provider, then subscribe to the events that populate it. Keep rendering light, since the POS must stay responsive during busy trading.
⚠️ Warning: The POS command/event model (Q41–Q47) is the single most tested area in experienced LS Central technical interview questions. If you cannot explain how to add a custom command and subscribe to its events, revise it before any LS Central developer interview.
Statement Posting and Data Flow Interview Questions
48. Technically, how does a POS transaction become ledger entries?
Raw transactions are gathered by the statement calculation, then the statement posting codeunits create item ledger, G/L, VAT, and tender entries. Therefore, posting is where retail data meets the Business Central ledgers.
49. How do you customize statement posting safely?
Subscribe to the statement calculation/posting events to add or adjust entries (e.g., custom fee, dimension). Avoid modifying LS posting codeunits directly so upgrades remain clean.
50. How are dimensions carried from POS to the G/L?
Dimensions are resolved from store, terminal, item, and setup, then written onto the posted entries during statement posting. You can extend this via events to add custom dimension logic.
51. How do you troubleshoot a statement that posts wrong amounts?
Trace from the transaction lines → statement lines → posted entries, check tender/account mapping and posting groups, and use the debugger on the posting codeunit. Snapshot debugging helps for store-specific issues.
52. What is the role of the item ledger and value entries in retail posting?
They record inventory movement and cost for POS sales/returns. As in BC, run Adjust Cost so COGS is accurate; retail high volume makes cost adjustment timing important.
53. How do you add a custom field to flow from POS to statement posting?
Add the field to the transaction table (extension), populate it at the POS via events, then map it into the posted entry through a posting event subscriber. This is a classic experienced LS Central technical interview question.
54. How do you handle high-volume posting performance?
Post in batches per store/period, ensure proper indexing/keys, use SetLoadFields, avoid per-row heavy logic in subscribers, and schedule posting off-peak. Monitor with telemetry to find bottlenecks.
55. How do returns and voids flow through posting technically?
Returns create negative sale/inventory entries (ideally exact-cost reversing), and voids remove/mark transactions before posting. The statement reflects net amounts so ledgers stay accurate.
Replication and Distributed Architecture Questions
56. How does the Scheduler replication engine work technically?
Jobs define tables, fields, filters, and direction; the engine tracks changes and transfers deltas between head office and stores. Subjobs and dependencies control sequence so related data arrives consistently.
57. How do you add a custom table to replication correctly?
Register it in the appropriate replication job with keys, filters, and direction, and ensure dependency ordering. Test both push (to store) and pull (to HO) so no store is left with missing or stale data.
58. How do you handle replication conflicts?
Design a clear system of record per table (HO owns master data, store owns transactions). Consequently, conflicts are avoided by direction rather than resolved after the fact.
59. What changed with LS Central SaaS regarding replication?
SaaS/centralized models reduce store databases, so much replication is eliminated in favor of a central environment with online terminals. However, offline/hybrid scenarios still use synchronization concepts.
60. How do you design for connectivity loss in a distributed store?
Ensure the terminal can sell offline and buffer transactions, then reconcile on reconnect. Your custom code must not block the sale on a head-office call during outages.
61. How do you monitor replication health?
Check job status, error logs, last-run timestamps, and pending counts. Set up alerts so a stuck job is caught before it starves stores of prices, offers, or items.
62. How do you push a new offer to specific stores technically?
Configure the offer with store targeting and validation, then ensure the offer tables are in the replication scope so only targeted terminals receive and activate it during valid dates.
Integration and API Interview Questions
63. How do you expose LS Central data via APIs?
Use Business Central API pages/queries over LS Central tables (items, prices, inventory, members) to build OData/REST endpoints. As a result, e-commerce and external systems can consume retail data.
64. How do you integrate an e-commerce platform with LS Central?
Through APIs and connectors that sync items, prices, stock, offers, and members. Keep LS Central as the system of record, pushing catalog/inventory out and pulling web orders in for fulfillment.
65. How do you integrate payment/EFT at the POS technically?
Use a certified EFT connector configured in profiles; the POS delegates authorization to the device/provider and records the tender result. This keeps PCI scope with the provider, not your code.
66. How do you call an external REST service from LS Central AL?
Use
HttpClient with request/response types and parse JSON via JsonObject/JsonToken, the same as core AL. Store secrets in Isolated Storage or Key Vault, never in tables.67. How do you connect LS Central to Power Platform?
Via Business Events, virtual tables, and the BC connector in Power Automate/Power Apps. Retail events can trigger flows (e.g., low-stock alerts) without custom polling.
68. How do you handle a custom hardware peripheral at the POS?
Extend the hardware profile and OPOS/printer/peripheral handling, or integrate via a device connector/control add-in. Test on real hardware since behavior varies by device.
69. How do you write automated tests for LS Central customizations?
Use the AL test framework with test codeunits and handlers, plus LS Central test libraries where available, to simulate POS actions and posting. Then run them in CI against a sandbox with LS Central installed.
Upgrade and Tooling Interview Questions
70. How do you approach upgrading an LS Central customization?
Recompile against the new LS Central and Business Central symbols, fix breaking changes (deprecated events/objects), retest POS and posting on a sandbox pilot store, then deploy. Extension-only code makes this far smoother.
71. How do you convert legacy LS Nav C/AL to LS Central AL?
Baseline with txt2al, then refactor toward events and extension objects, replacing base modifications. Map old LS Nav objects to their LS Central equivalents and add tests during the rewrite.
72. How do you run CI/CD for LS Central apps?
Use AL-Go or Azure DevOps pipelines to compile, install LS Central as a dependency, run tests in a container/sandbox, sign, and deploy per environment. Gate merges on passing analyzers and tests.
73. Which code analyzers do you enable for LS Central extensions?
CodeCop, UICop, PerTenantExtensionCop (or AppSourceCop for marketplace). They catch best-practice, UI, and compatibility issues at compile time before they reach a store.
74. How do you manage dependencies between your app, LS Central, and BC?
Declare minimum versions in app.json, follow semantic versioning, and test the exact version combination you will deploy. Mismatched versions cause install failures, so pin responsibly.
75. How do you emit telemetry from an LS Central customization?
Use
Session.LogMessage to send custom signals to Application Insights with dimensions (store, terminal, action). Consequently, you can monitor POS/posting behavior and errors across the chain.🔴 Expert LS Central Technical Interview Questions (6+ Years)
Senior-level LS Central technical interview questions focus on solution architecture, performance at chain scale, upgrade strategy, and integration design. To stand out, you should therefore back every answer with real code and architecture decisions and their measurable impact. Additionally, interviewers test whether you protect upgradeability across many stores and countries.
Architecture and Design Interview Questions
76. How do you architect a custom retail extension for maintainability?
Separate data, POS behavior, posting, and integration into clear modules; use interfaces for pluggable logic; expose your own integration events; and keep POS event subscribers thin. As a result, the app is testable and upgrade-safe.
77. When do you use a table extension vs a related table in retail?
Use a table extension for 1:1 attributes on items/transactions. Use a related table for 1:many or large/rarely-used data, to avoid widening hot, high-volume POS/transaction tables and hurting performance.
78. How do interfaces improve LS Central customizations?
Interfaces let you define pluggable strategies (e.g., custom pricing or loyalty calculation) selected by enum, so other extensions can swap implementations without editing your code. This is key for ISV-grade retail apps.
79. How do you design a custom POS feature to survive LS Central upgrades?
Subscribe only to documented LS Central events, avoid internal objects, keep a facade over your logic, add automated tests, and validate on each new LS Central version in a sandbox before production.
80. How do you manage a large multi-app retail solution (LS + ISVs + custom)?
Define clear dependency layers and version compatibility, coordinate upgrade timing across apps, isolate customizations behind stable contracts, and test the full app stack together on a pilot store.
81. How do you design multi-country retail on one platform?
Use a core template plus per-country layers for tax, fiscalization, e-invoicing, and language, respecting each Business Central localization. Keep customizations parameter-driven so one codebase serves many countries.
82. How do you decide standard vs ISV vs custom for a retail gap?
Rule of thumb: configure first, buy certified ISV second, build last. Weigh upgrade cost, support, and localization. Build custom only for true differentiators, behind stable extension contracts.
Performance and Scalability Interview Questions
83. How do you keep the POS responsive under heavy load?
Keep event subscribers lightweight, avoid synchronous head-office calls during sales, use SetLoadFields and proper keys, and defer heavy work to background jobs. The customer-facing sale must never wait on slow logic.
84. What are common performance anti-patterns in LS Central customizations?
Heavy logic in sale-line events, per-row FlowField calculation, Commit in loops, missing keys, and external calls during the sale. Avoid these to keep POS and posting fast at chain scale.
85. How do you optimize high-volume statement posting?
Batch per store/period, ensure indexing, minimize subscriber overhead, run cost adjustment appropriately, and process off-peak. Use telemetry to locate long-running SQL and lock waits.
86. How do you avoid deadlocks in high-concurrency retail posting?
Access tables in a consistent order, keep transactions short, lock late and briefly, avoid unnecessary Commits, and use
ReadIsolation where suitable. Deadlock questions are common at senior level.87. How do you diagnose a slow POS or posting issue in production?
Use Application Insights telemetry, Performance Profiler, and snapshot debugging to find the hot path. Then optimize the specific event/query rather than guessing.
88. How do you design background processing for retail at scale?
Use Job Queue and StartSession for replenishment calc, posting, and integration, respecting SaaS limits on concurrent background sessions. Ensure idempotency so retries do not double-post.
Integration, DevOps and Advanced Topics
89. How do you design a robust omnichannel integration architecture?
Make LS Central the system of record for items, price, inventory, and members; expose stable APIs; use async/queued sync with retries and idempotency; and reconcile inventory across channels to prevent overselling.
90. How do you handle API rate limits and payload limits in SaaS integrations?
Batch requests, handle 429 throttling with backoff, paginate, and keep payloads within limits. High-volume retail integrations must be designed around these SaaS operational limits.
91. How do you secure secrets and payment/EFT credentials?
Store them in Isolated Storage or Azure Key Vault, never in tables or source. Delegate card authorization to the certified provider so sensitive data stays out of your extension.
92. How do you implement CI/CD for a full retail solution?
Automate build/test/sign/deploy with AL-Go or Azure DevOps, installing LS Central and ISVs as dependencies in the pipeline, running tests on a sandbox pilot store, and promoting signed artifacts through environments.
93. How do you manage LS Central and BC wave upgrades across a live chain?
Test the new versions in a sandbox pilot store, validate POS, posting, offers, replication, and integrations, schedule updates in low-traffic windows, and keep rollback and hypercare ready.
94. How do you instrument a retail solution for observability?
Emit custom telemetry per store/terminal/action to Application Insights, build dashboards/alerts for POS errors, failed postings, and replication lag, so issues are caught before they affect trading.
95. How do you design a custom loyalty or pricing engine as pluggable logic?
Define an interface with an enum-selected implementation, register it via LS Central extensibility, and inject it at the calculation event. Consequently, the engine is swappable and testable without touching LS objects.
Migration, Governance and Judgment Questions
96. What is your strategy to migrate LS Nav customizations to LS Central?
Assess and categorize customizations, decide reimplementation vs conversion, convert C/AL to AL extensions, map LS Nav objects to LS Central equivalents, add tests, and validate POS/posting on a pilot store before rollout.
97. How do you handle data migration for a technical go-live?
Migrate items/variants/barcodes, prices, offers, members/points, and opening stock/balances via configuration packages/APIs, then validate on a test POS and reconcile per store. Automate and repeat the migration for cutover.
98. How do you keep a large customization base evergreen?
Extension-only code, documented-event subscriptions, certified ISVs with committed support, pilot-store regression each wave/version, telemetry alerts, and a standing release-readiness checklist owned by support.
99. How do you govern code quality across a retail delivery team?
Enforce analyzers, PR reviews, naming/affix standards, automated tests, and CI gates. Additionally, maintain shared coding guidelines so multiple developers produce consistent, upgrade-safe LS Central code.
100. How do you evaluate an LS Central ISV/connector technically?
Check certification, update cadence vs LS/BC, dependency footprint, telemetry impact, data portability/exit, and reference deployments at similar scale. Weigh integration cost against building and maintaining.
101. How do you design for a seasonal peak technically?
Load-test the POS and posting paths, pre-replicate seasonal data, freeze risky deployments during peak, scale background processing, and ensure offline resilience so outages never block sales.
102. How do you handle a critical POS bug in production?
Reproduce with snapshot debugging and telemetry, ship a targeted hotfix through the pipeline, validate on a pilot store, deploy in a safe window, and run a root-cause review to prevent recurrence.
103. How do you approach Copilot/AI extensibility in an LS Central context?
Because LS Central sits on Business Central, you can build Copilot capabilities with the PromptDialog page and Azure OpenAI module (consuming Copilot Credits), with human-in-the-loop review, for tasks like demand insight or back-office automation.
104. How do you balance customization vs standard to protect margin and upgradeability?
Quantify each customization's upgrade and maintenance cost versus business value, prefer configuration and certified ISVs, and keep custom code minimal and contract-based. This protects both TCO and future upgrades.
105. What separates a great LS Central developer from a good one?
Judgment: writing upgrade-safe, performant, testable retail code; knowing when to use events vs interfaces; keeping the POS fast; instrumenting with telemetry; and translating retail requirements into minimal, maintainable AL. This is ultimately the most important LS Central technical interview question for senior roles.
❗ Important: At senior level, interviewers want judgment, not syntax recall. For every expert question above, prepare one real code story: the problem, the pattern you chose, and the measurable result (POS speed, fewer posting errors, faster upgrades).
🎯 LS Central Technical Interview Questions: Free Rotating Mock Exam
Ready to test yourself on these LS Central technical interview questions? Attempt this 15-question timed mock exam right here. You get 10 minutes, one question at a time, just like a real screening test. Importantly, the exam picks a random 15 questions from a larger pool and shuffles the options, so every retake shows you a different set. No sign-up is needed, and your attempt is not stored anywhere.
📝 LS Central Technical Mock Exam
Rules: 14 random questions (from a 40-question pool) · 10 minute limit · Pass mark 70% (10/14) · Options shuffled · Retake for a different set.
💡 Tip: Because this exam rotates, retake it several times to cover the whole 40-question pool. Revising one level of LS Central technical interview questions per day and retaking daily is a proven way to prepare.
Final Words on LS Central Technical Interview Questions
These 105 LS Central technical interview questions cover what actually gets asked of retail developers in 2026, from the POS engine to chain-scale architecture. Do not memorize; instead, understand the why behind each answer and back it with code you have written. Interviewers can spot recitation instantly.
To prepare fully, pair this with the functional and core-platform tracks. Read my companion posts, 105 LS Central functional interview questions , 105 Business Central technical interview questions, and 105 Business Central functional interview questions , plus my Business Central licensing guide. For official information, see the LS Central product page from LS Retail.
Which LS Central technical interview question stumped you in a real interview? Share it in the comments and I will add it (with the answer) to this list.
Trademarks & Screenshots: Microsoft, Dynamics 365, Business Central, Dynamics NAV, and related names are trademarks of Microsoft Corporation. LS Central and LS Retail are products of LS Retail. Screenshots are used for educational and illustrative purposes only. Navision Planet is an independent resource and is not affiliated with, endorsed by, or sponsored by Microsoft or LS Retail. All product names, logos, and brands are the property of their respective owners.
