COPADO-DEVELOPER practice question 5 of 15

Dave has been assigned the task of deleting a custom object. After committing the destructive changes, he notices that no feature branch has been…

Full set: 84 questions
Dave has been assigned the task of deleting a custom object. After committing the destructive changes, he notices that no feature branch has been created. What could be the reason? The Re-Create Feature Branch checkbox was not flagged. The base branch was set to master branch, and the component was not yet in production. He did not have rights to delete the component in the source org. The Re-Create Feature Branch checkbox was flagged. You would like your scratch org to have a namespace. Where can your set this up?
Answer options
A: In the user story.
B: In the project template. Correct answer
C: In the extensions.
D: In the scratch org definition.
Correct Answer:
B. In the project template.
Explanation

In Copado, default scratch-org attributes—including namespace—are stored in the project template’s JSON definition. Adding "namespace": "YourNS" in that template means every scratch org created for the project carries the namespace automatically.

Why Incorrect

A. User stories inherit definitions from the project template; they cannot set namespace directly.
C. Extensions allow additional SFDX commands but do not define namespace.
D. Scratch-org definition files are held inside the project template; you don’t upload them per org in Copado.

References

1. Copado Doc “Creating Scratch Orgs with Project Templates”, Winter ’23, Section ‘Namespace Definition’, steps 3-4.

2. Salesforce DX Dev Guide, “Scratch Org Definition File”, v58, Section ‘namespace’, confirms JSON key usage.

Scroll to Top