The author should save and run the dashboard to inspect the actual consumer-facing behavior. Dashboard Builder's Preview function is designed primarily to preview the current dashboard page during authoring and doesn't always reproduce the complete navigation experience of the executed dashboard.

Oracle distinguishes the authoring workflow from runtime execution: authors can Preview the current page, Save their changes, or select Run to leave Dashboard Builder and display the dashboard as consumers see it. In the executed dashboard, multiple pages are navigated using page tabs across the dashboard viewer. Therefore, running the saved dashboard is the appropriate validation method when the concern is whether multiple dashboard-page tabs appear correctly.

Dashboard Report Links control items such as Print or Export links associated with dashboard content; they don't create dashboard-page tabs. Section Properties affect the layout and behavior of a section rather than dashboard-level navigation. Deleting and recreating the page as a subpage isn't required, and browser-cache clearing doesn't address the distinction between page Preview and dashboard runtime.

Therefore, option C correctly verifies the end-user experience.

Reference Topic: Designing, Creating, and Enhancing Dashboards — Dashboard Pages, Preview, and Runtime Navigation