In privately scoped applications, which statement about table access is true?

In privately scoped applications, which statement about table access is true?

• A. All application scopes can read from the table
• B. Only the owning scope can read from the table
• C. Administrators can read any table
• D. The table is accessible to external apps only

Answer: (A)

Cross-scope data access in privately scoped apps is designed so that tables within a private scope can be read by code in other application scopes, as long as the relevant ACLs allow it. The key idea is that the data plane is shared across scopes, enabling reading across apps even though the code and definitions live in separate scopes. This means a table created in a privately scoped application can be read by other application scopes unless an ACL explicitly denies it, while write access remains more tightly controlled. In practice, you would still secure sensitive data with ACLs and roles, but the default behavior supports cross-scope read access for privately scoped tables.

Cross-scope data access in privately scoped apps is designed so that tables within a private scope can be read by code in other application scopes, as long as the relevant ACLs allow it. The key idea is that the data plane is shared across scopes, enabling reading across apps even though the code and definitions live in separate scopes. This means a table created in a privately scoped application can be read by other application scopes unless an ACL explicitly denies it, while write access remains more tightly controlled.

In practice, you would still secure sensitive data with ACLs and roles, but the default behavior supports cross-scope read access for privately scoped tables.