Courseiva
Data Governance →mediumMultiple Choice

SF-Data-Arch Data Governance Practice Question

A multinational manufacturer runs a single Salesforce org for sales and service. Its governance team wants to enforce that all new custom objects created in production carry a business owner, a retention classification, and a data sensitivity label. Administrators frequently create objects ad hoc, and the team wants an automated check rather than a manual review. Which approach should the data architect recommend?

⚠ Common exam trap

The trap here is assuming record-level validation rules or change-request workflows can enforce metadata standards, when only metadata-aware tooling can inspect object definitions.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Use Metadata API and Apex Metadata API to scan object definitions against a governance checklist and block deployment when required attributes are missing.

Metadata-level governance requires inspecting object definitions, which only metadata-aware tooling can do. A programmatic check using Metadata API and Apex Metadata API lets the team compare each object against required attributes such as owner, retention classification, and sensitivity label, and it can fail the deployment automatically. Manual workflows and record-level rules cannot assert anything about the object definition itself.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Enable Field Audit Trail and Field History Tracking on all custom objects to capture who created each object.

    Why it's wrong here

    Field Audit Trail and Field History Tracking record changes to field values on records, not the creation of object metadata. They provide forensic history after the fact and cannot block an object from being deployed without a business owner or sensitivity label. They answer who changed what data, not whether an object definition meets a governance standard.

  • ✗

    Build a custom validation rule on each custom object that checks the owner field is populated on records.

    Why it's wrong here

    Validation rules operate on record data, not on object metadata. They cannot assert that a new object definition itself carries a business owner, retention class, or sensitivity label. A validation rule could enforce a required field on records of an object, but it cannot prevent an object from being created without the governance attributes the team requires.

  • ✓

    Use Metadata API and Apex Metadata API to scan object definitions against a governance checklist and block deployment when required attributes are missing.

    Why this is correct

    Metadata API exposes object definitions, including custom fields, descriptions, and custom metadata values, so a governance service can programmatically evaluate every object against the required attributes. Apex Metadata API allows the check to run inside Salesforce and to fail a deployment or raise an alert. This gives the automated, metadata-level enforcement the governance team asked for.

  • ✗

    Require every administrator to submit a change request through a ServiceNow workflow before creating a custom object.

    Why it's wrong here

    A change-request workflow is process control, not platform enforcement. It relies on humans remembering to file and reviewers catching omissions, and it does not automatically read object metadata such as retention classification or sensitivity label. It also adds latency to every deployment. The requirement is for an automated check on the object definition itself, which this external workflow does not provide.

About these practice questions

One of 222 original SF-Data-Arch practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Salesforce exam blueprint

This SF-Data-Arch practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Data-Arch exam.