A team is building a Native App with the Snowflake Native App Framework. They write the manifest, setup script, and the stored procedures and functions, and they need a single provider-side object that bundles this versioned logic together so it can be published in a listing and later installed into a consumer account. Which object do they create on the provider side to hold the app?
- AAn application package, which holds the versioned app logic and content and is published through a listing for installation Correct
- BA secure share, which is the only object the Native App Framework can attach to a listing for installation by a consumer account
- CAn application object, which the provider creates and then transfers ownership of directly to the consumer account
- DA reader account, which the provider provisions so the consumer can install and run the packaged application logic
Why A is correct: An "application package" is the provider-side container that bundles the manifest, setup script, and versioned logic so it can be listed and installed as an app.
Why B is wrong: Secure shares underpin plain Secure Data Sharing of data, but the Native App Framework packages installable application logic in an application package, not a bare share.
Why C is wrong: The application object is what the consumer ends up with after installation in their own account, not the provider-side bundle, so this confuses the two sides.
Why D is wrong: A reader account lets a non-Snowflake consumer query shared data, but it does not bundle Native App logic for installation, so it solves a different problem.