How do secure views compare to non-secure views in Snowflake?
Correct Answer: D
Secure views and non-secure views in Snowflake are differentiated primarily by their handling of data access and security rather than performance characteristics. A secure view enforces row-level security and ensures that the view definition is hidden from the users. However, in terms of performance, secure views do not inherently execute slower or faster than non-secure views. The performance of both types of views depends more on other factors such as underlying table design, query complexity, and system workload rather than the security features embedded in the views themselves. References: Snowflake Documentation on Views: This section provides an overview of both secure and non-secure views, clarifying that the main difference lies in security features rather than performance, thus supporting the assertion that there are no inherent performance differences.
Question 152
Which copy INTO command outputs the data into one file?
Correct Answer: B
The COPY INTO command in Snowflake can be configured to output data into a single file by setting the MAX_FILE_NUMBER option to 1. This option limits the number of files generated by the command, ensuring that only one file is created regardless of the amount of data being exported. References: [ COF-C03 ] SnowPro Core Certification Exam Study Guide Snowflake Documentation on Data Unloading
Question 153
By default, which role is required to change the refresh frequency for an auto-fulfilled application package?
Correct Answer: C
The correct answer is C. GLOBALORGADMIN . Corrected typos: The original options contain typing errors: A). ACCOUNT AUXIN should be ACCOUNTADMIN B). SYSAEMIN should be SYSADMIN C). CLOBALORGADMIN should be GLOBALORGADMIN D). HECURITYADMIH should be SECURITYADMIN Auto-fulfillment is an organization-level capability related to Snowflake Native Apps and listings across regions or accounts. Because refresh frequency for auto-fulfilled application packages is managed at the organization/global level, the required role is GLOBALORGADMIN. Why C is correct: GLOBALORGADMIN is the organization-level administrative role used for managing organization-wide features. Changing the refresh frequency for an auto-fulfilled application package requires this higher-level administrative authority. Why the other options are incorrect: A). ACCOUNTADMIN is the highest administrative role within a Snowflake account, but auto-fulfillment refresh frequency is an organization-level setting. B). SYSADMIN manages account objects such as warehouses, databases, schemas, and tables, but it does not manage organization-level auto-fulfillment settings by default. D). SECURITYADMIN manages users, roles, and grants, but it is not the default role for managing auto- fulfillment refresh frequency. Official Snowflake documentation reference: Snowflake documentation for auto-fulfillment and organization-level administration identifies GLOBALORGADMIN as the role used for managing organization-level Snowflake features. Reference: Snowflake Documentation - Auto-fulfillment; Snowflake Documentation - Organization roles; Snowflake Documentation - Snowflake Native Apps; SnowPro Core Study Guide - Snowflake Account and Resource Management.
Question 154
The bulk data load history that is available upon completion of the COPY statement is stored where and for how long?
Correct Answer: D
The bulk data load history available after a COPY statement is stored in the metadata of the pipe and is retained for 64 days1.
Question 155
When a Snowflake user loads CSV data from a stage, which copy into < table > command guideline should they follow?
Correct Answer: B
When using theCOPY INTO < table > command to load CSV data from a stage into a Snowflake table, one of the crucial guidelines to follow is that the number of columns in each row within the CSV file should be consistent. This ensures data integrity and allows for a smooth data loading process, as Snowflake expects each row in the CSV file to map directly to a row in the target table based on the number of columns. If there ' s a mismatch in the number of columns between any row in the file and the target table, Snowflake might return an error or produce unexpected results during the load operation. It ' s important to note that while the CSV field delimiter can be specified to something other than a comma, ensuring the consistency in the number of columns across all rows is fundamental to successfully loading data. References: Snowflake Documentation on Loading Data: Loading CSV Data
