SnowPro Specialty: Native Apps free question 9 / 10 · Domain 4: Manage Snowflake Native Applications
An urgent fix must reach consumers in a remote region that receive the app through Cross-Cloud Auto-Fulfillment. What does the legacy upgrade page suggest, and what trade-off does it name?
- Ship the fix as a new version, which upgrades remote regions first
- Contact Snowflake Support right away, which then pauses the refresh schedule
- Reduce the listing's refresh frequency, which can raise replication costs
- Ask consumers there to reinstall, which resets their app data
Show the answer and explanation
Answer: C
Why this is correct
The section "Upgrade an app across regions" says changes to an installed app in a consumer account might not be visible until the refresh to remote regions is performed. The APPLICATION_STATE view can be used to monitor the state, and if the upgrade is not complete more than one day after the first refresh following the upgrade, the provider should contact Snowflake Support. With Cross-Cloud Auto-Fulfillment, automated upgrades may take some time, depending on the refresh schedule, the number of installed instances and the number of regions. If the upgrade contains an urgent fix, the provider can reduce the refresh frequency of the listing to a smaller value. Reducing the refresh frequency can increase the costs associated with replication.
Why the other options are wrong
"Ask consumers there to reinstall, which resets their app data" … The page does not suggest reinstalling for an urgent fix. It suggests changing the refresh frequency.
"Ship the fix as a new version, which upgrades remote regions first" … The page does not order regions by version or patch. Remote regions see changes after the refresh.
"Contact Snowflake Support right away, which then pauses the refresh schedule" … The page suggests contacting Support when an upgrade is not complete more than one day after the first refresh following it, which is a different case.
Tighten, then relax
Shortening the refresh for an urgent fix and restoring it afterwards limits the extra replication cost to the period when it matters.