Snowflake SnowPro Core Practice Test 93
Question 920
For an original SnowPro Core educational scenario, consider: A provider wants different sets of shared objects for different subscriber roles and has not planned privilege segmentation. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Create and test suitable secure views with correct row and column projection plus consumer-specific filtering where supported.
- Check: Review SHOW GRANTS TO SHARE, database-role assignments and consumer-visible objects with a test account.
- Grant all privileges on every schema to PUBLIC to fix one share's missing SELECT.
- Check: Test CREATE DATABASE FROM SHARE, role access to a sample table and attempted writes.
- Change: Grant appropriate database, schema and object privileges to the share or grant a scoped database role to the share.
Explanation
Correct Answer
B:Shared objects require valid provider-side grants and can be grouped through supported database-role sharing patterns. Acceptance: Only intended objects are visible through the share and privilege gaps are resolved safely.
E:Shared objects require valid provider-side grants and can be grouped through supported database-role sharing patterns. Evidence: Review SHOW GRANTS TO SHARE, database-role assignments and consumer-visible objects with a test account.
Incorrect Answers
A:Change: Create and test suitable secure views with correct row and column projection plus consumer-specific filtering where supported. Shared objects require valid provider-side grants and can be grouped through supported database-role sharing patterns.
C:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Shared objects require valid provider-side grants and can be grouped through supported database-role sharing patterns.
D:Check: Test CREATE DATABASE FROM SHARE, role access to a sample table and attempted writes. Shared objects require valid provider-side grants and can be grouped through supported database-role sharing patterns.
Question 921
A Snowflake engineer is examining this platform situation: A supplier should see only its own purchase orders, not other suppliers' rows in a broad source table. A proposed shortcut is: Share the entire base table and tell consumers not to query other suppliers' rows. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Create and test suitable secure views with correct row and column projection plus consumer-specific filtering where supported.
- Remove unauthorized consumer accounts or grants from the share and validate loss of access with the recipient.
- Share the entire base table and tell consumers not to query other suppliers' rows.
- Grant appropriate database, schema and object privileges to the share or grant a scoped database role to the share.
Explanation
Correct Answer
A:Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information. Applied case: A supplier should see only its own purchase orders, not other suppliers' rows in a broad source table.
Incorrect Answers
B:Remove unauthorized consumer accounts or grants from the share and validate loss of access with the recipient. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
C:Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
D:Grant appropriate database, schema and object privileges to the share or grant a scoped database role to the share. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
Question 922
A Snowflake implementation review finds: A supplier should see only its own purchase orders, not other suppliers' rows in a broad source table. The team proposes: Create and test suitable secure views with correct row and column projection plus consumer-specific filtering where supported. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Sharing within a region differs from replicated fulfillment across geographic or cloud boundaries; data movement and control requirements apply.
- Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
- Provider control includes revocation; removing a consumer can invalidate access to its imported database without deleting the provider's source.
- Clean room collaboration is designed to support permitted analytics while controlling access to underlying participant data and query outputs.
Explanation
Correct Answer
B:Demonstrable success requires: Each partner receives only its authorized subset without revealing internal sensitive columns. This principle explains the proposed technical approach, which is: Create and test suitable secure views with correct row and column projection plus consumer-specific filtering where supported.
Incorrect Answers
A:Sharing within a region differs from replicated fulfillment across geographic or cloud boundaries; data movement and control requirements apply. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
C:Provider control includes revocation; removing a consumer can invalidate access to its imported database without deleting the provider's source. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
D:Clean room collaboration is designed to support permitted analytics while controlling access to underlying participant data and query outputs. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
Question 923
The data platform team has not yet approved changes. Current evidence indicates: A supplier should see only its own purchase orders, not other suppliers' rows in a broad source table. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Review supported fulfillment region selections, refresh status, provider costs and consumer availability.
- Use representative simulated consumer context or controlled subscriber tests to verify row filters and column exposure.
- Compare share membership before and after removal, attempt a consumer query and inspect surviving provider data.
- Inspect reader account provisioning, attached shares, warehouse credit consumption and restrictions on write operations.
Explanation
Correct Answer
B:Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information. If confirmed, the proportionate intervention is: Create and test suitable secure views with correct row and column projection plus consumer-specific filtering where supported.
Incorrect Answers
A:Review supported fulfillment region selections, refresh status, provider costs and consumer availability. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
C:Compare share membership before and after removal, attempt a consumer query and inspect surviving provider data. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
D:Inspect reader account provisioning, attached shares, warehouse credit consumption and restrictions on write operations. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
Question 924
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A supplier should see only its own purchase orders, not other suppliers' rows in a broad source table. The service owner needs positive and negative results and evidence that legitimate data workflows still function. Which acceptance result demonstrates correct platform behavior without disrupting authorized workflows? Select ONE best answer.
- The recipient can query approved datasets without a separate Snowflake account and costs are controlled by the provider.
- Each partner receives only its authorized subset without revealing internal sensitive columns.
- The former subscriber loses access while authorized subscribers and the original dataset remain available.
- Consumers see authorized current records while the provider controls membership and original data.
Explanation
Correct Answer
B:Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information. The approved implementation step was: Create and test suitable secure views with correct row and column projection plus consumer-specific filtering where supported.
Incorrect Answers
A:The recipient can query approved datasets without a separate Snowflake account and costs are controlled by the provider. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
C:The former subscriber loses access while authorized subscribers and the original dataset remain available. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
D:Consumers see authorized current records while the provider controls membership and original data. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
Question 925
An implementation sign-off request identifies the following problem: A supplier should see only its own purchase orders, not other suppliers' rows in a broad source table. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- Change: Create and test suitable secure views with correct row and column projection plus consumer-specific filtering where supported. Verify: Use representative simulated consumer context or controlled subscriber tests to verify row filters and column exposure.
- Change: Provision a governed reader account and share suitable data while monitoring the provider-funded compute and usage limits. Verify: Inspect reader account provisioning, attached shares, warehouse credit consumption and restrictions on write operations.
- Change: Evaluate an approved Snowflake clean room or governed collaboration workflow with restricted query templates, join controls and aggregate privacy requirements. Verify: Inspect allowed queries, match-key protections, minimum group thresholds and sample privacy-leakage tests.
- Change: Remove unauthorized consumer accounts or grants from the share and validate loss of access with the recipient. Verify: Compare share membership before and after removal, attempt a consumer query and inspect surviving provider data.
Explanation
Correct Answer
A:Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information. The change is successful only when: Each partner receives only its authorized subset without revealing internal sensitive columns.
Incorrect Answers
B:Change: Provision a governed reader account and share suitable data while monitoring the provider-funded compute and usage limits. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
C:Change: Evaluate an approved Snowflake clean room or governed collaboration workflow with restricted query templates, join controls and aggregate privacy requirements. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
D:Change: Remove unauthorized consumer accounts or grants from the share and validate loss of access with the recipient.
Question 926
A Snowflake engineer is examining this platform situation: A marketplace publisher wants to hide proprietary transformation logic while exposing a curated aggregate view. A proposed shortcut is: Share the entire base table and tell consumers not to query other suppliers' rows. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Create and test suitable secure views with correct row and column projection plus consumer-specific filtering where supported.
- Share the entire base table and tell consumers not to query other suppliers' rows.
- Use a supported Snowflake listing with appropriate discoverability, metadata, availability and consumer access controls.
- Remove unauthorized consumer accounts or grants from the share and validate loss of access with the recipient.
Explanation
Correct Answer
A:Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information. Applied case: A marketplace publisher wants to hide proprietary transformation logic while exposing a curated aggregate view.
Incorrect Answers
B:Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information. Use this instead: Create and test suitable secure views with correct row and column projection plus consumer-specific filtering where supported.
C:Use a supported Snowflake listing with appropriate discoverability, metadata, availability and consumer access controls. A marketplace publisher wants to hide proprietary transformation logic while exposing a curated aggregate view.
D:Remove unauthorized consumer accounts or grants from the share and validate loss of access with the recipient. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
Question 927
A Snowflake implementation review finds: A marketplace publisher wants to hide proprietary transformation logic while exposing a curated aggregate view. The team proposes: Create and test suitable secure views with correct row and column projection plus consumer-specific filtering where supported. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Snowflake Secure Data Sharing can expose provider-managed current data without copying it, and consumer access is read-only.
- Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
- Reader accounts permit consumers without Snowflake accounts to query provider shares, but the provider manages and pays for reader account warehouse usage.
- Shared objects require valid provider-side grants and can be grouped through supported database-role sharing patterns.
Explanation
Correct Answer
B:Demonstrable success requires: Each partner receives only its authorized subset without revealing internal sensitive columns. Applied case: A marketplace publisher wants to hide proprietary transformation logic while exposing a curated aggregate view.
Incorrect Answers
A:Snowflake Secure Data Sharing can expose provider-managed current data without copying it, and consumer access is read-only. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
C:Reader accounts permit consumers without Snowflake accounts to query provider shares, but the provider manages and pays for reader account warehouse usage. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
D:Shared objects require valid provider-side grants and can be grouped through supported database-role sharing patterns. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
Question 928
The data platform team has not yet approved changes. Current evidence indicates: A marketplace publisher wants to hide proprietary transformation logic while exposing a curated aggregate view. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Use representative simulated consumer context or controlled subscriber tests to verify row filters and column exposure.
- Review membership, listing access settings, user request flow and a nonmember denial test.
- Compare share grants, authorized account identifiers and consumer database results after a controlled provider update.
- Inspect allowed queries, match-key protections, minimum group thresholds and sample privacy-leakage tests.
Explanation
Correct Answer
A:Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information. Confirm afterward that: Each partner receives only its authorized subset without revealing internal sensitive columns.
Incorrect Answers
B:Review membership, listing access settings, user request flow and a nonmember denial test. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
C:Compare share grants, authorized account identifiers and consumer database results after a controlled provider update. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
D:Inspect allowed queries, match-key protections, minimum group thresholds and sample privacy-leakage tests. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
Question 929
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A marketplace publisher wants to hide proprietary transformation logic while exposing a curated aggregate view. The service owner needs positive and negative results and evidence that legitimate data workflows still function. Which acceptance result demonstrates correct platform behavior without disrupting authorized workflows? Select ONE best answer.
- Authorized analysts read the shared data while modifying the provider's source remains disallowed.
- Each partner receives only its authorized subset without revealing internal sensitive columns.
- Approved remote consumers can access a refreshed dataset in their region with documented latency and controls.
- Only intended objects are visible through the share and privilege gaps are resolved safely.
Explanation
Correct Answer
B:Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:Authorized analysts read the shared data while modifying the provider's source remains disallowed. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
C:Approved remote consumers can access a refreshed dataset in their region with documented latency and controls. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
D:Only intended objects are visible through the share and privilege gaps are resolved safely. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
Question 930
For an original SnowPro Core educational scenario, consider: A marketplace publisher wants to hide proprietary transformation logic while exposing a curated aggregate view. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Create a database FROM SHARE and grant supported IMPORTED PRIVILEGES or shared database roles to designated consumer account roles.
- Change: Create and test suitable secure views with correct row and column projection plus consumer-specific filtering where supported.
- Share the entire base table and tell consumers not to query other suppliers' rows.
- Check: Use representative simulated consumer context or controlled subscriber tests to verify row filters and column exposure.
- Check: Inspect allowed queries, match-key protections, minimum group thresholds and sample privacy-leakage tests.
Explanation
Correct Answer
B:Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information. Acceptance: Each partner receives only its authorized subset without revealing internal sensitive columns.
D:Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information. Required intervention: Create and test suitable secure views with correct row and column projection plus consumer-specific filtering where supported.
Incorrect Answers
A:Change: Create a database FROM SHARE and grant supported IMPORTED PRIVILEGES or shared database roles to designated consumer account roles. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
C:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
E:Check: Inspect allowed queries, match-key protections, minimum group thresholds and sample privacy-leakage tests. Secure views can help protect underlying logic and enforce a carefully designed shared projection; ordinary raw-table sharing may expose extra information.
