先試後買

A. Create a private listing on the Snowflake Marketplace and share it with the specific customer accounts by explicitly granting access to their Snowflake account identifiers.

B. Create a public listing on the Snowflake Marketplace and rely on Snowflake's built-in usage monitoring to identify the intended customer accounts.

C. Create a public listing with a very high price to deter unintended installations, then manually adjust the price to zero for beta testers.

D. Publish the application directly to the Snowflake Marketplace without creating a listing, and then share the installation URL with the selected customer accounts.

E. Use Snowflake's data sharing feature to share the application package with the customer accounts.

A. Expose secure views within the application package. Consumer accounts can then create views in their account that reference these secure views.

B. Create stored procedures that execute 'CREATE VIEW' statements in the consumer's account, controlled by parameters passed from the consumer, using EXECUTE AS OWNER.

C. Utilize Data Sharing to share the underlying tables directly with the consumer account.

D. Grant the 'SELECT privilege directly on the application's underlying tables to a role in the consumer account.

E. Implement a UDF that constructs and executes the user's SQL query against the application's data and returns the results.

A. Reduce the number of columns captured in the event tables to minimize the amount of data being written. Store all tracing data in a single large event table to simplify querying.

B. Implement sampling or conditional logging within the UDFs, only logging events for a subset of executions or when specific conditions are met. Utilize asynchronous logging techniques where appropriate to offload logging operations.

C. Disable event logging entirely for high-volume UDFs to eliminate the performance overhead.

D. Write event data directly to an external cloud storage system (e.g., AWS S3, Azure Blob Storage) bypassing Snowflake's Event Tables altogether.

E. Increase the frequency of event table flushes to reduce the number of events buffered in memory. This minimizes memory pressure and write latency.

A. Use a transient table within the application's managed database.

B. Use an external stage pointing to AWS S3 or Azure Blob Storage.

C. Store the data in the user's temporary stage.

D. Create a volatile table within the application's managed database.

E. Use a permanent table within the application's managed database.

A. Create a stored procedure running as OWNER, grant necessary privileges, then call this SP from UDF running as Invoker.

B. Create a secure view that exposes only the necessary columns of the table, granting 'SELECT privilege on the secure view to the application's invoker role. Configure the UDF to select from this secure view.

C. Grant 'SELECT privilege on the specific table to the application's service user role. Configure the UDF to run as OWNER, and use 'EXECUTE AS OWNER.

D. Grant 'SELECT privilege on the specific table directly to the application's invoker role.

E. Create an API integration that enables the UDF to securely authenticate and access the data through an external service.

A. Utilize secure data sharing with data clean rooms, exposing the required datasets via views on each data clean room.

B. Implement a data access service within the Native App that uses external functions to query data from consumer accounts, relying on network policies for security.

C. Create a shared database from each consumer account containing views over the required tables, granting SELECT privileges on these views to the application role.

D. Package the data extraction logic directly into the Native App using User-Defined Functions (UDFs) that establish secure connections to each consumer account using separate credentials stored securely within the application package.

E. Grant SELECT privileges directly to the application role on all relevant tables in the consumer accounts.

A. GRANT INSERT, UPDATE, DELETE ON TABLE .. TO ROLE ;

B. GRANT USAGE ON DATABASE TO ROLE ;

C. GRANT USAGE ON SCHEMA TO ROLE ;

D. GRANT SELECT ON ALL TABLES IN DATABASE TO ROLE ;

E. GRANT ALL PRIVILEGES ON WAREHOUSE TO ROLE ;

A. Offer a free trial period with limited functionality to allow potential consumers to evaluate the application before committing to a paid subscription.

B. Use Snowflake's built-in resource monitors to proactively track application consumption and alert consumers when they approach predefined spending limits.

C. Refrain from providing any cost-related information upfront to encourage broader adoption, deferring cost discussions until after installation and usage.

D. Provide detailed cost estimation documentation outlining the expected costs for different usage scenarios and data volumes.

E. 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.

A. The application package needs to be explicitly authorized to access secure views in the provider account. This requires a manifest update and resubmission of the package.

B. The UDF is not declared as SECURE, preventing it from accessing objects in a different security context. Declare the UDF as SECURE.

C. The consumer's role does not have the OWNERSHIP privilege on the application object. Assign the OWNERSHIP privilege to the consumer's role.

D. The consumer lacks the necessary permissions on the underlying tables referenced by the secure view in the provider account. Grant the consumer direct access to these tables.

E. The secure view in the provider account has data masking policies applied that prevent the UDF from accessing the data. Remove the masking policies.

A. Instruct consumers to manually create the roles and grant privileges after installation, providing them with a separate documentation file containing the necessary SQL commands.

B. Use a 'CREATE ROLE IF NOT EXISTS' statement within the setup script, followed by 'GRANT statements using the 'APPLICATION' keyword to avoid granting privileges directly to the role within the provider account.

C. Dynamically generate SQL statements within the setup script based on a configuration table stored within the application package, then execute these statements to create the roles and grant privileges.

D. Use a UDF to create the roles and grant privileges. This UDF should be owned by the application and be executed with CALLER's rights.

E. Hardcode the role names in the setup script and create them using a stored procedure executed with the 'OWNER privilege. Then, grant the necessary privileges to those roles.

A. Use which is a function specifically designed to check if the app is running in a consumer account.

B. Examine the session context function 'CURRENT ACCOUNT()' function and compare it with the provider account identifier, if matches then it is a provider. It is the best method.

C. Read an environment variable set during the application installation process by the consumer.

D. Query the view. Presence in this view indicates a provider environment.

A. The application prompts the consumer for their Snowflake account credentials and uses those credentials to access the data.

B. The consumer shares the table directly with the application provider's Snowflake account.

C. The consumer grants the "GLOBAL' privilege 'SELECT on the table directly to the application package name.

D. The consumer creates a secure view on top of the table and grants 'SELECT privilege on the secure view to the application's installed application object (application instance).

E. The application provider requests the 'IMPORTED PRIVILEGES on the consumer account, allowing the application to access any object within the account.

A. Create a new version of the application package. Implement a Snowpark Python stored procedure within the new version that handles schema migrations and data transformations. This procedure should be automatically executed during the upgrade process.

B. Modify the existing application package directly with the updated code and schema. This will automatically update the application for all consumers.

C. Create a new version of the application package. Include a setup script that detects the existing version of the application and performs any necessary schema migrations or data transformations. Announce the new version and instruct consumers to manually upgrade.

D. Create a new version of the application package. Before releasing, use a feature flag system to gradually roll out the new feature to a subset of consumers, monitoring for any issues before a full release.

E. Create a new version of the application package with the updated code and schema. Consumers will automatically be upgraded to the new version upon release.