What is the baseline behavior of a table in a privately scoped application?

What is the baseline behavior of a table in a privately scoped application?

• A. All application scopes can read from the table
• B. Only the owning scope can read from the table
• C. The table is readable only by administrators
• D. The table is read-only in the private scope

Answer: (A)

In a privately scoped application, the main idea is that code and metadata are isolated to the owning scope, but data in a table is readable across all application scopes by default. This means any application scope can read from that table, which allows cross-scope usage like reporting or referencing data in other apps, while write access remains controlled by ACLs and the owning scope. So the baseline behavior is that all application scopes can read from the table, not just the owner or admins, and not that it’s read-only within the private scope.

In a privately scoped application, the main idea is that code and metadata are isolated to the owning scope, but data in a table is readable across all application scopes by default. This means any application scope can read from that table, which allows cross-scope usage like reporting or referencing data in other apps, while write access remains controlled by ACLs and the owning scope. So the baseline behavior is that all application scopes can read from the table, not just the owner or admins, and not that it’s read-only within the private scope.