高品質Scaled Agile SAFe-SPC模擬試験最新版 & 公認されたJpexam - 認定試験のリーダー誰でも給料が高いのを希望します。でも、給料が高いかどうかはあなたの価値次第です。SAFe-SPC認証試験に合格したら、自分の価値を高めることができます。我々Jpexamの問題集は全面的で質量の高いですから、受験生としてのあなたに一番ふさわしいです。我々の資料を利用したら、あなたはSAFe-SPC試験に合格することができます。 Scaled Agile SAFe Practice Consultant SPC (6.0) 認定 SAFe-SPC 試験問題 (Q78-Q83):質問 # 78
(Select 3) Which of the following have acceptance criteria?
A. Business Capabilities
B. Program Epics
C. Strategic Themes
D. Enabler Features
E. Portfolio Enabler Epics
F. Spikes
正解：A、B、D
解説：
A). Business Capabilities: In SAFe, Capabilities (including Business Capabilities) are large solution behaviors that have acceptance criteria to ensure they are fully defined and testable.
D). Enabler Features: All Features, including Enabler Features, require acceptance criteria to clarify when the Feature is done.
F). Program Epics: Epics require acceptance criteria to define the conditions for completion and evaluation.
Portfolio Enabler Epics (B) have a higher-level definition and are not typically assigned granular acceptance criteria. Strategic Themes (C) and Spikes (E) do not have acceptance criteria; Spikes are research items.
References:
SAFe 6.0 Website: Features and Capabilities
SPC 6.0 Guide: "Each Feature, Capability, and Epic should have clear acceptance criteria."
質問 # 79
SAFe is a dual-operating system for Business Agility. What is one element of the dual-operating system?
A. Value Stream Network
B. A Lean portfolio
C. Agile Teams
D. Solution Context
正解：A
解説：
SAFe 6.0 describes the dual-operating system as "combining the existing hierarchical structure with a second operating system that is organized around value streams and Agile Release Trains." The Value Stream Network is a key element of this dual-operating system, allowing organizations to deliver value quickly and efficiently while maintaining stability in their functional hierarchy.
References:
SAFe 6.0, "Business Agility" article
SPC 6.0 Study Guide, "Thriving in the Digital Age and Business Agility" section
質問 # 80
What are the primary responsibilities of Program Portfolio Management (PPM)?
A. Program management, stakeholder management, PI Planning.
B. Lightweight business case, Epic specification workshop, Budget allocation.
C. Governance, investment funding, product strategy.
D. Governance, strategy and investment funding, program management.
正解：D
解説：
Program Portfolio Management (now commonly referred to as Lean Portfolio Management in SAFe 6.0) is accountable for:
Strategy and Investment Funding: Ensuring the portfolio's investments align with the enterprise's business strategy.
Agile Portfolio Operations (Program Management): Supporting program execution, including coordination and support across value streams.
Governance: Assuring compliance, monitoring progress, and evaluating outcomes.
SAFe 6.0 documentation emphasizes these three pillars as the core responsibilities of LPM/PPM.
Option D omits program management, while B and C list activities or deliverables but not the full scope of responsibilities.
References:
SAFe 6.0 Website: Lean Portfolio Management
SPC 6.0 Guide: "Strategy and Investment Funding, Agile Portfolio Operations, and Lean Governance are the primary responsibilities of Lean Portfolio Management."
質問 # 81
Which process is used for Epics to accelerate learning and development and reduce risk?
A. Defining non-functional requirements (NFRs)
B. Creating a Lean business case
C. Using the SAFe Lean Startup cycle
D. Applying weighted shortest job first (WSJF)
正解：C
解説：
SAFe recommends the Lean Startup cycle for managing Epics. This process accelerates learning, guides hypothesis-driven development, and reduces risk by enabling incremental evaluation and fast feedback before full investment in new business ideas.
References:
SAFe 6.0, "Epic" and "Lean Startup Cycle" articles
SPC 6.0 Guide, "Building Solutions with Agile Product Delivery"
質問 # 82
Which basic Agile quality practice ensures consistent quality measures for each work product?
A. Pairing and peer-review
B. Workflow automation
C. Standards and Definition of Done
D. Collective ownership
正解：C
解説：
The "Definition of Done" and established quality standards are basic Agile practices that ensure every work product meets agreed-upon quality criteria before it is considered complete. This approach drives consistency, transparency, and reliable outcomes across teams and ARTs.
References:
SAFe 6.0, "Built-In Quality" article
SPC 6.0 Practice Guide, "Establishing Team and Technical Agility"