How do you know which components are supported in source tracking?

How do you know which components are supported in source tracking?

• A. Metadata Coverage Dashboard
• B. Metadata Coverage Report
• C. Code Review Log
• D. Package Manifest

Answer: (B)

In source tracking, you need a clear view of which metadata types can be managed through your version-controlled workflow. The Metadata Coverage Report provides that exact view: it lists each metadata type and shows whether it is fully supported, partially supported, or not supported by source tracking. This lets you quickly identify which components you can reliably track with your DX project and scratch org setup, and where you’ll need to rely on other deployment methods. The dashboard might give a high-level summary, but the report gives the per-type details you need. A Code Review Log isn’t about tracking metadata changes, and a Package Manifest simply specifies what to deploy or retrieve, not which components are compatible with source tracking.

In source tracking, you need a clear view of which metadata types can be managed through your version-controlled workflow. The Metadata Coverage Report provides that exact view: it lists each metadata type and shows whether it is fully supported, partially supported, or not supported by source tracking. This lets you quickly identify which components you can reliably track with your DX project and scratch org setup, and where you’ll need to rely on other deployment methods. The dashboard might give a high-level summary, but the report gives the per-type details you need. A Code Review Log isn’t about tracking metadata changes, and a Package Manifest simply specifies what to deploy or retrieve, not which components are compatible with source tracking.