ARA-C01 · Question #16
What are purposes for creating a storage integration? (Choose three.)
The correct answer is B. Store a generated identity and access management (IAM) entity for an external cloud provider C. Support multiple external stages using one single Snowflake object - Storage integrations D. Avoid supplying credentials when creating a stage or when loading or unloading data - By. Storage integrations in Snowflake serve three core purposes addressed by B, C, and D. B is correct: a storage integration creates and stores a Snowflake-managed IAM entity (e.g., an AWS IAM role ARN or Azure service principal) that the external cloud provider trusts…
Question
What are purposes for creating a storage integration? (Choose three.)
Options
- AControl access to Snowflake data using a master encryption key that is maintained in the cloud
- BStore a generated identity and access management (IAM) entity for an external cloud provider
- CSupport multiple external stages using one single Snowflake object - Storage integrations
- DAvoid supplying credentials when creating a stage or when loading or unloading data - By
- ECreate private VPC endpoints that allow direct, secure connectivity between VPCs without
- FManage credentials from multiple cloud providers in one single Snowflake object.
How the community answered
(31 responses)- A3% (1)
- B87% (27)
- E6% (2)
- F3% (1)
Explanation
Storage integrations in Snowflake serve three core purposes addressed by B, C, and D. B is correct: a storage integration creates and stores a Snowflake-managed IAM entity (e.g., an AWS IAM role ARN or Azure service principal) that the external cloud provider trusts, eliminating the need to embed long-lived credentials. C is correct: a single storage integration object can be referenced by multiple external stages, centralizing cloud access configuration. D is correct: because the IAM trust is established via the integration object, users do not need to supply cloud credentials when creating stages or performing load/unload operations. A is incorrect (that describes customer-managed keys / Tri-Secret Secure). E is incorrect (that describes PrivateLink). F is incorrect - a storage integration is scoped to one cloud provider and region, not multiple.
Topics
Community Discussion
No community discussion yet for this question.