Portfolio level NFRs apply to ...?

• A. A single ART
• B. The system under test
• C. All ARTs
• D. The product owner team

Answer: (C)

Portfolio level nonfunctional requirements represent enterprise-wide quality attributes that must be satisfied by the entire solution, not just a single part. Because a SAFe portfolio combines multiple value streams and multiple Agile Release Trains, these NFRs set expectations that cut across all ARTs and guide architectural decisions, integration, and the overall solution’s behavior. They ensure that every ART contributes to the same performance, security, reliability, regulatory compliance, and maintainability standards, so the final integrated system meets the enterprise goals. That’s why portfolio-level NFRs apply to all ARTs — they are the cross-cutting constraints that shape the whole portfolio’s delivery, not just one team or a single system component. For example, a portfolio-wide NFR on data privacy would require consistent access controls and data handling practices across every ART delivering parts of the solution.