A developer wants to create in Business Manager extension with the cartridge named plugin_vm_extension. Which two steps should the developer take for…

For a Business Manager extension to become functional and visible, two fundamental deployment and configuration steps are required. First, the cartridge containing the extension (pluginbmextension) must be added to the cartridge path specifically for the Business Manager site context. This registration step tells the platform where to find the extension's code and resources. Second, the code version that includes this new cartridge must be activated on the server instance. Activating a code version makes the new code and its features live and executable by the platform.

1. Salesforce B2C Commerce Developer Documentation

Configure a Cartridge Path: "To use a cartridge

you must add it to the cartridge path for your site... Business Manager also has a cartridge path

which you can configure by selecting Administration > Sites > Manage Sites > Business Manager. The Business Manager cartridge path must include the bmapparel cartridge and any cartridge you are using to extend Business Manager." This source confirms that a BM extension cartridge must be added to the specific Business Manager site's cartridge path (Supporting Answer A).

2. Salesforce B2C Commerce Developer Documentation

Select a Code Version: "Before new custom code is available on a B2C Commerce instance

you must upload it and activate the code version that contains it... When you activate a version

it becomes the version that runs on the selected instance." This source confirms that activating the code version is the necessary step to make the new code operational (Supporting Answer D).

3. Salesforce B2C Commerce Developer Documentation

Create a Business Manager Extension: The development lifecycle for a BM extension involves creating the cartridge

adding it to the BM cartridge path

and deploying the code version. The documentation outlines these steps as foundational. For example

in the section on testing

it is implicit that the code must be on an active code version and the cartridge path must be set correctly for the extension to be accessible for testing.