A cloned container object retains privileges granted on the objects contained in the source object.

Master the SnowPro Advanced Architect Test with flashcards, multiple-choice questions, and detailed explanations. Prepare thoroughly for your certification!

Multiple Choice

A cloned container object retains privileges granted on the objects contained in the source object.

Explanation:
Cloning preserves the state of the object at the moment you create the clone, including its access controls. Because privileges on the contained objects are part of the object's metadata, those grants present on the source’s contained objects at the time of cloning are carried over to the clone. In practice, this means the clone starts with the same access rights as the source for its internal objects, so users and roles that could access those objects before cloning can continue to access them in the clone right away. Keep in mind that changes to privileges on the source after cloning don’t automatically propagate to the clone; you’d need to manage grants on the clone separately if you want them to diverge.

Cloning preserves the state of the object at the moment you create the clone, including its access controls. Because privileges on the contained objects are part of the object's metadata, those grants present on the source’s contained objects at the time of cloning are carried over to the clone. In practice, this means the clone starts with the same access rights as the source for its internal objects, so users and roles that could access those objects before cloning can continue to access them in the clone right away.

Keep in mind that changes to privileges on the source after cloning don’t automatically propagate to the clone; you’d need to manage grants on the clone separately if you want them to diverge.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy