[2026年02月] SAFe-SPC 問題集完全版解答 SAFe Practice Consultant 試験学習ガイド [Q59-Q75]

Share

[2026年02月]更新のSAFe-SPC問題集完全版解答でSAFe Practice Consultant試験学習ガイド

試験問題と解答SAFe-SPC学習ガイド


Scaled Agile SAFe-SPC 認定試験の出題範囲:

トピック出題範囲
トピック 1
  • トレーニングとチームコーチング
  • ART とバリューストリームのさらなる立ち上げ
トピック 2
  • デジタル時代の繁栄
  • ビジネス敏捷性のためのコアコンピテンシー
トピック 3
  • 顧客中心主義とデザイン思考
  • デジタル時代の成功とビジネスの俊敏性
トピック 4
  • 多機能アジャイルチーム
  • 組み込み品質
トピック 5
  • ビジネスアジリティのためのオペレーティング システムとしての SAFe®
  • リーン アジャイル リーダーになる
トピック 6
  • ARTバックログの優先順位付け
  • アジャイル製品配信によるソリューションの構築
トピック 7
  • 継続的な学習の文化の構築
  • 組織の俊敏性の確立
トピック 8
  • ケイデンスに基づいた開発。オンデマンドリリース
  • チームと技術の俊敏性の確立

 

質問 # 59
What is NOT a SAFE-recommended Metric?

  • A. Number of defects outstanding.
  • B. Percent of unit test coverage.
  • C. Percent of user stories accepted by the Product Owner.
  • D. Number of lines of code produced.
  • E. Number of new test cases automated.
  • F. Number of test cases produced.

正解:D


質問 # 60
Phase-gate Milestones are not a good predictor of project performance.

  • A. True
  • B. False

正解:A


質問 # 61
Vikas is a new Solution Architect and is trying to understand the Solution Context. What is the most important factor for him to consider?

  • A. The acceptance criteria for the Capabilities.
  • B. Job sequencing for the Epics in the Value Stream Backlog.
  • C. The environment in which the Solution is deployed.
  • D. The Economic Framework for the Value Stream.

正解:C

解説:
The Solution Context defines the environment in which the solution operates, including operational, regulatory, deployment, and support conditions. For a Solution Architect, understanding this environment is essential to ensure the solution will function as required in its real-world context.
References:
SAFe 6.0 Website: Solution Context
SPC 6.0 Guide: "Solution Context describes the environment in which the solution operates."


質問 # 62
You are invited to help an Agile Release Train that has struggled through multiple PIs. They just finished the second Iteration in the current PI and have nothing to demonstrate at the System Demo. Program stakeholders are really concerned.
What would you do?

  • A. Re-plan the current PI: De-scope to leave enough time to integrate what you've built during the IP Iteration.
  • B. Have every team demonstrate their team increment to the stakeholders separately in the team branch.
  • C. Stop working on any new functionality and fully integrate and test the system; adjust scope based on learnings.
  • D. Find a vendor that specializes in integrating system increments from multiple teams.
  • E. Re-architect the system so that there are no dependencies between the teams and integration is not needed.

正解:C

解説:
When the ART cannot show integrated value at the System Demo, it indicates that teams are not continuously integrating and testing, leading to lack of transparency and feedback. SAFe emphasizes continuous integration and working, tested systems at every iteration. The best immediate action is to stop new work and focus on integrating and testing what has been built, learning from this to improve future practices. This will help restore trust with stakeholders and reveal root causes for future improvements.
"When the system is not integrated, the team should stop developing new functionality and invest in integration and testing. This enables learning, ensures stakeholder visibility, and helps restore the regular cadence of System Demos." (Source: SAFe 6.0 Framework: System Demo, Continuous Integration; SPC 6.0 Guide, "Coaching ART Execution")


質問 # 63
(Select 3) What are three ways to coordinate across Value Streams?

  • A. Apply cadence and synchronization.
  • B. Establish Enterprise architecture.
  • C. Create a Portfolio Vision and Roadmap.
  • D. Fund the Portfolio, not the Value Streams.
  • E. Move teams across Value Streams to respond to changing business demands.
  • F. Empower the Value Stream Engineer to coordinate all teams in the Value Stream.

正解:A、B、C


質問 # 64
What are the SAFe Core Values that typically resonate with executives when talking about SAFe?

  • A. Empowerment, self-managing teams, decentralization of control, value.
  • B. Built-in Quality, cadence, synchronization, trust.
  • C. Lean Leadership, Built-in Quality, Agile Architecture, product flow.
  • D. Built-in Quality, program execution, alignment, transparency.

正解:D

解説:
SAFe defines four Core Values: Alignment, Built-in Quality, Transparency, and Program Execution. These values help executives understand the framework's foundation and address concerns about consistent delivery, quality, trust, and business alignment.
"SAFe's four core values are: Alignment, Built-in Quality, Transparency, and Program Execution." (Source: SAFe 6.0 Framework: Core Values; SPC 6.0 Guide, "Becoming a Lean-Agile Leader")


質問 # 65
You are invited to help an Agile Release Train that has struggled through multiple PIs. They just finished the
second Iteration in the current PI and have nothing to demonstrate at the System Demo. Program stakeholders
are really concerned.
What would you do?

  • A. Find a vendor that specializes in integrating system increments form multiple teams.
  • B. Have every team demonstrate their team increment to the stakeholders separately in the team branch.
  • C. Stop working on any new functionality and fully integrate and test the system; adjust scope based on
    learnings.
  • D. Re-plan the current PI: De-scope to leave enough time to integrate what you've built during the IP
    Iteration.
  • E. Re-architect the system so that there are no dependencies between the teams and integration is not needed.

正解:C


質問 # 66
Which of the following is a Lean Thinking Principle?

  • A. Identify the Value Stream for each product
  • B. Simplicity is essential
  • C. Agile processes promote sustainable development
  • D. Deliver working software frequently

正解:A

解説:
"Identify the Value Stream for each product" is directly referenced as one of the Lean Thinking Principles in SAFe. This principle comes from Lean and underpins the SAFe emphasis on organizing around value and optimizing the flow from concept to delivery. The other choices are derived from Agile Manifesto principles, not Lean Thinking.
References:
SAFe 6.0, "Lean-Agile Mindset" and "Lean Thinking" articles
SPC 6.0 Guide, "Becoming a Lean-Agile Leader"


質問 # 67
What is the SAFe calculation for Weighted Shortest Job First?

  • A. (User/Business Value + Size + Risk Reduction/Opportunity Enablement)/Job Size.
  • B. (Risk Reduction/Opportunity Enablement + Time Criticality + Size)/Business Value.
  • C. (User/Business Value + Size + Risk Reduction/Opportunity Enablement)/Time.
  • D. (User/Business Value + Time Criticality + Opportunity Enablement/Risk Reduction)/Job Size.

正解:D


質問 # 68
What is the purpose of Solution Intent?

  • A. Create a comprehensive design document for approval before development begins.
  • B. Record and communicate the necessary requirements and design decisions.
  • C. Provide an up-front and static definition of the system's design.

正解:B


質問 # 69
Which process is used for Epics to accelerate learning and development and reduce risk?

  • A. Creating a Lean business case
  • B. Applying weighted shortest job first (WSJF)
  • C. Using the SAFe Lean Startup cycle
  • D. Defining non-functional requirements (NFRs)

正解: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"


質問 # 70
The teams on the ART just finished the second Iteration in the PI and have nothing to demonstrate at the System Demo. What steps should be taken next?

  • A. Stop working on any new functionality and fully integrate and test the system; adjust scope based on learnings
  • B. Re-architect the system so that there are no dependencies between the teams, and integration is not needed
  • C. Continue to work on new functionality and reserve time to fully integrate the system during the IP Iteration.
  • D. Require every team to demonstrate their team increment to the stakeholders separately in the team branch

正解:A

解説:
SAFe recommends immediately integrating and testing the system when there is nothing to demonstrate, rather than continuing with new work. This helps surface integration issues early and allows for scope adjustment based on the learnings, supporting the principle of "integrating frequently" and "demonstrating working software." References:
SAFe 6.0, "System Demo" and "PI Execution" articles
SPC 6.0 Guide, "Coaching ART Execution"


質問 # 71
What role would a traditional program manager most likely take on in SAFe?

  • A. Release Train Engineer or Value Stream Engineer.
  • B. Scrum master
  • C. Product Manager
  • D. Business Owner

正解:A


質問 # 72
(Select 2) When might Feature size not be a good substitute for the duration of WSJF?

  • A. The Feature involves a team or team members who represent a bottleneck.
  • B. The Feature has not yet been broken down into user stories by the Product Owner.
  • C. The Feature did not originate from a Value Stream Capability.
  • D. The Feature involves a remote third-party vendor that has a formal scope-approval process.
  • E. The Feature did not originate from a Program Epic.

正解:A、D

解説:
WSJF (Weighted Shortest Job First) uses job size or duration as the denominator to prioritize work. SAFe often uses feature size (story points) as a proxy for duration. However, this is not always accurate:
B: If a Feature involves a team or member who is a bottleneck, the actual duration may be longer than estimated by size, due to limited availability.
D: If a Feature depends on a remote third-party vendor with formal approval processes, duration may be impacted by external delays not reflected in the feature's size.
Options A, C, and E do not directly impact the suitability of size as a proxy for duration.
References:
SAFe 6.0 Website: WSJF
SPC 6.0 Guide: "Use feature size as a proxy for duration unless bottlenecks or dependencies (e.g., with external vendors) distort that relationship."


質問 # 73
(Select 2) What steps in the Portfolio Kanban are most appropriate for running research spikes?

  • A. Portfolio Backlog-run a spike before pulling into development.
  • B. Funnel-understand whether the Epic makes sense.
  • C. Implementing-teams perform spikes as usual
  • D. Analysis-spikes help clarify feasibility.

正解:B、D

解説:
A: During the Analysis step, research spikes (time-boxed investigations) are used to clarify feasibility, identify unknowns, and gather data for decision making.
C: In the Funnel step, early research or spikes help determine if the Epic is even worth advancing, especially for innovations or high-risk items.
Portfolio Backlog (D) is for items already accepted for future implementation; it's generally too late for basic research spikes. Implementing (B) is for execution, not discovery.
References:
SAFe 6.0 Website: Portfolio Kanban
SPC 6.0 Guide: "Spikes are often run during the Funnel and Analysis steps to clarify scope, feasibility, and business case."


質問 # 74
Velocity is a good measure of team performance.

  • A. False
  • B. True

正解:A


質問 # 75
......

SAFe Practice Consultant SPC (6.0)無料で更新される100%試験高合格率保証:https://jp.fast2test.com/SAFe-SPC-premium-file.html

リアル試験問題と解答でScaled Agile SAFe-SPC問題集はここにある:https://drive.google.com/open?id=1SA3U7spmNYLsQW5QQ3NEUY7mg7KiNSsq


弊社を連絡する

我々は12時間以内ですべてのお問い合わせを答えます。

我々の働いている時間: ( GMT 0:00-15:00 )
月曜日から土曜日まで

サポート: 現在連絡 

English Deutsch 繁体中文 한국어