SnowPro Specialty: Native Apps free question 8 / 10 · Domain 4: Manage Snowflake Native Applications
Without release channels, a custom release directive pilot_rd covers account ORG1.A. The provider must move the directive to ORG1.B instead. What does the release directive page say to do?
- Set a new version on pilot_rd; the accounts follow the version
- Run MODIFY RELEASE DIRECTIVE pilot_rd with the new account
- Unset pilot_rd, then add it back with ORG1.B straight away
- Add ORG1.B to the default release directive and leave pilot_rd
Show the answer and explanation
Answer: C
Why this is correct
The section "Update a custom release directive" says MODIFY RELEASE DIRECTIVE updates the version or patch of a custom directive, but you cannot modify the accounts associated with it. To change the organization and account, remove the release directive from the application package and then add it back. When you change the accounts, add the new release directive immediately after you remove the old one. Keeping the two steps together keeps the gap between them short.
Why the other options are wrong
"Run MODIFY RELEASE DIRECTIVE pilot_rd with the new account" … MODIFY RELEASE DIRECTIVE updates the version or patch; the page says you cannot modify the accounts associated with the directive.
"Add ORG1.B to the default release directive and leave pilot_rd" … The default release directive applies to all consumers and has no account list. It does not move the custom directive.
"Set a new version on pilot_rd; the accounts follow the version" … Changing the version does not change which accounts the directive covers.
Keep the gap short
Running the unset and the new set together, in one script, keeps the pilot account from briefly falling back to the default version.