Maintenance metrics are not consistently calculated across related rows.

A custom prompt is the native low-code mechanism for generating an inspection report from current app data while following the company’s existing template instructions. The maker can define inputs for the inspection fields, specify required sections, tone, order, and formatting, and invoke the prompt from the new app. This keeps the report-generation experience within Power Platform and minimizes custom AI development. A paginated report is well suited to deterministic, pixel-precise reporting, but it does not perform the requested generative composition and generally presents a separate reporting artifact. A Word template performs deterministic field substitution and is useful when no generative rewriting is required; it does not supply the AI-driven custom narrative described in the case. The prompt should be grounded only with approved inspection data, tested for missing inputs, and reviewed for output consistency before production use. The Study Guide covers “build prompts,” “add inputs to a prompt,” and “consume a prompt in apps.” Option C is therefore the component that directly implements native generative inspection-report creation.

Study Guide reference/topic: “Create prompts and models in AI Hub — Consume a prompt in apps.” AB-410 Study Guide | Microsoft Learn technical reference