Hmm, let's see... B and C, definitely. A SECURITYADMIN can do it, and a role with the ATTACH POLICY privilege can too. Simple as that. Although, I do wonder if the 'CWKERSHIE' is some kind of inside joke. Maybe the Snowflake devs have a sense of humor after all!
Haha, 'CWKERSHIE'? That sounds like something straight out of a Harry Potter book. I'm pretty sure the answer is B and C, but I'm going to write in 'Wizard' as a third option, just in case.
Ah, the age-old question of who can boss around the network policies in Snowflake. My money's on B and D - a SECURITYADMIN and a role with the NETWORK_POLlCY account parameter set. I'm not falling for that 'CWKERSHIE' trap, no sir!
Wait, wait, wait. What's this 'CWKERSHIE' thing? Is that a new Snowflake feature I haven't heard about? I'm gonna have to look that one up. In the meantime, I'm going with B and C too.
Hmm, I think the answer is B and C. A SECURITYADMIN or higher role can definitely enforce network policies, and a role with the ATTACH POLICY privilege can also do it. I'm pretty sure that's how it works in Snowflake.
Yes, you're right! A SECURITYADMIN or higher role and a role with the ATTACH POLICY privilege can activate and enforce network policies in a Snowflake account.
Yes, you're right! A SECURITYADMIN or higher role and a role with the ATTACH POLICY privilege can activate and enforce network policies in a Snowflake account.
Ashton
4 months agoTawanna
4 months agoTammi
4 months agoErnest
4 months agoRosendo
3 months agoNidia
4 months agoAaron
4 months agoDorothea
4 months agoQueen
5 months agoArt
3 months agoAdela
3 months agoTamera
4 months agoAlona
4 months agoAnisha
4 months agoMarcelle
4 months agoNaomi
5 months agoMirta
5 months ago