A Project Has a Magento Cron Job Implemented to Export

Multiple Choice

A project has a Magento cron job implemented to export new order data to a file. This process can also be triggered by a custom bin/magento command. The functionality uses a lock file in var/locks to prevent concurrent execution. There are instances when the process gets locked after Production deployments and order data is not exported. How do you prevent this from happening?

A) Use the VAR_LOCKS_CLEAR variable available for the post_deploy stage in the .magento.env.yaml file Use the VAR_LOCKS_CLEAR variable available for the post_deploy stage in the .magento.env.yaml file
B) Write a custom post_deploy hook to delete orphan lock files and include it in the .magento.app.yaml file Write a custom hook to delete orphan lock files and include it in the .magento.app.yaml file
C) Use the VAR_LOCKS_CLEAR variable available for the build stage in the .magento.app.yaml file variable available for the build stage in the
D) You must access the Production environment and delete the lock file