In the recommended approach for permissions across related objects, where should related objects and their writeback datasets be placed?

• A. In separate projects
• B. In the same project
• C. In external storage
• D. In the code repository

Answer: (B)

Permissions are governed at the project level, so related objects that interact and their writeback datasets should live in the same project. This keeps a single, coherent set of access rules for both the objects and the writebacks, making it easy to grant, audit, and maintain the necessary permissions. If you place them in separate projects, you’d have to duplicate and synchronize permissions across projects, which can lead to gaps, blocked writes, or unintended access. External storage or a code repository doesn’t align with Foundry’s permission governance and lineage for datasets and their writebacks, so they’re not suitable for maintaining consistent access controls across related objects. Keeping everything in one project ensures governance is straightforward and access remains consistent.