CertSafari
    Snowflake SnowPro Specialty: Native Apps· Lessons

    Domain 4 · Lesson 11/12

    Uninstalling a Native App with DROP APPLICATION

    Manage the consumer application lifecycle.

    8 min read
    9.67% of exam
    5 sources
    Published 21 Oct 2026
    Docs as of 18 Oct 2026

    What you will be able to do

    • Decide whether to suspend an app's compute or drop the app
    • Prepare an account for uninstall so that wanted objects and data survive
    • Predict what DROP APPLICATION removes with and without CASCADE, including application roles and nested objects

    1.Suspending compute instead of uninstalling

    Uninstalling a Native App cannot be undone. DROP APPLICATION removes the application object and everything inside it, and Snowflake does not support UNDROP for applications. Before you drop an app, decide whether you want it gone or only want it to stop costing money. Those two goals call for different actions.

    If cost is the reason, suspend the compute the app created and keep the app installed. For an app built on Snowpark Container Services, ALTER COMPUTE POOL ... SUSPEND stops the container workloads and their compute charges. For a warehouse-based app, suspend the warehouses it created. Data, configuration and grants all stay where they are, so resuming the app later means resuming its compute, not reinstalling and reconfiguring it.

    A suspended app is still installed, so it still receives upgrades. Snowflake upgrades installed apps automatically when a provider publishes a new version or patch, with no action from the consumer. A consumer can steer the timing with a maintenance policy, a schedule that holds upgrades back until a window they choose. Suspending an app's resources does not pause its upgrade schedule, and upgrades continue to be applied during the configured maintenance window. An app that is switched off for a quarter will be on a newer version when you switch it back on.

    Checkpoint 1 of 3· Check yourself

    A consumer wants to stop paying for an SPCS-based Native App for one quarter and use it again afterwards with its data and grants intact. What should they do, and what happens to the app during that quarter?

    Sources1234

    2.Preparing an account before dropping an app

    Most of the damage from a careless uninstall comes from objects the app owns outside its own boundary. Through its grants, an app can create warehouses, databases, stages or compute pools in your account, and it may still own them. Without CASCADE, DROP APPLICATION refuses to run while those objects exist and returns an error instead. That error is your prompt to decide what to keep.

    Work through these steps before running the drop:

    1. Transfer ownership of any outside object you want to keep. Use a role with the MANAGE GRANTS privilege to run GRANT OWNERSHIP to one of your own roles. The new owner does not need to be ACCOUNTADMIN.
    2. Drop or transfer the compute pools a container app created. A pool still bound to the app when it is dropped becomes unusable and must be dropped manually. Reinstalling the same app under the same name does not make it usable again.
    3. Export any data inside the APPLICATION boundary that you want to keep. That data is removed with the app, so arrange the export through the app or with the provider.
    4. Cancel any paid listing subscription in Snowflake Marketplace. Dropping the app does not stop the billing.

    The drop itself can be run by the app's owner or by a user with the MANAGE GRANTS privilege on the app. The ownership transfers in step 1 need MANAGE GRANTS as well, so a role with that privilege can carry out the whole uninstall.

    Checkpoint 2 of 3· Check yourself

    Before uninstalling an SPCS-based Native App, an admin finds that the app still owns a database the team wants to keep and a compute pool it created. Which plan keeps the database and leaves nothing broken behind?

    Sources12

    3.What DROP APPLICATION removes, with and without CASCADE

    Three things go with every drop, whether or not you use CASCADE. The APPLICATION object goes, along with everything inside it: schemas, tables, procedures, Streamlit apps and services. All application roles are dropped too, so any access those roles granted on objects in your account is lost immediately. Nothing can be undropped. Your event table, if you configured one, is not affected because it belongs to you.

    Application roles are how an app hands out access. The app's setup script creates them, they can exist only inside an app, and the role that installed the app receives them automatically. That owner can then grant them to other roles in your account. Privileges granted to an application role can cover the app's own schemas and procedures as well as objects outside the app, so a role that reads data through an application role loses that access the moment the roles are dropped.

    CASCADE decides what happens to objects the app owns outside itself. Without it, the drop fails if any such objects exist. With it, every object the app owns is dropped, including tables whose primary or unique keys are referenced by foreign keys in your other tables. An app-owned table that your own tables reference therefore causes an error without CASCADE and is removed with it.

    Transferring ownership protects an object only if its container is also out of the app's hands. Objects you took ownership of normally stay in your account. CASCADE, however, removes everything inside an app-owned container, including schemas and tables your own roles own. To keep a table the app created, transfer ownership of the table and of the database and schema that contain it, then drop the app without CASCADE. If the drop succeeds without CASCADE, the app owned nothing outside itself.

    Effect of DROP APPLICATION with and without CASCADE
    ObjectWithout CASCADEWith CASCADE
    APPLICATION object and everything inside itDroppedDropped
    Application roles and the access they grantedDropped; access lostDropped; access lost
    App-owned objects outside the app (warehouses, databases, tables)Command returns an errorDropped, including tables referenced by foreign keys
    Your objects inside an app-owned containerNot reached (command errors if the container exists)Dropped with the container
    Objects you own in your own containersRemainRemain
    Your event tableNot affectedNot affected

    Checkpoint 3 of 3· Match them up

    Match each object to what happens to it when a consumer drops a Native App, with or without CASCADE

    Tap a term, then the definition that fits it.

    Sources251

    Sources

    (5)

    Every claim above is drawn from one of these pages, quoted as it was written on the date shown.

    1. 1.
      “Dropping a Snowflake Native App is a permanent, irreversible action.”
      ↩︎ Suspending compute instead of uninstalling
      “The app itself remains installed and subject to its upgrade schedule even while its resources are suspended.”
      ↩︎ Suspending compute instead of uninstalling
      “DROP APPLICATION without CASCADE returns an error when the app owns objects outside itself.”
      ↩︎ Preparing an account before dropping an app
      “Even if you reinstall the same app from the same package and version with the same name, the orphaned compute pool cannot be reused.”
      ↩︎ Preparing an account before dropping an app
      “Data inside the APPLICATION object is removed when the app is dropped.”
      ↩︎ Preparing an account before dropping an app
      “Your event table, if configured, is not affected: it belongs to you.”
      ↩︎ What DROP APPLICATION removes, with and without CASCADE
      “Objects whose ownership you transferred remain in your account.”
      ↩︎ What DROP APPLICATION removes, with and without CASCADE
      “The app itself remains installed and subject to its upgrade schedule even while its resources are suspended.”
      ↩︎ Exam trap 2
      “Dropping the app does not automatically cancel a paid listing subscription.”
      ↩︎ Exam trap 3
      “use a role with the MANAGE GRANTS privilege to transfer ownership to one of your own roles before you drop the app.”
      ↩︎ Checkpoint
      “Objects the app owned outside the APPLICATION boundary are dropped if you used CASCADE, including objects your roles own inside them.”
      ↩︎ Checkpoint
    2. 2.
      “UNDROP is not supported for APPLICATION objects.”
      ↩︎ Suspending compute instead of uninstalling
      “This command can be run by the app owner or a user with the MANAGE GRANTS privilege on the app.”
      ↩︎ Preparing an account before dropping an app
      “All app roles are dropped when the application object is dropped.”
      ↩︎ What DROP APPLICATION removes, with and without CASCADE
      “Any access granted by those roles on objects in the consumer account is lost.”
      ↩︎ What DROP APPLICATION removes, with and without CASCADE
      “including tables with primary or unique keys that are referenced by foreign keys in other tables”
      ↩︎ What DROP APPLICATION removes, with and without CASCADE
      “running this command with CASCADE also drops those objects”
      ↩︎ Exam trap 1
      “running this command with CASCADE also drops those objects”
      ↩︎ Prediction
    3. 4.
      “consumers can set a maintenance policy for an upgrade so that apps don’t update during specific time periods”
      ↩︎ Suspending compute instead of uninstalling
    4. 5.
      “Application roles defined in the setup script are automatically granted to the role owning the app instance.”
      ↩︎ What DROP APPLICATION removes, with and without CASCADE
      “Unlike database roles, application roles may also be granted privileges on objects outside of the installed app.”
      ↩︎ What DROP APPLICATION removes, with and without CASCADE

    Ready to test yourself?

    Practise the 35 questions on this subdomain.

    Spotted a mistake, or was something unclear? Tell us.