What is the purpose of versioned artifacts in dashboards in Aware?

• A. To restrict modifications and prevent sharing.
• B. To support rapid experimentation and enable sharing while tracking changes.
• C. To delete old versions automatically.
• D. To force re-authoring dashboards for every update.

Answer: (B)

Versioned artifacts capture snapshots of dashboards over time, which makes experimentation and collaboration practical while keeping a record of changes. With this approach, you can try new designs or data configurations, compare how a dashboard has evolved, and choose the best version to publish. Sharing can target a specific version so others see exactly what you intended, and the history shows who made changes and when. Old versions are preserved to enable rollback and auditing, and updates don’t force you to re-create dashboards from scratch—it's about evolving the work while maintaining a clear trail. The other options describe restricting access, automatic deletion, or requiring re-authoring, none of which align with how versioned artifacts are used to support flexible experimentation and traceable sharing.