Free practice · No sign-up required
20 questions with answer explanations. Choose an answer below to begin.
In SFRA, which layer is responsible for handling client requests and returning responses?
Understand SFRA architecture and MVC pattern
0/20 answered · Bookmark questions to review later. Focus the practice area to use keys 1–9 and Enter.
Learn by doing
Use official documentation and hands-on labs to work through topics you missed.
Prefer to read at your own pace? Work through each question below, then open its answer to check your reasoning. You can link directly to a question or print this reference.
In SFRA, which layer is responsible for handling client requests and returning responses?
Controller (JavaScript files)
View (ISML templates)
Model (custom objects)
Service (external integrations)
Correct answer
Controller (JavaScript files)
Controllers in SFRA handle incoming HTTP requests, process data, and return responses. Views handle rendering, models represent data, and services communicate with external systems.
Which method is automatically called in an SFRA controller when a GET request is made?
start()
init()
show()
get()
Correct answer
init()
In SFRA controllers, the `init()` method is executed before any action for both GET and POST requests. There is no `show()` or `get()` method by default; actions are defined as methods and mapped via routes.
Where should form field validation rules be defined in SFRA?
In the controller action
In the ISML template
In the form model definition file
In the routes configuration
Correct answer
In the form model definition file
Form validation rules are defined in the form model file (e.g., `forms/default/myForm.json`). The controller may invoke validation, but the rules themselves are part of the form model. Templates only render forms, and routes map URLs.
Which ISML directive is used to include another template file within a template?
Correct answer
The `` directive includes another ISML template at that point. `isimport` and `isrequire` are not valid directives. `isinsert` is used for decorator templates.
What is the base class that a custom SFRA service should extend?
LocalServiceRegistry
BaseService
Service
AbstractService
Correct answer
LocalServiceRegistry
In SFRA, services are created using `LocalServiceRegistry.createService()`, and the service object extends the base service provided by the registry. There is no `BaseService` or `AbstractService` class; the registry handles the base functionality.
What is the purpose of the `@after` decorator in an SFRA controller?
To execute code after a response is sent
To define a hook that runs after the main action
To set a cookie in the response
To validate form data after submission
Correct answer
To define a hook that runs after the main action
The `@after` decorator registers a function to be called after a specific controller action, often used for post-processing. It does not run after the response is sent (that would be a middleware), and it is not for cookie setting or validation.
When extending a base SFRA model, which method should be overridden to include custom attributes in the output?
getData()
serialize()
toJSON()
getAttributes()
Correct answer
toJSON()
The `toJSON()` method is used to serialize model data. Overriding it allows you to include custom attributes. `getData()` and `getAttributes()` are not standard. `serialize()` is not a model method in SFRA.
What is the difference between `InputField` and `SelectField` in SFRA form definitions?
InputField is for numeric values; SelectField is for string values
InputField is used for GET forms; SelectField for POST forms
InputField requires validation; SelectField does not
InputField accepts text input; SelectField provides a dropdown
Correct answer
InputField accepts text input; SelectField provides a dropdown
In SFRA form models, `InputField` renders a text input, while `SelectField` renders a dropdown (select) element. Both support validation, and the form method (GET/POST) does not affect field type.
In a SFRA job, which step type allows you to execute custom JavaScript code?
Script step
Custom step
Pipeline step
Java step
Correct answer
Script step
The 'Script step' in a job allows execution of custom JavaScript code (or other scripts). 'Custom step' is not a job step type in SFRA; pipeline steps are for pipelines, and Java steps are not used.
A developer needs to add a new locale (e.g., fr-CA) that is not in the default list. What is the recommended approach in SFRA?
Add the locale to the site's allowed locales in Business Manager
Create a new cartridge with locale-specific properties
Modify the system's locale configuration file
Override the locale service to include the new locale
Correct answer
Create a new cartridge with locale-specific properties
The recommended approach is to create a new cartridge with locale-specific properties and settings. Adding to allowed locales is needed but not sufficient; the locale must be supported by custom resources. Modifying system files is not recommended, and overriding the locale service is unnecessary.
A custom OCAPI data endpoint returns product data. For security and performance, where should cache expiration be set?
In the service definition JSON file
In the controller action using `response.setExpires()`
In the OCAPI settings in Business Manager
In the API's resource hook
Correct answer
In the OCAPI settings in Business Manager
Cache expiration for OCAPI endpoints is configured in Business Manager under OCAPI settings. Setting it in the controller is not the standard way as OCAPI handles caching at the API level. Service definitions and resource hooks are for other purposes.
How should a developer access site preferences (custom site attributes) in an SFRA controller?
Using `session.custom.sitePreferences`
Using `request.custom.sitePreferences`
Using `app.getSite().preferences`
Using `require('dw/system/Site').getCurrent().getCustomPreferenceValue()`
Correct answer
Using `require('dw/system/Site').getCurrent().getCustomPreferenceValue()`
The correct way is via the `Site` API: `Site.getCurrent().getCustomPreferenceValue()`. Preferences are not available on session or request objects directly. `app.getSite()` is not a valid API in SFRA.
A developer wants to modify the product search results to boost certain products. Which SFRA hook should be used?
ProductSearch.beforeSearch
ProductSearch.modifySearchResult
Search.afterSearch
ProductSearch.afterSearch
Correct answer
ProductSearch.beforeSearch
The `ProductSearch.beforeSearch` hook allows modification of search parameters before the search is executed. `afterSearch` would run after results are returned, not ideal for boosting. `modifySearchResult` is not a standard hook.
When migrating a legacy pipeline to an SFRA controller, what is the recommended approach?
Rewrite the pipeline as a single controller action
Convert pipeline steps into separate controller endpoints
Use the PipelineController to wrap the pipeline
Import the pipeline as a service
Correct answer
Convert pipeline steps into separate controller endpoints
The best practice is to convert each pipeline step into a separate controller endpoint, leveraging SFRA's MVC pattern. Using a single action defeats modularity, and PipelineController is not a standard SFRA component. Importing as a service is not appropriate.
A custom service in SFRA needs to log request/response details for debugging. What is the best way to add logging?
Override the service's `logRequest` method
Use the `afterRequest` hook in the service definition
Add `require('dw/system/Logger').getLogger()` calls in the service callback
Configure logging in the Business Manager service settings
Correct answer
Add `require('dw/system/Logger').getLogger()` calls in the service callback
The `Logger` API is the standard way to add logging in a service callback. There is no `logRequest` method or `afterRequest` hook for services. Business Manager settings are for the server log configuration, not per-service logging.
An order is placed and the developer needs to send order data to an external system. Should an order hook or a job be used?
Use a job because it can handle failures and retries
Use a hook because it executes synchronously and ensures data is sent before response
Use a job to avoid adding latency to the checkout
Use a hook for immediate action, and a job for additional processing if needed
Correct answer
Use a hook for immediate action, and a job for additional processing if needed
Hooks are ideal for immediate, synchronous actions but can add latency. Jobs are better for asynchronous, reliable processing with retries. The best practice often combines both: a hook for immediate action (e.g., logging) and a job for heavier processing (e.g., external sync).
A custom product feed is generated daily and takes 10 minutes. To improve performance, what caching strategy should be applied?
Use Serialized file caching
Use Service Worker cache
Use Server-side caching with a brief TTL
Use Client-side caching with ETags
Correct answer
Use Serialized file caching
For a batch-generated feed, serialized file caching (e.g., storing the feed as file in the application's cache directory) is appropriate because the feed is static between generations. Server-side caching with TTL is useful for dynamic data but less efficient for large files. Client-side caching is not applicable for server-side processing.
A custom form in SFRA submits data via POST. What must be included to prevent CSRF attacks?
The form must use HTTPS
A CSRF token in the form as a hidden field
Set `SameSite` cookie attribute
Validate the request origin header
Correct answer
A CSRF token in the form as a hidden field
CSRF protection in SFRA is implemented by including a CSRF token in the form (typically via `dw.web.CSRFProtection`). HTTPS and SameSite cookies add security but are not sufficient alone. Origin header validation is not standard in SFRA.
A custom model is used across multiple sites in a multi-site environment. How should the model be shared to avoid duplication?
Place the model cartridge in the site path of each site
Create the model as a plugin cartridge and assign it to all sites
Use a shared library cartridge
Duplicate the model code in each site's custom cartridge
Correct answer
Use a shared library cartridge
A shared library cartridge is the recommended approach for sharing code across sites. Placing the cartridge in each site path works but leads to duplication. Plugin cartridges are for functionality, not specifically for sharing models. Duplication is bad practice.
A controller error occurs and the developer wants to display a custom error page. What is the best approach for global error handling in SFRA?
Catch exceptions in each controller action and render a custom template
Override the `handleError` function in the base controller
Set up error handling in the route configuration
Use the global error handler middleware in the server configuration
Correct answer
Use the global error handler middleware in the server configuration
SFRA provides a global error handler middleware that can be configured to catch errors and render custom error pages. Catching in each action is repetitive and not maintainable. Overriding `handleError` is not standard. Route configuration does not handle errors.
Recall the answer before opening each card.
Controller. Controllers process HTTP requests and return responses; views handle rendering, models represent data.
init(). The init() method executes before any action method, regardless of HTTP method.
In the form model definition file (e.g., forms/default/myForm.json). Rules are part of the model, not the controller or template.
The isinclude directive. It inserts the content of another template at the point of inclusion.
LocalServiceRegistry. Services are created via LocalServiceRegistry.createService(), which provides the base service object.
It registers a function to run after the main action. Used for post-processing hooks.
toJSON(). Overriding toJSON() allows custom serialization of model data.
InputField renders a text input; SelectField renders a dropdown (select) element.
Script step. The Script step allows running custom JavaScript or other scripts.
Create a new cartridge with locale-specific properties and place it in the site path.
In Business Manager under OCAPI settings. Not in controllers or service definitions.
Use require('dw/system/Site').getCurrent().getCustomPreferenceValue('name').
ProductSearch.beforeSearch. It allows boosting or filtering before the search runs.
Convert each pipeline step into a separate controller endpoint, leveraging MVC modularity.
Add require('dw/system/Logger').getLogger() calls inside the service callback.
Use a hook for immediate action, and a job for additional async processing if needed.
Serialized file caching. Store the feed as a file in the cache directory between generations.
A CSRF token as a hidden field, generated by dw.web.CSRFProtection.
Use a shared library cartridge. Place the cartridge in each site's cartridge path.
Use the global error handler middleware configured in the server.js file.
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Connect the concepts
Open a branch to connect a topic with its practice questions and explanations. Use the map to choose your next review topic.
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
Questions 1–3 and 6–7 focus on SFRA’s MVC layers and controller mechanics. You must understand that controllers handle requests and return responses, the init() method runs before actions, decorators like @after run after the main action, and model’s toJSON() is overridden for custom serialization. Form validation rules live in form model files, not controllers or templates. These questions test your grasp of separation of concerns and the framework’s lifecycle.
Questions 4–5 and 9–10 and 13 cover service creation (extending LocalServiceRegistry), ISML template inclusion (isinclude directive), job step types (Script step runs custom JavaScript), localization (create new cartridge for new locale), and search customization (ProductSearch.beforeSearch hook). These items test your ability to integrate external systems, automate tasks, and extend built-in functionality through hooks and services.
Questions 11–12 and 17–18 address OCAPI caching (set in Business Manager), site preferences (Site.getCurrent().getCustomPreferenceValue()), caching strategies (serialized file caching for batch feeds), and CSRF protection (include CSRF token as hidden field). You need to know where configurations live, how to access custom attributes, and which security measures are standard in SFRA.
Questions 14, 19, and 20 cover pipeline migration (convert steps to separate controller endpoints), multi-site code sharing (use a shared library cartridge), and global error handling (configure global error handler middleware). These questions test your ability to modernize legacy code, avoid duplication across sites, and implement consistent error responses.
Study workflow
When a client request arrives, determine if it should be handled by a controller or a custom service. Controllers handle user-facing interactions and return views or JSON. Services handle external system communication or complex business logic. Always start by mapping the request to the correct SFRA layer.
Create a form model JSON file under forms/default/ and define fields with validation rules (required, minLength, etc.). In the controller action, use form.get() to retrieve the model and form.isValid() to check. Avoid putting validation logic in templates; keep it in the model definition.
For batch-generated content like product feeds, use serialized file caching by writing the output to a cache file and serving it until the next generation. For dynamic data, consider server-side caching with a TTL. Monitor cache hit rates and adjust TTLs to balance freshness and performance.
In the controller that renders the form, generate a CSRF token using dw.web.CSRFProtection and pass it to the template. In the template, include it as a hidden input field named csrf_token. On form submission, verify the token in the controller before processing data.
In the server configuration file (server.js), add a global error handler middleware using app.use with a callback that catches errors and renders a custom error template. Log the error with Logger for debugging. This centralizes error responses and avoids repetitive try-catch blocks.
FAQ
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
The init() method runs automatically before any action, regardless of HTTP method. It is used for common setup like session validation or setting up pre-requisites. It is not an action itself but a lifecycle hook that executes before action methods.
Use require('dw/system/Logger').getLogger() inside the service callback to log details. Call Logger methods for request/response data. There is no built-in logRequest method; you must add logging explicitly in the callback function.
Create a shared library cartridge that contains common models, services, and scripts. Assign that cartridge to the site's cartridge path. This avoids code duplication and simplifies maintenance. Do not copy code into each site's cartridges.
No. Best practice is to convert each pipeline step into a separate controller endpoint. This leverages SFRA's modular MVC pattern, making the code easier to maintain and test. A single action would defeat the purpose of migration.
Use the ProductSearch.beforeSearch hook. In the hook implementation, modify the search parameters (like boosting criteria) before the search is executed. The afterSearch hook runs after results and is not suitable for boosting.
Browse another free bank or use the study strategy guide to turn your misses into spaced review.
