Scaled Agile Framework (SAFe) Architect Practice Test

In the context of ensuring that inter-Agile Release Train (ART) dependencies are visible after Program Increment (PI) Planning, the most appropriate action is to update the Solution board. The Solution board serves as a visual tool that captures and communicates the progress of the solution, including dependencies across different ARTs involved in a solution delivery.

By updating the Solution board, the Solution Architect ensures that all stakeholders have a clear view of how various teams and trains are interconnected, their current status, and how dependencies may affect their work. This transparency is critical for effective collaboration and helps in managing risks associated with those dependencies.

The Solution board not only showcases the dependencies but can also highlight any critical paths and timelines, making it an essential artifact in cross-ART coordination. This visibility aids in maintaining alignment across the trains as the work progresses through the PI.

The other choices, while they may serve important roles in the ART and solution hierarchy, do not focus on the immediate need to visualize inter-ART dependencies in the same way the Solution board does. The program board is more focused on a single ART, the Solution Intent is about the overarching architectural intent, and the Solution Backlog deals with prioritizing work items and features instead of visualizing dependencies. Hence, updating