An Adobe Commerce developer creates a new website using a data patch.

The correct answer is Option A. This approach ensures that the configuration is set using the CLI with the --lock-config flag, which prevents the setting from being overridden by configuration changes in other environments.

Understanding the Configuration Requirement:

The developer needs to ensure consistent configuration across all environments without visibility into them. This calls for a method that can enforce configuration at a system level.

Setting catalog/price/scope to 1 configures pricing to be scoped at the website level, as required.

Using the CLI with --lock-config:

The command bin/magento config:set catalog/price/scope 1 --lock-config not only sets the configuration but also locks it. This lock ensures that the setting will not be inadvertently changed by system configuration settings in other environments.

By locking the configuration, the value becomes consistent across all environments and is stored in app/etc/config.php, which can be committed to version control and deployed across environments.

Why Other Options Are Incorrect:

Option B: While this option sets the configuration, it lacks the --lock-config flag. Without locking, the setting can still be overridden or altered in other environments, which does not guarantee consistency.

Option C: Modifying the config.xml for setting catalog/price/scope could be an approach, but this method is not environment-proof. It also doesn’t provide the same guarantee as using --lock-config, which explicitly prevents environment-specific changes from altering the configuration.

References:

Environment Configuration in Adobe Commerce - Details on managing environment-specific configurations and using the --lock-config flag.

Using the Magento CLI for Configuration Management - Documentation on setting and locking configuration values via CLI.

Option A is the best solution to ensure that the configuration is consistently deployed across all environments while protecting it from changes by leveraging the --lock-config option.