SetSuperContent is intended for what purpose in the editor?

• A. It should be used to render final production content.
• B. It is used only for preview and should not be consumed by the custom block.
• C. It is stored in the block's metadata.
• D. It defines the authentication flow.

Answer: (B)

In the editor, you often want a live look at how a block will appear without tying that preview to what gets saved and published. SetSuperContent is there to supply content only for that in-Editor preview layer. It lets the author see how the block behaves and renders while editing, but that preview content isn’t what the block uses when the content is saved or rendered in production. This keeps the editing experience visually accurate without contaminating the final, published data.

So, it’s not meant for final production content, it isn’t something that should be stored with the block’s metadata, and it doesn’t define an authentication flow. It exists purely to drive the editor’s preview.