What should be done manually after deleting a Custom Object in the Dev Sandbox?

What should be done manually after deleting a Custom Object in the Dev Sandbox?

• A. Submit a ticket
• B. Promote the user story
• C. Rollback the changes
• D. Archive the changes

Answer: (B)

When a Custom Object is deleted in the Dev Sandbox, promoting the user story is a necessary step to ensure that the development work, including the changes associated with the Custom Object, is properly managed in the deployment pipeline. Promoting the user story allows the changes to be documented and tracked as they progress through various environments. This process is crucial because the deletion of a Custom Object can impact related components, and by promoting the user story, you can communicate the intent and context of that change to other team members and ensure that all relevant artifacts, like tests or dependencies, are accounted for in further stages of development and deployment. Other options don’t directly correspond with the appropriate actions following a deletion. For example, submitting a ticket may be necessary for support-related issues but does not address the need for documentation or propagation of changes to other environments. Similarly, rolling back changes and archiving are not aligned with the proactive steps that should be taken after a Custom Object has been deleted, as they relate more to restoring previous states or preserving past changes rather than promoting current work.

When a Custom Object is deleted in the Dev Sandbox, promoting the user story is a necessary step to ensure that the development work, including the changes associated with the Custom Object, is properly managed in the deployment pipeline. Promoting the user story allows the changes to be documented and tracked as they progress through various environments.

This process is crucial because the deletion of a Custom Object can impact related components, and by promoting the user story, you can communicate the intent and context of that change to other team members and ensure that all relevant artifacts, like tests or dependencies, are accounted for in further stages of development and deployment.

Other options don’t directly correspond with the appropriate actions following a deletion. For example, submitting a ticket may be necessary for support-related issues but does not address the need for documentation or propagation of changes to other environments. Similarly, rolling back changes and archiving are not aligned with the proactive steps that should be taken after a Custom Object has been deleted, as they relate more to restoring previous states or preserving past changes rather than promoting current work.