McAfee-Secured Website

Exam Bundle

Exam Code: SnowPro Core COF-C03

Exam Name SnowPro Core COF-C03

Certification Provider: Snowflake

Snowflake SnowPro Core COF-C03 Bundle $19.99

100% Snowflake SnowPro Core COF-C03 Guaranteed Success With Testking Training Materials

Get Real SnowPro Core COF-C03 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    SnowPro Core COF-C03 Questions & Answers

    116 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual SnowPro Core COF-C03 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • Study Guide

    SnowPro Core COF-C03 Study Guide

    222 PDF Pages

    Developed by industry experts, this 222-page guide spells out in painstaking detail all of the information you need to ace SnowPro Core COF-C03 exam.

SnowPro Core COF-C03 Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $154.98
Bundle Price: $134.99

Purchase Individually

  • Questions & Answers

    Questions & Answers

    116 Questions

    $124.99
  • Study Guide

    Study Guide

    222 PDF Pages

    $29.99

Snowflake SnowPro Core COF-C03 Practice Test 31

Question 300

An investigator suspects secondary roles influence a SELECT's authorization. Which session control should they review?

  1. USE SECONDARY ROLES
  2. CURRENT_ROLE()
  3. GRANT ROLE
  4. USE ROLE

Explanation

Correct Answer

A:

Correct: USE SECONDARY ROLES setting. USE SECONDARY ROLES specifies whether eligible secondary roles contribute to access.

Incorrect Answers

B:

Incorrect for this requirement: CURRENT_ROLE() returns the session's current primary role; the problem instead calls for USE SECONDARY ROLES setting.

C:

Incorrect for this requirement: GRANT ROLE assigns role membership to a user or another role; the problem instead calls for USE SECONDARY ROLES setting.

D:

Incorrect for this requirement: USE ROLE switches the session's primary role; the problem instead calls for USE SECONDARY ROLES setting.

Question 301

A role has the right grants but the user was never assigned membership. What operation is needed?

  1. CURRENT_ROLE()
  2. USE SECONDARY ROLES
  3. USE ROLE
  4. GRANT ROLE

Explanation

Correct Answer

D:

Correct: GRANT ROLE to the user. GRANT ROLE assigns role membership to a user or another role.

Incorrect Answers

A:

Incorrect for this requirement: CURRENT_ROLE() returns the session's current primary role; the problem instead calls for GRANT ROLE to the user.

B:

Incorrect for this requirement: USE SECONDARY ROLES specifies whether eligible secondary roles contribute to access; the problem instead calls for GRANT ROLE to the user.

C:

Incorrect for this requirement: USE ROLE switches the session's primary role; the problem instead calls for GRANT ROLE to the user.

Question 302

Security needs a history of failed user sign-ins and their client addresses. Which view should be reviewed?

  1. QUERY_HISTORY
  2. ACCESS_HISTORY
  3. GRANTS_TO_ROLES
  4. LOGIN_HISTORY

Explanation

Correct Answer

D:

Correct: login attempt records. LOGIN_HISTORY records account login attempts and related authentication outcomes.

Incorrect Answers

A:

Incorrect for this requirement: QUERY_HISTORY records SQL statement execution context and metrics; the problem instead calls for login attempt records.

B:

Incorrect for this requirement: ACCESS_HISTORY captures supported base object access and column lineage evidence; the problem instead calls for login attempt records.

C:

Incorrect for this requirement: GRANTS_TO_ROLES records object grants assigned to roles for audit reporting; the problem instead calls for login attempt records.

Question 303

Operations wants to know who ran a destructive DELETE and when. Which history is a starting point?

  1. QUERY_HISTORY
  2. LOGIN_HISTORY
  3. ACCESS_HISTORY
  4. GRANTS_TO_ROLES

Explanation

Correct Answer

A:

Correct: SQL execution audit. QUERY_HISTORY records SQL statement execution context and metrics.

Incorrect Answers

B:

Incorrect for this requirement: LOGIN_HISTORY records account login attempts and related authentication outcomes; the problem instead calls for SQL execution audit.

C:

Incorrect for this requirement: ACCESS_HISTORY captures supported base object access and column lineage evidence; the problem instead calls for SQL execution audit.

D:

Incorrect for this requirement: GRANTS_TO_ROLES records object grants assigned to roles for audit reporting; the problem instead calls for SQL execution audit.

Question 304

An analyst must trace whether an ETL query read specific sensitive base columns. Which history view is relevant?

  1. ACCESS_HISTORY
  2. LOGIN_HISTORY
  3. QUERY_HISTORY
  4. GRANTS_TO_ROLES

Explanation

Correct Answer

A:

Correct: access and column lineage. ACCESS_HISTORY captures supported base object access and column lineage evidence.

Incorrect Answers

B:

Incorrect for this requirement: LOGIN_HISTORY records account login attempts and related authentication outcomes; the problem instead calls for access and column lineage.

C:

Incorrect for this requirement: QUERY_HISTORY records SQL statement execution context and metrics; the problem instead calls for access and column lineage.

D:

Incorrect for this requirement: GRANTS_TO_ROLES records object grants assigned to roles for audit reporting; the problem instead calls for access and column lineage.

Question 305

An auditor must list object privileges historically granted to account roles. What view fits?

  1. LOGIN_HISTORY
  2. QUERY_HISTORY
  3. ACCESS_HISTORY
  4. GRANTS_TO_ROLES

Explanation

Correct Answer

D:

Correct: grant records. GRANTS_TO_ROLES records object grants assigned to roles for audit reporting.

Incorrect Answers

A:

Incorrect for this requirement: LOGIN_HISTORY records account login attempts and related authentication outcomes; the problem instead calls for grant records.

B:

Incorrect for this requirement: QUERY_HISTORY records SQL statement execution context and metrics; the problem instead calls for grant records.

C:

Incorrect for this requirement: ACCESS_HISTORY captures supported base object access and column lineage evidence; the problem instead calls for grant records.

Question 306

Suspicious failed logins spike overnight. Which account history is most directly useful?

  1. LOGIN_HISTORY
  2. QUERY_HISTORY
  3. ACCESS_HISTORY
  4. GRANTS_TO_ROLES

Explanation

Correct Answer

A:

Correct: authentication events. LOGIN_HISTORY records account login attempts and related authentication outcomes.

Incorrect Answers

B:

Incorrect for this requirement: QUERY_HISTORY records SQL statement execution context and metrics; the problem instead calls for authentication events.

C:

Incorrect for this requirement: ACCESS_HISTORY captures supported base object access and column lineage evidence; the problem instead calls for authentication events.

D:

Incorrect for this requirement: GRANTS_TO_ROLES records object grants assigned to roles for audit reporting; the problem instead calls for authentication events.

Question 307

A stored procedure may have executed an expensive query. Which account history shows statement timing and status?

  1. QUERY_HISTORY
  2. LOGIN_HISTORY
  3. ACCESS_HISTORY
  4. GRANTS_TO_ROLES

Explanation

Correct Answer

A:

Correct: query execution records. QUERY_HISTORY records SQL statement execution context and metrics.

Incorrect Answers

B:

Incorrect for this requirement: LOGIN_HISTORY records account login attempts and related authentication outcomes; the problem instead calls for query execution records.

C:

Incorrect for this requirement: ACCESS_HISTORY captures supported base object access and column lineage evidence; the problem instead calls for query execution records.

D:

Incorrect for this requirement: GRANTS_TO_ROLES records object grants assigned to roles for audit reporting; the problem instead calls for query execution records.

Question 308

The governance team wants evidence of underlying table objects referenced through a view. What history view helps?

  1. LOGIN_HISTORY
  2. QUERY_HISTORY
  3. ACCESS_HISTORY
  4. GRANTS_TO_ROLES

Explanation

Correct Answer

C:

Correct: base-object access data. ACCESS_HISTORY captures supported base object access and column lineage evidence.

Incorrect Answers

A:

Incorrect for this requirement: LOGIN_HISTORY records account login attempts and related authentication outcomes; the problem instead calls for base-object access data.

B:

Incorrect for this requirement: QUERY_HISTORY records SQL statement execution context and metrics; the problem instead calls for base-object access data.

D:

Incorrect for this requirement: GRANTS_TO_ROLES records object grants assigned to roles for audit reporting; the problem instead calls for base-object access data.

Question 309

A sensitive field must appear redacted for most users regardless of aggregation. Which policy category fits?

  1. Row access policy
  2. Aggregation policy
  3. Join policy
  4. Masking policy

Explanation

Correct Answer

D:

Correct: column-value obfuscation. Masking policy limits exposed values of protected columns conditionally.

Incorrect Answers

A:

Incorrect for this requirement: Row access policy filters visible rows according to a policy expression; the problem instead calls for column-value obfuscation.

B:

Incorrect for this requirement: Aggregation policy can require protected data to be queried in qualifying aggregate groups; the problem instead calls for column-value obfuscation.

C:

Incorrect for this requirement: Join policy can limit which columns are permitted for joins on protected tables; the problem instead calls for column-value obfuscation.

Question 310

An account-level business role can see only rows for its assigned branch. Which policy fits?

  1. Masking policy
  2. Aggregation policy
  3. Join policy
  4. Row access policy

Explanation

Correct Answer

D:

Correct: row visibility filtering. Row access policy filters visible rows according to a policy expression.

Incorrect Answers

A:

Incorrect for this requirement: Masking policy limits exposed values of protected columns conditionally; the problem instead calls for row visibility filtering.

B:

Incorrect for this requirement: Aggregation policy can require protected data to be queried in qualifying aggregate groups; the problem instead calls for row visibility filtering.

C:

Incorrect for this requirement: Join policy can limit which columns are permitted for joins on protected tables; the problem instead calls for row visibility filtering.