The Architect has been presented with a requirement from the business to implement a new LINK cartridge. The current site is built on the Storefront Reference Architecture, and the LINK cartridge is certified for Pipelines and Controllers. On review, the Architect notes that the Jobs are all created in Pipelines. How should the Architect implement that cartridge to make sure the required jobs runs property?
A. The Job Pipelines must be updated to use SiteGenesis Controllers.
B. The job Pipelines must be removed and recreated with scripts.
C. The job Pipelines must be updated to use SFRA Controllers.
D. The job Pipelines must be updated to work as custom job steps.
D. The job Pipelines must be updated to work as custom job steps.
Explanation:
LINK Cartridge Compatibility:
Since the cartridge is certified for Pipelines and Controllers, it should work within the existing SFRA (Storefront Reference Architecture) framework.
However, Jobs in SFRA are typically implemented as custom job steps rather than standalone Pipelines.
Why Not the Other Options?
A (SiteGenesis Controllers):
SFRA does not use SiteGenesis controllers—this would break compatibility.
B (Remove Pipelines and recreate with scripts):
Jobs in SFRA are not script-based; they are managed via Job Steps in Business Manager.
C (Update to SFRA Controllers):
Jobs do not run via storefront controllers—they are backend processes managed by Job Steps.
Correct Approach (D):
The LINK cartridge’s job logic should be adapted into custom job steps (e.g., dw.job.JobStep implementations).
This ensures:
1. Compatibility with SFRA’s job execution framework.
2. Proper scheduling & logging via Business Manager.
3. No dependency on storefront controllers (since jobs run in the background).
Key Takeaway:
Since the business requires a LINK cartridge integration and the site uses SFRA, the best practice is to convert the job Pipelines into custom job steps (option D). This ensures seamless execution without breaking existing architecture.