14.2 Custom Views & Scheduled Reports

Build Reusable Evidence

A View defines how selected objects and data are presented. A report template assembles reusable content into a generated document, while a dashboard supports interactive exploration. Choose the artifact from the audience's task: an operator investigating a changing incident needs interaction, whereas a weekly capacity review needs a reproducible selection and time window.

Start with the question and output fields. For a production-VM review, useful columns might include VM name, cluster, configured resources, demand and the relevant contention measurement. Record units and aggregation so a reader can distinguish provisioned capacity from observed use. Avoid exporting every available metric without a purpose.

Create a List View

Create or clone a View in the installed release's content area. Give it an exam/lab-specific name and meaningful description, select the subject object type, then choose the supported presentation. A list presents objects as rows with data as columns; a distribution groups objects into categories; a trend presentation emphasizes changes over time. Do not confuse a heat-map dashboard widget with a guaranteed View type in every release.

1. Select the intended subject, such as Virtual Machine.
2. Choose the data fields and label their units clearly.
3. Configure transformations such as latest, average, maximum or sum where supported and appropriate.
4. Set filters and object scope using actual properties/groups.
5. Preview against known objects and a declared time range.
6. Compare at least one row with the object's detail view before saving.

A host metric cannot automatically be added to a VM row merely because both objects appear in the same inventory. Use supported relationships, aggregation and subject types. If a field is blank, verify its availability and collection rather than inventing a value.

Select the Right Transformation

Suppose a VM has hourly example CPU-demand observations of 1, 2, 3 and 10 GHz. Their arithmetic mean is 4 GHz and their maximum is 10 GHz. A report showing only the mean may hide a peak important to capacity planning. The sum, 16 GHz, is not a physically meaningful concurrent CPU requirement because the observations occurred at different times.

Likewise, summing a group of VM reservations answers a different question from averaging utilization percentages. Confirm the denominator and avoid averaging percentages across differently sized objects without considering weighting. State the transformation in the column title or report description so the next reader can reproduce the result.

Create the Report Template

Add the saved View and other supported report content to a report template. Arrange the order around the review question, choose applicable layout settings, and generate a preview. Reports support outputs such as PDF and CSV. A formatted PDF is useful for a meeting; a CSV is better for further calculation, but its units and filtering still need documentation.

Run the template against the intended scope, not an arbitrary selected inventory object. A report that looks correct against one small cluster can include unintended tenants when run from a parent datacenter. Check row counts, names, excluded objects and empty sections. Confirm that aggregation has not double-counted parent and child objects.

Schedule and Deliver

Create a supported recurrence and choose the target object/scope and output. Configure delivery through the supported email or storage mechanism and test it with an authorized recipient. Scheduling the report and configuring outbound transport are separate. An existing report file does not establish that a scheduled message was delivered.

Confirm timezone, execution time, retry/failure handling and retention. If collection is delayed, a report scheduled too soon after a batch run can contain incomplete data. Save the definition and generation timestamp alongside the report so later comparisons use equivalent inputs.

Sharing and Maintenance

Grant the required View/report permissions and object visibility to the intended users. Exporting a template does not automatically export live data, integrations or every custom definition on which it depends. After importing elsewhere, verify object types, field identifiers, groups and source accounts.

When a management pack or product version changes, recheck saved Views and reports with representative objects. A silent blank column is a content defect even when the document renders successfully. For this exam, demonstrate the whole chain: define the View, validate its data, assemble a report, run it for the correct scope and verify scheduled delivery. This is more useful than memorizing a menu path without knowing what its output measures.

Official Reading

Use the official 2V0-16.25 objective guide for scope and Broadcom technical documentation for the installed 9.0 component. This independent lesson was reviewed October 18, 2026; actual deployment support depends on the applicable version and configuration.

Review Takeaways

• Choose a View subject and presentation before selecting data fields and filters.
• Transformations such as average, latest and maximum answer different questions.
• A report template and its execution scope/time range determine the final evidence.
• Verify report generation and authorized delivery separately.