A data governance team is building a metadata repository for a new Salesforce implementation. They need to capture the business definition of 'Active Customer' and also record the underlying Salesforce object and field names that store this data. Which combination of metadata types should they capture?

Only technical metadata, since the system stores the data

Only business metadata, since the definition is what matters for governance

Business metadata for the definition and technical metadata for the object/field names

Technical metadata for the definition and business metadata for the object/field names

A healthcare organization must comply with data protection regulations. They need to classify data assets by sensitivity and ensure that only authorized users can access sensitive data. They also need to document the classification decisions. What should they do?

Use only technical metadata to avoid over-classifying

Apply sensitivity labels and store classification metadata in the catalog with audit trails

Create a business glossary instead of sensitivity labels

Rely on the database security settings without documenting classifications

A data team needs to capture metadata for a new data warehouse. They have a limited budget and need to prioritize capturing lineage and data quality information. Which technique is most efficient for this?

Hiring consultants to document all metadata

Using only the data dictionary provided by the database

Manual annotation of every table and column

Automated profiling and lineage extraction using data catalog tools

A company is building a business glossary. They have stakeholders from finance, sales, and operations who use different terms for the same concept. They want to ensure that all stakeholders can find the terms they use. What is the best approach?

Use only the most common term and ignore others

Create a single canonical term and add synonyms from each department

Avoid a glossary and rely on data dictionaries

Create separate glossaries for each department

SalesforceCertified Data Architect

Domain 4Objective 1

Compare and Contrast Various Techniques, Approaches and Considerations for Capturing and Managing Business and Technical Metadata (e.g., Business Dictionary, Data Lineage, Taxonomy, Data Classification). DATA-ARCHITECT Practice Questions (Page 2)

Part of the METADATA MANAGEMENT domain, which accounts for 7% of the DATA-ARCHITECT exam.

35questions here

7free pages

8concepts

7%of the exam

8 Concepts in This Objective

Business metadata vs technical metadata
Business dictionary and glossary
Data lineage
Taxonomy
Data classification
Techniques for capturing metadata
Approaches for managing metadata
Considerations for metadata management

Questions 6–10

6application · medium
A data architect is documenting the data flow for a Salesforce integration. They need to record the source object, the target object, and the transformation rules. Which type of metadata is this?
Select an answer first
7application · medium
A data governance team is building a metadata repository for a new Salesforce implementation. They need to capture the business definition of 'Active Customer' and also record the underlying Salesforce object and field names that store this data. Which combination of metadata types should they capture?
Select an answer first
8expert · hard
A healthcare organization must comply with data protection regulations. They need to classify data assets by sensitivity and ensure that only authorized users can access sensitive data. They also need to document the classification decisions. What should they do?
Select an answer first
9application · medium
A data team needs to capture metadata for a new data warehouse. They have a limited budget and need to prioritize capturing lineage and data quality information. Which technique is most efficient for this?
Select an answer first
10expert · hard
A company is building a business glossary. They have stakeholders from finance, sales, and operations who use different terms for the same concept. They want to ensure that all stakeholders can find the terms they use. What is the best approach?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to DATA-ARCHITECT

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Salesforce. “DATA-ARCHITECT” is a trademark of its owner, used for identification only.

Compare and Contrast Various Techniques, Approaches and Considerations for Capturing and Managing Business and Technical Metadata (e.g., Business Dictionary, Data Lineage, Taxonomy, Data Classification). DATA-ARCHITECT Practice Questions (Page 2)

Questions 6–10

A data architect is documenting the data flow for a Salesforce integration. They need to record the source object, the target object, and the transformation rules. Which type of metadata is this?

A healthcare organization must comply with data protection regulations. They need to classify data assets by sensitivity and ensure that only authorized users can access sensitive data. They also need to document the classification decisions. What should they do?

A data team needs to capture metadata for a new data warehouse. They have a limited budget and need to prioritize capturing lineage and data quality information. Which technique is most efficient for this?

A company is building a business glossary. They have stakeholders from finance, sales, and operations who use different terms for the same concept. They want to ensure that all stakeholders can find the terms they use. What is the best approach?

Keep studying — METADATA MANAGEMENT