A provider is developing a Snowflake Native Application that shares event data with consumers. The provider wants to ensure that specific columns in the event data are obfuscated for certain consumer accounts, while remaining visible to others. Which of the following approaches is the MOST secure and maintainable way to achieve this?

• A. Create a separate view for each consumer account with the sensitive columns masked using a CASE statement based on the CURRENT_ACCOUNT() function.
• B. Implement dynamic data masking policies on the sensitive columns using the CURRENT_ACCOUNT() function to determine which accounts receive obfuscated data.
• C. Data masking is not supported in Native Apps. The provider must rely on consumer-side masking implementations.
• D. Use a stored procedure to query the event data, applying obfuscation logic based on the consumer's APP INSTANCE ID() before returning the results.
• E. Implement conditional logic within the event table function to obfuscate data based on the consumer's APP_INSTANCE_ID().

You are developing a Snowflake Native Application for a data enrichment service and plan to list it on the Snowflake Marketplace. You want to control the costs incurred by consumers of your application while maximizing its accessibility. Which of the following strategies represent Snowflake Marketplace best practices for cost management and pricing?

• A. Use Snowflake's built-in resource monitors to proactively track application consumption and alert consumers when they approach predefined spending limits.
• B. Offer a free trial period with limited functionality to allow potential consumers to evaluate the application before committing to a paid subscription.
• C. Provide detailed cost estimation documentation outlining the expected costs for different usage scenarios and data volumes.
• D. Implement a tiered pricing model based on data volume processed, compute resources consumed, or number of users accessing the application. Offer a free basic tier with limited functionality.
• E. Refrain from providing any cost-related information upfront to encourage broader adoption, deferring cost discussions until after installation and usage.

You are managing a Snowflake Native Application that provides data enrichment services. Over time, you've accumulated several application package versions: v1 .0 (initial release), v1.1 (bug fixes), v2.0 (new features and schema changes), and v2.1 (performance improvements for v2.0). Some consumers are still using v1 .0, while others have upgraded to v2.1. You need to retire v1.0 to reduce maintenance overhead. Which of the following actions and considerations are MOST important when deprecating vl .0? Select TWO that apply.

• A. Identify consumers still using v1.0. Communicate the deprecation timeline and provide clear instructions on how to upgrade to a supported version. Offer support during the transition.
• B. Immediately drop version v1.0 from the application package to free up storage space.
• C. Keep v1.0 indefinitely to ensure compatibility with all existing application instances, regardless of usage.
• D. Update the application's metadata in the Snowflake Marketplace to indicate that v1.0 is no longer supported.
• E. Automatically migrate all consumers still using v1.0 to the latest version (v2.1 ) without their consent to simplify management.

You have developed a Snowflake Native Application that utilizes a Python UDF to perform sentiment analysis on customer reviews. During consumer testing, you notice that the application is throwing 'ModuleNotFoundError: No module named 'transformers" errors on the consumer's account, even though the 'transformers' library is included in your application's packages directory. Select the two options that best address this issue:

• A. In the UDF code, explicitly add the application's packages directory to the Python path using 'sys.path.append('/app/packages')' before importing the 'transformers' library. Also, bundle the 'transformers' package along with its dependencies into a single zip file and upload it to an internal stage.
• B. Ensure the 'transformers' library is explicitly listed in the 'manifest.ymr file under the 'packages' section and that the application's setup script correctly installs the package using 'pip install transformers.
• C. Check if the consumer account has any conflicting Python packages installed that might be shadowing the 'transformers library. Use the 'SHOW PACKAGES' command in Snowflake to list installed packages and their versions on the consumer account.
• D. Verify that the application role has sufficient privileges (USAGE) on the 'transformers' library and that the consumer account's security policies allow access to external packages. The consumer account must explicitly allow the usage of external packages in their account-level security settings.
• E. Confirm that the application is built using a compatible Python version (e.g., 3.8) with the consumer's environment, and that the 'PYTHON_VERSION' property in the 'manifest.ymr file is set accordingly. Additionally, regenerate the package directory with all dependencies using 'conda' instead of 'pip'.

You are managing versions of a Snowflake Native App that persists data to tables within the consumer's account. You want to provide consumers with the ability to rollback to a previous version of the application without losing dat a. Which combination of Snowflake features and practices would best support this requirement?

• A. Implement a backup and restore mechanism within your application, creating regular snapshots of the consumer's tables and storing them in a secured location. Provide a rollback procedure that restores data from the appropriate snapshot.
• B. Rely solely on Snowflake's Time Travel feature on the consumer's tables, instructing users to manually restore data to the desired point in time after rolling back the application.
• C. Combine Snowflake's Time Travel feature with automated scripts within your application that identify and restore tables affected by the rollback to the specific point in time when the previous version was active. Provide users with a simplified rollback process.
• D. Store data version history within the application and reconstruct historical states on demand. This requires complex data modeling and coding.
• E. Require consumers to manually back up their data before each application upgrade and provide instructions on how to restore it.