Which Table Ownership Ties Records to a Business Unit?
Short answer
D Choose user or team owned so each record inherits an owning business unit and the table shows all scope levels in the security role designer.
Question
You must create a new table to support a new feature for an app. Records for the table must be associated with a business unit. The table must be visible when specifying a security role. You need to configure table ownership. Which table ownership type should you use?
Key Takeaways
You must satisfy two constraints at once — records tied to a business unit and the table visible in the security role designer — and the trap is choosing the option that merely contains the word 'business' even though business-owned is not a Dataverse ownership type.
This Dataverse question tests table ownership types and how they affect business unit association and security role configuration. It establishes that only user or team owned tables link each record to an owning business unit while still appearing with full scope options in a security role.
Common mistake: Choosing C (business-owned) because the question stresses business unit association; Dataverse has no business-owned ownership type, and organization-owned records carry no owning business unit at all.
Expert Analysis
Why the Answer Is Correct
Dataverse exposes only three ownership values — Organization, User or Team, and None — and only user or team ownership stamps every record with an owning business unit inherited from its owner. That satisfies the first requirement directly: each record is associated with a business unit. It also satisfies the second: user/team-owned tables appear in the security role designer with all four scope columns — User, Business Unit, Parent: Child Business Units, and Organization. Organization-owned tables expose only the Organization scope, and None-owned tables are excluded from security roles entirely. Therefore user or team owned (D) is the only type that meets both stated conditions.Why the Other Options Are Wrong
Organization-owned (A) records live at the organization level and have no owning business unit column value, so they fail the first requirement even though they technically appear in a security role. None (B) removes the table from security role configuration altogether, directly violating the visibility requirement. Business-owned (C) is not a valid Dataverse ownership type at all — the ownership enum contains only None, Organization, and User/Team — so it cannot be selected when configuring the table. Option C exists purely as a distractor that plays on the phrase 'associated with a business unit'.Community Comment Notes
The single comment, from exam_upskill, asserts "C. business-owned" with one like, but that ownership type does not exist in Dataverse, so the claim cannot be verified against the platform. Learners reasoning from the phrase 'associated with a business unit' tend to gravitate toward the word 'business' without checking the actual ownership enum. The requirements are only jointly satisfiable by user or team ownership, which links records to the owner's business unit and keeps every scope level available in the security role designer. Community votes here should not override the documented ownership model.Official Reference
Exam Strategy
When a question bundles two requirements, test each option against both instead of matching keywords — 'business unit' points to user/team ownership, not a 'business-owned' type. Also memorize the real Dataverse ownership enum (None, Organization, User/Team) so you instantly reject options that are not selectable values.
Frequently Asked Questions
Why doesn't organization-owned ownership work if the table still appears in a security role?
Organization-owned tables do appear in security roles, but their records carry no owning business unit, so the business unit requirement fails.
Is business-owned a real Dataverse table ownership type?
No. Dataverse supports only Organization, User or Team, and None ownership; business units group users, teams, and records rather than owning tables.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded.
From public community threads 1
-
exam_upskill 👍 1 Answered CC. business-owned
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.