I85PREP
⌘ K
SuiteCommerce Developer study materials
SuiteCommerce Developer study resources

SuiteCommerce Developer practice questions

One question at a time. Build your SuiteCommerce Developer understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1SuiteCommerce Platform and Architecture

In a SuiteCommerce Advanced implementation, which layer is responsible for rendering the storefront views that the shopper interacts with in the browser?

  1. The NetSuite ERP server-side transaction engine
  2. The CSV import scheduler
  3. The SuiteScript governance monitor
  4. The Commerce web store application built on the frontend framework Correct answer.

Explanation

SuiteCommerce Advanced splits responsibilities: the Commerce web store application (the frontend layer, historically Backbone/Marionette-based) renders the storefront views the shopper sees, while NetSuite ERP handles records and transactions. The ERP engine does not render browser views.

Question 2SuiteCommerce Platform and Architecture

What is the primary purpose of the Commerce API (formerly called the shopping API) in a SuiteCommerce architecture?

  1. To expose storefront data such as items, cart, and checkout to the frontend application Correct answer.
  2. To schedule SuiteScript map/reduce jobs
  3. To compile SASS files into CSS during deployment
  4. To manage NetSuite role permissions and passwords

Explanation

The Commerce API provides the endpoints the frontend uses to read catalog data and manipulate the cart and checkout flow without direct record access. Compilation, scheduling, and permission management are handled by other tools entirely.

Question 3SuiteCommerce Platform and Architecture

A developer needs to add custom business logic that runs on the server when an order is placed from the web store. Where should that logic live?

  1. In a client-side JavaScript file loaded by the browser
  2. In a SuiteScript file referenced by the extension's service controller or a backend model Correct answer.
  3. In the sitemap configuration file
  4. In a CSS override in the theme

Explanation

Server-side logic in SuiteCommerce Advanced runs as SuiteScript invoked through the extension's service controllers or backend models. Client-side files, CSS, and sitemap configuration cannot execute privileged server logic.

Question 4SuiteCommerce Platform and Architecture

Which statement best describes the role of an extension in SuiteCommerce Advanced customization?

  1. It bundles custom modules, templates, and assets that override or extend core functionality without editing core source files Correct answer.
  2. It is a NetSuite bundle type that installs only SuiteScript plug-ins
  3. It replaces the entire NetSuite ERP database schema
  4. It is a backup snapshot of the site theme

Explanation

Extensions are the supported customization mechanism: they contain modules and templates that layer over core code so upgrades remain feasible. They do not alter the ERP schema, are not limited to plug-ins, and are not backups.

Question 5SuiteCommerce Platform and Architecture

A developer wants the storefront to display a promotional banner only when a shopper's cart subtotal exceeds a threshold. Which approach fits the SuiteCommerce architecture?

  1. Create a NetSuite workflow that edits the HTML of the page
  2. Add the banner to the robots.txt file
  3. Add a custom module that reads cart data via the Commerce API and conditionally renders the banner template Correct answer.
  4. Hard-code the banner into the core header template and rebuild

Explanation

Conditional, data-driven rendering belongs in a custom frontend module that reads cart state through the Commerce API and decides whether to render the template. Editing core templates is upgrade-hostile, workflows cannot rewrite page HTML, and robots.txt affects crawlers only.

Question 6SuiteCommerce Platform and Architecture

What does the SuiteCommerce configuration record (commonly called the shopping configuration) primarily control?

  1. The employee payroll schedule
  2. Storefront behaviors and settings such as catalog, checkout, and domain options consumed by the application Correct answer.
  3. The NetSuite chart of accounts structure
  4. The SuiteScript deployment status of all scripts

Explanation

The configuration record stores settings the commerce application reads at runtime, such as catalog and checkout behavior and domain information. Accounting structure, payroll, and script deployment status are managed elsewhere.

Question 7SuiteCommerce Platform and Architecture

In the SuiteCommerce Advanced development workflow, what is the purpose of the local development server (the gulp-based dev environment)?

  1. To store customer payment tokens
  2. To run NetSuite scheduled scripts
  3. To host the production storefront for shoppers
  4. To serve the application locally with live reload so developers can iterate on modules and templates before deployment Correct answer.

Explanation

The local dev server lets developers run and preview the application on their machine with live reload, shortening iteration cycles. It is not a production host, does not run scheduled SuiteScript, and never stores payment tokens.

Question 8SuiteCommerce Platform and Architecture

Which file type in a SuiteCommerce Advanced theme is compiled into the CSS that the storefront serves?

  1. JSON configuration records
  2. SuiteScript 2.x modules
  3. SCSS source files Correct answer.
  4. XML sitemap files

Explanation

Theme styling is authored in SCSS, which the build compiles into the CSS delivered to browsers. SuiteScript, JSON configuration, and XML sitemaps serve unrelated purposes.

Question 9SuiteCommerce Platform and Architecture

A team must ensure that customizations survive a future SuiteCommerce Advanced version upgrade. Which practice best supports that goal?

  1. Implement changes in extensions that override core modules rather than editing core source files Correct answer.
  2. Copy the entire core source tree into a separate folder and edit it there
  3. Disable all core modules and rewrite the storefront from scratch
  4. Store custom code only in the production file system

Explanation

Keeping customizations in extensions that override core modules isolates them from core code, so upgrades can replace core files without losing work. Forking or rewriting core code, or editing only production files, makes upgrades painful and risky.

Question 10SuiteCommerce Platform and Architecture

What is the role of a service controller (a SuiteScript SSP application file) in SuiteCommerce Advanced?

  1. It manages DNS records for the store domain
  2. It defines the visual layout of product list pages
  3. It stores the shopper's saved credit cards
  4. It handles server-side requests routed to a backend service and returns responses to the frontend Correct answer.

Explanation

Service controllers are the server-side entry points that receive routed requests, run SuiteScript logic, and return data to the frontend. Layout, payment storage, and DNS are handled by templates, the payment provider, and domain configuration respectively.

Question 11SuiteCommerce Platform and Architecture

How does the SuiteCommerce frontend typically obtain product detail data for a product detail page?

  1. By calling a Commerce API endpoint that returns the item's data as JSON Correct answer.
  2. By querying the NetSuite database directly from the browser
  3. By reading a static HTML file generated at build time for each item
  4. By parsing the sitemap XML in the browser

Explanation

The frontend requests item data from a Commerce API endpoint that returns JSON, which the view renders. Browsers cannot query the NetSuite database directly, static per-item HTML is not how the catalog is served, and sitemaps contain URLs rather than product attributes.

Question 12SuiteCommerce Platform and Architecture

Which component is responsible for routing a storefront URL such as /product/123 to the correct view and data request?

  1. The frontend router combined with the application's module configuration Correct answer.
  2. The payment gateway adapter
  3. The NetSuite tax engine
  4. The SuiteScript governance queue

Explanation

Client-side routing maps URLs to views, and module configuration determines which modules and templates handle them. Tax, governance, and payment components play no part in URL routing.

Question 13SuiteCommerce Platform and Architecture

A developer must expose a new custom field from item records to the storefront product page. Which combination of steps is required?

  1. Ensure the field is available to the commerce API response and render it in the product detail template Correct answer.
  2. Change the store's DNS CNAME record
  3. Create a new NetSuite subsidiary and assign the item to it
  4. Add the field to the robots.txt file

Explanation

The field must be included in the data the Commerce API returns for the item, and the template must render it. Subsidiaries, robots.txt, and DNS settings do not affect field exposure on product pages.

Question 14SuiteCommerce Platform and Architecture

Which statement accurately distinguishes SuiteCommerce Standard from SuiteCommerce Advanced?

  1. Standard runs without NetSuite while Advanced requires NetSuite
  2. Standard requires SuiteScript extensions while Advanced forbids them
  3. Standard is only for B2B while Advanced is only for B2C
  4. Standard offers a hosted storefront with limited customization, while Advanced provides a full extensible codebase for deep customization Correct answer.

Explanation

SuiteCommerce Standard is a hosted offering with constrained customization options, whereas SuiteCommerce Advanced exposes the full application codebase for extension-based customization. Both run on NetSuite, and neither is restricted by business model in the way the other options claim.

Question 15SuiteCommerce Platform and Architecture

What is the purpose of the manifest file in a SuiteCommerce Advanced extension?

  1. It defines the NetSuite account's fiscal calendar
  2. It declares the extension's metadata, dependencies, and assets so the build and deployment process can assemble it Correct answer.
  3. It stores the shopper's session cookie
  4. It contains the compiled CSS for the theme

Explanation

The manifest describes the extension to the toolchain: what it contains, what it depends on, and which assets to include during build and deployment. It is not a session store, a fiscal calendar, or compiled CSS.

Question 16SuiteCommerce Platform and Architecture

A shopper adds an item to the cart on the storefront. Which sequence best reflects the SuiteCommerce architecture?

  1. The theme's SCSS recompiles to update the cart
  2. The browser writes directly to a NetSuite transaction record
  3. The frontend calls a Commerce API cart endpoint, which invokes server-side logic that updates the cart and returns the new state Correct answer.
  4. The sitemap regenerates to reflect the cart contents

Explanation

Cart changes flow through Commerce API endpoints that execute server-side logic and return updated cart state to the frontend. Browsers cannot write records directly, and styling or sitemap processes are unrelated to cart operations.

Question 17SuiteCommerce Platform and Architecture

Why does SuiteCommerce Advanced separate frontend templates from backend SuiteScript logic?

  1. To avoid using NetSuite records entirely
  2. To prevent the storefront from using JSON
  3. To let presentation change independently of business logic and to keep privileged operations on the server Correct answer.
  4. To eliminate the need for any testing

Explanation

Separating templates from server logic supports independent evolution of presentation and business rules while keeping privileged operations server-side. It does not ban JSON, remove testing needs, or eliminate record usage.

Question 18SuiteCommerce Platform and Architecture

Which mechanism allows a SuiteCommerce extension to replace the behavior of a core JavaScript module without modifying the core file?

  1. Renaming the core file in the deployment
  2. Deleting the core module from the source tree
  3. Declaring an override of the core module's path in the extension's configuration Correct answer.
  4. Adding the core module name to robots.txt

Explanation

Extensions declare overrides that map a core module path to a custom implementation, so the build resolves the custom version without touching core files. Renaming or deleting core files breaks the build, and robots.txt has no effect on module resolution.

Question 19SuiteCommerce Platform and Architecture

A developer observes that a custom SuiteScript service controller exceeds governance limits during checkout. Which approach is most appropriate?

  1. Move the logic to a client-side script to bypass governance
  2. Reduce redundant record searches and cache or batch data access within the controller Correct answer.
  3. Increase the account's SuiteScript governance limit in setup
  4. Disable the checkout flow entirely

Explanation

Governance usage is reduced by eliminating redundant searches and batching or caching lookups. Moving privileged logic to the client is insecure and unsupported, governance limits are not user-adjustable, and disabling checkout is not a solution.

Question 20SuiteCommerce Platform and Architecture

Which statement about the relationship between the SuiteCommerce application and NetSuite records is correct?

  1. The application writes directly to NetSuite tables from client code
  2. The application stores all business data in browser local storage
  3. The application bypasses NetSuite and uses a separate database
  4. The application reads and writes business data through server-side SuiteScript that operates on NetSuite records Correct answer.

Explanation

Business data lives in NetSuite records, and the commerce application accesses it through server-side SuiteScript layers. Browser storage, a separate database, and direct client writes are not how the architecture persists business data.

Question 21SuiteCommerce Platform and Architecture

What is the primary function of the SuiteCommerce theme in the application architecture?

  1. It defines the visual styling and layout assets applied to storefront templates Correct answer.
  2. It executes order fulfillment logic
  3. It stores customer authentication credentials
  4. It schedules nightly data imports

Explanation

The theme supplies styling and layout assets that shape the storefront's appearance. Fulfillment logic, credential storage, and import scheduling are handled by other parts of the platform.

Question 22SuiteCommerce Platform and Architecture

A developer wants search engine crawlers to receive a fully rendered product page even though the storefront renders views in the browser. Which SuiteCommerce capability addresses this?

  1. Disabling JavaScript in the theme
  2. A larger browser local storage quota
  3. A second DNS A record for crawlers
  4. A server-side rendering or prerender path that returns rendered HTML to crawlers Correct answer.

Explanation

Because the storefront is largely client-rendered, SuiteCommerce provides a server-side rendering/prerender path so crawlers receive rendered HTML. Storage quotas, extra DNS records, and disabling JavaScript do not solve crawler rendering.

Question 23SuiteCommerce Platform and Architecture

Which item best describes a backend model in SuiteCommerce Advanced?

  1. A browser bookmarklet for administrators
  2. A server-side module that encapsulates data access and business logic used by service controllers Correct answer.
  3. A NetSuite saved search used only in reports
  4. A CSS class applied to product tiles

Explanation

Backend models are server-side modules that centralize data access and business rules for controllers to call. CSS classes, bookmarklets, and reporting saved searches do not serve that architectural role.

Question 24SuiteCommerce Platform and Architecture

A business wants B2B features such as company-specific pricing and purchase-order checkout in SuiteCommerce. What should the architect confirm?

  1. That checkout bypasses NetSuite order records
  2. That the implementation uses the B2B commerce features and configuration supported by the chosen edition Correct answer.
  3. That all pricing is hard-coded in templates
  4. That the storefront disables user accounts entirely

Explanation

B2B capabilities like company accounts, custom pricing, and purchase orders depend on the B2B feature set and configuration available in the chosen edition. Disabling accounts, hard-coding prices, and bypassing order records would defeat the requirement.

Question 25SuiteCommerce Platform and Architecture

Which practice is recommended when adding a new JavaScript dependency to a SuiteCommerce Advanced extension?

  1. Declare it in the extension's dependency configuration so the build bundles it correctly Correct answer.
  2. Add it to the robots.txt allow list
  3. Paste the library source into every template
  4. Load it from an unverified third-party URL at runtime

Explanation

Dependencies should be declared in the extension configuration so the build resolves and bundles them predictably. Pasting into templates, loading unverified remote code, and editing robots.txt are unsafe or ineffective.

Question 26SuiteCommerce Platform and Architecture

In the SuiteCommerce architecture, what is the primary role of the Commerce API (the commerce web services layer)?

  1. It compiles Sass theme files into the deployed stylesheet
  2. It schedules SuiteScript map/reduce jobs for order fulfillment
  3. It stores uploaded product images in the NetSuite file cabinet
  4. It exposes endpoints that the storefront JavaScript calls to read catalog, cart, and checkout data Correct answer.

Explanation

The Commerce API is the server-side service layer that the frontend JavaScript consumes to retrieve shopping data and perform cart and checkout operations. It abstracts NetSuite records and business logic behind HTTP endpoints. Image storage and Sass compilation are handled by other components.

Question 27SuiteCommerce Platform and Architecture

A developer needs to know which environment variables and settings a SuiteCommerce Advanced site uses at build time. Which file is the central place these are defined for the local project?

  1. The local.conf file generated from the distribution configuration Correct answer.
  2. The ns.package.json file inside each extension
  3. The distro.json file that lists bundled modules
  4. The deploy.json file produced after compilation

Explanation

The local.conf (derived from the distribution's configuration file) holds the environment-specific settings such as application URLs, tokens, and touchpoint information used during local development. It is generated by the setup task rather than hand-authored from scratch.

Question 28SuiteCommerce Platform and Architecture

Which statement best describes how SuiteCommerce Advanced handles search engine visibility for a storefront that renders content client-side?

  1. It relies on the browser to render pages and assumes crawlers execute all JavaScript identically
  2. It disables JavaScript for known crawler user agents at the CDN
  3. It requires the merchant to submit a static sitemap of pre-rendered pages
  4. It provides a server-side rendering path so crawlers receive fully formed HTML for indexable pages Correct answer.

Explanation

SuiteCommerce Advanced includes server-side rendering so that search engine crawlers receive complete HTML for SEO-relevant pages, even though shoppers get a client-side application. This avoids depending on crawler JavaScript execution.

Question 29SuiteCommerce Platform and Architecture

What is the function of the SSP application (the SuiteScript-based server application) in SuiteCommerce Advanced?

  1. It defines the URL paths that map storefront requests to backend service controllers Correct answer.
  2. It generates the Sass variables used by the theme
  3. It manages the NetSuite role permissions for storefront shoppers
  4. It hosts the compiled frontend JavaScript bundle for the browser

Explanation

The SSP application registers the service controllers and the URL patterns that route storefront requests to backend SuiteScript logic. It is the server-side entry point for the commerce services.

Question 30SuiteCommerce Platform and Architecture

A developer must add a new endpoint that returns custom loyalty points for the logged-in shopper. Where should the new service controller logic be implemented?

  1. In the frontend view template's HTML markup
  2. In a SuiteScript service file registered with the SSP application Correct answer.
  3. In the theme's Sass partials so it compiles into the stylesheet
  4. In the distro.json module list only

Explanation

New server endpoints are implemented as SuiteScript service controllers registered with the SSP application so the frontend can call them. The controller then queries the relevant records and returns JSON.

Question 31SuiteCommerce Platform and Architecture

Which description best captures the role of a frontend model in SuiteCommerce Advanced?

  1. It renders the HTML markup for a page section
  2. It compiles the JavaScript bundle during deployment
  3. It stores the shopper's session cookie on the server
  4. It manages data retrieval and state for a view, calling backend services as needed Correct answer.

Explanation

A frontend model encapsulates the data and state a view needs, fetching from backend services and exposing methods the view uses. It separates data concerns from markup rendering.

Question 32SuiteCommerce Platform and Architecture

In SuiteCommerce Advanced, how is a view typically connected to its template?

  1. The template directly instantiates the model and calls backend endpoints
  2. The view declares a template and the framework renders it with the view's context data Correct answer.
  3. The theme stylesheet injects the template markup at runtime
  4. The backend controller renders the template and returns finished HTML for every request

Explanation

Views reference a template (often via a template property or compiled template module) and the framework renders that template using the view's data context. This keeps rendering declarative and tied to view state.

Question 33SuiteCommerce Platform and Architecture

A developer wants to override a single method of a core frontend module in an extension without editing core files. Which approach fits the SuiteCommerce Advanced extension model?

  1. Edit the compiled bundle in the deployment folder after each build
  2. Add a CSS rule that hides the original module's output
  3. Copy the entire core module into the extension and delete the original
  4. Use the extension's JavaScript entry point to extend or patch the module's prototype Correct answer.

Explanation

Extensions can extend core modules by loading after them and overriding specific methods on the module's prototype or object, preserving upgrade safety. Editing compiled output or duplicating whole modules creates maintenance problems.

Question 34SuiteCommerce Platform and Architecture

What does the ns.package.json file inside a SuiteCommerce Advanced extension primarily declare?

  1. The NetSuite account credentials used for deployment
  2. The extension's asset paths, dependencies, and how its files map into the build Correct answer.
  3. The SuiteScript governance limits for service controllers
  4. The shopper-facing URL routes for the storefront

Explanation

ns.package.json describes an extension's contents, including asset mappings and dependencies, so the build toolchain knows how to incorporate it. It does not hold credentials, routes, or governance settings.

Question 35SuiteCommerce Platform and Architecture

Which component in SuiteCommerce Advanced is responsible for defining the client-side URL routes that map browser paths to views?

  1. The NetSuite record type definition
  2. The frontend router configuration Correct answer.
  3. The Sass theme variables
  4. The SuiteScript service controller

Explanation

Client-side routing is configured in the frontend application's router, which maps URL patterns to the appropriate views and their data loading. Backend controllers handle data endpoints rather than browser routes.

Question 36SuiteCommerce Platform and Architecture

A merchant wants the storefront to display a custom attribute stored on item records on the product detail page. Which change is required on the backend data side?

  1. Expose the field through the product data returned by the commerce service layer Correct answer.
  2. Add the field to the theme's Sass variables
  3. Register the field in the client-side router configuration
  4. Add the field to the distro.json module list

Explanation

For a custom item field to reach the storefront, the backend service that returns product data must include that field in its response. The frontend can then render it in the template.

Question 37SuiteCommerce Platform and Architecture

Which statement correctly describes the relationship between a SuiteCommerce touchpoint and a NetSuite domain?

  1. A touchpoint is a SuiteScript file that renders product pages
  2. A touchpoint is a compiled JavaScript bundle served to the browser
  3. A touchpoint is a NetSuite role that controls shopper permissions
  4. A touchpoint binds a storefront configuration to a domain so requests resolve to the correct site Correct answer.

Explanation

A touchpoint associates a domain with a specific SuiteCommerce configuration, determining which storefront settings and content apply to requests arriving at that domain. This enables multiple sites or domains within one account.

Question 38SuiteCommerce Platform and Architecture

A developer is troubleshooting why a storefront page loads data from the wrong site configuration when accessed through a second domain. Which area should be examined first?

  1. The touchpoint and domain mapping for the storefront configuration Correct answer.
  2. The SuiteScript governance usage of the checkout controller
  3. The Sass compilation order in the theme
  4. The file cabinet folder permissions for images

Explanation

When requests resolve to the wrong site settings, the touchpoint-to-domain mapping is the likely cause, since it determines which configuration applies per domain. Styling, governance, and file permissions do not control site resolution.

Question 39SuiteCommerce Platform and Architecture

What is the purpose of the distribution configuration (distro.json) in a SuiteCommerce Advanced project?

  1. It lists the NetSuite employees authorized to deploy
  2. It declares which modules and extensions are included in the application build Correct answer.
  3. It stores the production database connection string
  4. It defines the CSS variables for the theme

Explanation

distro.json specifies the modules and extensions that make up the application, guiding the build toolchain on what to include and in what order. It is a build manifest, not a credential or styling store.

Question 40SuiteCommerce Platform and Architecture

Why does SuiteCommerce Advanced compile frontend assets (JavaScript, templates, Sass) before deployment rather than serving raw source files?

  1. To satisfy NetSuite's requirement that all files be stored as records
  2. To prevent developers from editing source files
  3. To produce optimized bundles and templates the browser can load efficiently Correct answer.
  4. To eliminate the need for a backend service layer

Explanation

Compilation bundles modules, precompiles templates, and processes Sass so the browser receives efficient, dependency-resolved assets. It is a performance and packaging step, not a restriction on editing source.

Question 41SuiteCommerce Platform and Architecture

Which item best describes how a SuiteCommerce extension declares that it depends on another module?

  1. By hard-coding a script tag in the page HTML
  2. By adding the dependency to the extension's package descriptor so the build resolves it Correct answer.
  3. By adding a CSS import to the theme
  4. By copying the dependency's source into the extension folder

Explanation

Dependencies are declared in the extension's package descriptor (ns.package.json), allowing the build toolchain to resolve and order modules correctly. Hard-coding tags or copying source bypasses dependency management.

Question 42SuiteCommerce Platform and Architecture

A developer observes that a custom service controller performs many record lookups per request and slows checkout. Which architectural change best addresses this?

  1. Cache or consolidate the data retrieval in the backend service to reduce repeated calls Correct answer.
  2. Add more CSS rules to the checkout page
  3. Increase the number of client-side route definitions
  4. Move the lookups into the frontend view template

Explanation

Reducing repeated backend record lookups through caching or consolidated queries addresses the performance bottleneck at its source. Frontend or styling changes do not reduce server-side data access cost.

Question 43SuiteCommerce Platform and Architecture

Which statement accurately describes the role of the NetSuite record model in the SuiteCommerce architecture?

  1. NetSuite records replace the need for a service layer
  2. NetSuite records are generated at runtime from the compiled frontend bundle
  3. NetSuite records are the system of record that commerce services read and write through SuiteScript Correct answer.
  4. NetSuite records are only used for styling the storefront

Explanation

Commerce services access NetSuite records (items, customers, orders) through SuiteScript, making records the authoritative data store behind the storefront. The frontend bundle does not generate records, and records do not eliminate the service layer.

Question 44SuiteCommerce Platform and Architecture

In a SuiteCommerce Advanced extension, where does the JavaScript entry point that runs custom initialization logic typically belong?

  1. In the theme's main Sass file
  2. In the SSP application's URL routing table
  3. In the NetSuite item record's custom field
  4. In the extension's JavaScript source configured as its entry module Correct answer.

Explanation

An extension's JavaScript entry module is where initialization and module patching logic is placed, and it is wired into the build through the extension's configuration. Sass, record fields, and routing tables serve different purposes.

Question 45SuiteCommerce Platform and Architecture

What is the primary purpose of the SuiteCommerce configuration record referenced by a storefront?

  1. It stores the compiled JavaScript bundle for deployment
  2. It defines the NetSuite account's chart of accounts
  3. It manages employee authentication for the backend
  4. It holds storefront settings such as enabled features, catalog display, and checkout options Correct answer.

Explanation

The SuiteCommerce configuration record centralizes storefront behavior settings, including feature toggles, catalog presentation, and checkout options, that the application reads at runtime. It is unrelated to accounting setup or asset storage.

Question 46SuiteCommerce Platform and Architecture

A team wants two different branded storefronts served from one NetSuite account with separate catalogs and settings. Which architecture feature supports this?

  1. A single configuration with conditional CSS per brand
  2. Using separate SuiteScript governance limits per brand
  3. Multiple SuiteCommerce configurations bound to different touchpoints and domains Correct answer.
  4. Duplicating the NetSuite account for each brand

Explanation

Multiple SuiteCommerce configurations, each bound to its own touchpoint and domain, allow distinct storefronts within one account. Conditional CSS or separate accounts are not the intended mechanism.

Question 47SuiteCommerce Platform and Architecture

Which statement best explains why SuiteCommerce Advanced separates templates from SuiteScript service logic?

  1. Templates run on the server and services run in the browser
  2. Separation is required because SuiteScript cannot return JSON
  3. Templates handle presentation while services handle data and business rules, enabling independent change Correct answer.
  4. Templates must be written in SuiteScript to render

Explanation

Separating presentation templates from backend services lets each layer evolve independently and keeps business rules out of markup. Templates render data; services retrieve and validate it.

Question 48SuiteCommerce Platform and Architecture

A developer must ensure a custom extension survives a future SuiteCommerce Advanced version upgrade. Which practice is most aligned with the platform's extension model?

  1. Disable the build pipeline to preserve custom files
  2. Override behavior through extension entry points rather than editing core modules Correct answer.
  3. Hard-code version-specific paths in the theme
  4. Modify core source files directly to guarantee behavior

Explanation

Keeping customizations in extensions that patch or extend core modules at runtime preserves upgrade compatibility, since core files can be replaced during upgrades. Direct core edits and hard-coded paths break on upgrade.

Question 49SuiteCommerce Platform and Architecture

Which component serves compiled static assets such as JavaScript bundles and images to the shopper's browser?

  1. The SSP application service controllers
  2. The SuiteCommerce configuration record
  3. The static asset hosting layer configured for the site Correct answer.
  4. The NetSuite scheduled script queue

Explanation

Compiled bundles and media are delivered as static assets through the hosting layer configured for the site, separate from dynamic service requests. Service controllers handle data, not static file delivery.

Question 50SuiteCommerce Platform and Architecture

A developer needs to confirm which backend service endpoint a storefront view calls to retrieve cart contents. Which artifact should be inspected?

  1. The NetSuite item record's display name field
  2. The deploy.json file listing deployment targets
  3. The theme's Sass map of color variables
  4. The frontend model or service module associated with the cart view Correct answer.

Explanation

The frontend model or service module tied to the cart view defines which backend endpoint is called and how the response is used. Sass, record fields, and deploy artifacts do not describe endpoint calls.