[2025年10月]更新のPeoplecert DevOps-Foundation問題集厳選された問題集でパスして、最短時間を目指そう
Peoplecert DevOps-Foundation試験問題集で[2025年最新] 練習 高合格率な試験問題集問題
Peoplecert DevOps-Foundation 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
| トピック 6 |
|
| トピック 7 |
|
質問 # 33
Which statement about DevOps toolchains is CORRECT? They:
- A. Should be standardized across applications
- B. Require open source tools
- C. Automate tasks in a deployment pipeline
- D. Automate continuous testing activities
正解：C
解説：
ADevOps toolchainis designed toautomate repetitive tasksacross the software delivery process. This includes compiling code, running tests, building artifacts, deploying to environments, and monitoring systems.
While a toolchaincanautomate continuous testing (D), that is only one of many tasks automated.
Standardization (B) is beneficial but not always required-some applications may need specialized tools.
Open source tools (C) are not mandatory; many organizations use a mix of open source and proprietary tools.
Therefore,A-automation of tasks in a deployment pipeline-is the most universally correct statement.
References:
PeopleCert DevOps Foundation v3.6 - DevOps Toolchain Definition
The DevOps Handbook- Deployment Pipeline Automation
質問 # 34
Which of the following are benefits of automation?
- A. Decreased security and risk mitigation
- B. Fewer errors and slower lead time
- C. Higher quality and faster recovery
- D. More frequent and turbulent releases
正解：C
解説：
Automationbrings multiple key benefits in DevOps:
* Higher quality:Automated tests and deployments catch errors earlier, reduce human error, and ensure consistency.
* Faster recovery:Automated monitoring and remediation help restore services quickly after incidents.
* Other options either decrease quality, increase errors, or make releases less predictable-contradicting DevOps goals.
Extract-style reference:
"Automation reduces errors, increases quality, accelerates lead time, and shortens recovery by ensuring repeatable, reliable processes."
-DevOps Handbook
PeopleCert DevOps Foundation v3.6:Automation is a pillar of DevOps, referenced throughout the syllabus as a key driver for speed and reliability.
質問 # 35
Which of the following dictates an organization's culture?
- A. Employees' commitment and loyalty to the company
- B. What people value and how they behave
- C. The vision of its founders
- D. The leadership style of its executives
正解：B
解説：
Organizational culture is defined byshared values and behaviors-what people believe is important and how they act in practice. PeopleCert notes that while founders' vision, leadership style, and employee commitment can influence culture, the actual culture is visible in the consistent behaviors and priorities of the organization' s members.
Therefore,B-what people value and how they behave-is the most accurate description of what dictates culture.
References:
PeopleCert DevOps Foundation v3.6 - Culture Definition
Edgar Schein -Organizational Culture and Leadership
質問 # 36
Which of the following does NOT make DevOps important now?
- A. Time to value must accelerate
- B. Enterprises have young, nimble start-up competitors
- C. IT must continue to operate in a silo culture
- D. Consumers have "app" mentalities and expectations
正解：C
解説：
The urgency for DevOps adoption is driven by increasing market competition, evolving customer expectations, and the need for rapid delivery of value.
* B: Nimble start-ups often deliver faster and more innovatively, putting pressure on established enterprises.
* C: Customers expect continuous improvement and seamless digital experiences ("app mentality").
* D: Reducing time-to-value is essential for staying competitive and meeting business demands.
However,Adescribes a siloed culture-something DevOps actively works to eliminate, not a reason for its importance. In fact, remaining siloed is an obstacle to achieving DevOps benefits, not a driver for adoption.
Therefore,Ais the correct "NOT" choice.
References:
PeopleCert DevOps Foundation v3.6 - Business Drivers Section
Accelerate- Market Forces and Organizational Response
The DevOps Handbook- Culture and Collaboration Principles
質問 # 37
Why are feedback loops important for improving DevOps capabilities?
- A. Trust grows
- B. Sharing is prevented
- C. Information is not amplified
- D. They drive more unplanned work
正解：A
解説：
In the PeopleCert DevOps framework, feedback loops are essential for creatingtrustbetween teams. When feedback is timely, accurate, and acted upon, teams see that issues are addressed quickly, leading to increased confidence in the process and in each other.
High-trust environments promote openness, knowledge sharing, and collaborative problem-solving. This encourages teams to raise issues early and experiment with improvements without fear of blame.
OptionsA,B, andDdescribe negative effects that actually occur when feedback loops areabsentor ineffective.
Well-designed loops reduce unplanned work, promote sharing, and amplify important information to the right people.
Therefore,C-trust grows-is the correct answer.
References:
PeopleCert DevOps Foundation v3.6 - Culture and Feedback Principles
The DevOps Handbook- Psychological Safety and Blameless Culture
Accelerate- Correlation Between Culture, Trust, and Performance
質問 # 38
Regardless of structure, what should a DevOps team NOT be?
- A. Flat
- B. Isolated
- C. Continuously engaged
- D. Balanced in terms of people and automation skills
正解：B
解説：
A core goal of DevOps is toeliminate isolationbetween roles, teams, and departments. Isolated teams-cut off from other parts of the value stream-create bottlenecks, reduce visibility, and slow feedback.
While flat hierarchies (A), continuous engagement (C), and balanced skills (D) are positive traits,Bis the opposite of DevOps principles.
Therefore,Bis the correct "NOT" choice.
References:
PeopleCert DevOps Foundation v3.6 - Anti-Patterns in Team Design
Accelerate- Effects of Silos on Performance
質問 # 39
An organization has identified they have a culture of blame where people are fearful of failure and lack the courage to try new things.
What can they do to encourage more courageous and experimentational behaviors?
- A. Build rituals that reward risk taking
- B. Sharing is inhibited
- C. Both b and c
- D. Identify and punish the people that make mistakes
正解：A
解説：
Ablame cultureis toxic and inhibits innovation. DevOps encourages a culture where risk-taking and experimentation are rewarded, not punished.
Organizations should "build rituals that reward risk taking"-examples include celebrating "fast failures" and running blameless post-mortems.
Extract-style reference:
"Encourage a culture where failure is seen as a learning opportunity, not a cause for punishment. Rituals that reward risk-taking foster innovation and create psychological safety."
-DevOps Handbook
DevOps Foundation v3.6 (Cultural Principles section) advocates psychological safety, learning from failure, and reward systems that incentivize experimentation.
質問 # 40
Which of the following tools measure a person's behavioral choices in situations where they are experiencing disagreement with their colleagues?
- A. Value Stream Mapping
- B. Thomas-Kilmann Conflict Mode Instrument
- C. Kubler Ross Change Curve
- D. Westrum's Typology of Organizational Culture
正解：B
解説：
TheThomas-Kilmann Conflict Mode Instrument (TKI)is a psychometric tool that measures an individual's behavior in conflict situations-specifically, how they handle disagreement with colleagues.
* It classifies responses into five modes: Competing, Collaborating, Compromising, Avoiding, and Accommodating.
Why not the others?
* Kubler Ross Change Curve:Describes emotional responses to change, not conflict styles.
* Westrum's Typology:Categorizes organizational culture (pathological, bureaucratic, generative) but doesn't measure individual behavior.
* Value Stream Mapping:A process improvement tool, not a behavioral assessment.
Reference/Extract:
"The Thomas-Kilmann instrument helps teams understand how individuals approach conflict and collaboration, enabling better resolution strategies-a key aspect of high-performing DevOps teams."
-DevOps Handbook; PeopleCert DevOps Foundation v3.6 Section 3.7
質問 # 41
The goal of which role is the creation of ultra-scalable and highly reliable software systems?
- A. Site resilience engineer
- B. Software engineer
- C. Product Owner
- D. Site reliability engineer
正解：D
解説：
TheSite Reliability Engineer (SRE)role originated at Google and is now widely recognized. SREs apply software engineering principles to IT operations to create systems that arescalable, reliable, and highly available. Their responsibilities include:
* Designing reliability into systems (SLIs, SLOs, SLAs)
* Automating operational tasks to reduce toil
* Building monitoring and alerting systems
* Performing capacity planning and disaster recovery exercises
A(Site resilience engineer) is not a standard industry term.C(Software engineer) focuses on developing applications but not specifically on operational reliability.D(Product Owner) is a role in Agile frameworks that manages product backlog and priorities, not system reliability.
Thus, the correct answer isB - Site Reliability Engineer.
References:
PeopleCert DevOps Foundation v3.6 - Roles in DevOps
Google SRE Book - Principles and Practices
質問 # 42
Which of the following DevOps practices encourages conversation driven development, delivery and support?
- A. Communication Platforms
- B. VisOps
- C. The Second Way
- D. ChatOps
正解：D
質問 # 43
What is one of the PRIMARY benefits of Continuous Delivery?
- A. It ensures that all releases are deployed into production in a timely manner
- B. It automates all of the tasks associated with development and operations
- C. It reduces the cost, time, and risk of delivering incremental changes to the business
- D. It prioritizes working on new features over keeping software deployable
正解：C
解説：
Continuous Delivery's primary benefit is that itreduces the cost, time, and risk of delivering incremental changes. By keeping software deployable at all times, teams can ship small, low-risk releases as needed.
* A:Prioritizing features over deployability increases risk.
* B:Not all releases are deployed immediately; CD keeps themready.
* D:CD doesn't automate everything-some manual steps may remain, especially in Continuous Delivery (vs. Continuous Deployment).
Extract-style reference:
"Continuous Delivery reduces deployment pain by ensuring that code is always in a deployable state, decreasing the cost, time, and risk associated with releases."
-Continuous Delivery, Jez Humble & David Farley
PeopleCert Syllabus: Highlights CD as a strategy for safer, more efficient business change.
質問 # 44
Which framework ensures that ITSM processes are designed with just enough control and structure in order to effectively and efficiently deliver services that facilitate customer outcomes when and how they are needed?
- A. DevOps
- B. Agile Service Management
- C. COBIT
- D. ITIL
正解：B
解説：
Agile Service Management (Agile SM)applies Agile principles to the design and improvement of IT Service Management (ITSM) processes. Its goal is to create processes that arelightweight, adaptable, and customer- focused, ensuring they provide just enough control to meet objectives without creating unnecessary bureaucracy.
This framework helps align ITSM practices with the speed and flexibility required in a DevOps environment, ensuring that services can be delivered in a timely, efficient, and outcome-focused manner.
A(ITIL) provides a comprehensive ITSM framework but is not inherently Agile.B(COBIT) focuses on governance rather than process agility.D(DevOps) is a cultural and technical movement, not specifically a framework for ITSM process design.
Thus,Cis correct.
References:
PeopleCert DevOps Foundation v3.6 - Agile Service Management Section
Agile Service Management Guide- ITSM Process Agility Principles
質問 # 45
Which of the following DevOps practices encourages conversation driven development, delivery and support?
- A. Communication Platforms
- B. VisOps
- C. The Second Way
- D. ChatOps
正解：D
解説：
ChatOpsis the DevOps practice of using chat platforms (like Slack, Teams, Mattermost) as the central interface for communication, collaboration, and even automated deployment or support tasks.
It encourages "conversation-driven development, delivery, and support," making processes transparent and collaborative.
* Second Way(A) is about feedback loops, but not specifically conversational platforms.
* Communication Platforms(C) is a generic term.
* VisOps(D) is not a standard DevOps term.
Extract-style reference:
"ChatOps is a collaboration model that connects people, tools, process, and automation into a transparent workflow. Teams communicate and execute commands from a central chat client."
-DevOps Handbook
PeopleCert Foundation v3.6: ChatOps promotes rapid feedback and a culture of sharing.
質問 # 46
Which of the following is NOT a crucial ingredient when leading a digital transformation?
- A. Curiosity
- B. Courage
- C. Command
- D. Collaboration
正解：C
解説：
Command(authoritarianism) is not a crucial ingredient for leading digital transformation.
The key ingredients:
* Collaboration
* Curiosity
* Courage
DevOps leadership is about empowering teams, experimenting, and driving change,notcommand-and-control.
Extract-style reference:
"Digital transformation leaders embrace collaboration, curiosity, and courage, fostering an environment where experimentation and learning drive change."
-Accelerate,DevOps Handbook
PeopleCert DevOps Foundation v3.6:Advocates servant and transformational leadership, not command
/control.
質問 # 47
Why is organizational culture so critical to successful DevOps?
- A. It represents the way automation will be introduced into their organization
- B. It represents the strategic direction of the organization
- C. It represents the way teams are organized in their work environment
- D. It represents the way people think and behave in their work environment
正解：D
解説：
In DevOps,culturerefers to the shared values, beliefs, and behaviors that influence how people work together.
PeopleCert highlights culture as the foundation for collaboration, trust, and open communication-critical for breaking down silos and enabling continuous delivery.
OptionAbest captures this definition: culture reflects theway people think and behavein their daily work, including attitudes toward experimentation, problem-solving, and collaboration.
While team structure (B), automation strategy (C), and strategic direction (D) are important, they are outcomes or enablers that depend on the underlying culture. Without the right cultural foundation, DevOps practices and tools will not achieve their full potential.
References:
PeopleCert DevOps Foundation v3.6 - CALMS: Culture
Accelerate- Culture's Link to Performance
質問 # 48
Which statement about deployment success rate is CORRECT?
- A. Applies only to production
- B. May apply to multiple environments, not just production
- C. Is the same as change success rate
- D. Is used to measure application reliability and stability
正解：B
解説：
Deployment success ratemeasures the proportion of deployments that meet their objectives without causing incidents, rollbacks, or degraded service. PeopleCert notes this metric is not limited to production-it can be applied to any environment where deployments occur (staging, testing, pre-prod).
Ais incorrect because focusing only on production misses valuable insights from earlier environments.Cis partially correct-success rate can inform reliability-but reliability is more broadly measured with other metrics like availability and MTTR.Dis incorrect becausechange success ratetypically includes all changes, not just deployments.
Therefore,Bis the accurate statement.
References:
PeopleCert DevOps Foundation v3.6 - Metrics and Measurement
Accelerate- Deployment Metrics
質問 # 49
Which of The Three Ways increases the flow of work from left to right?
- A. The Second Way
- B. The Third Way
- C. The First Way
- D. All of the above
正解：C
解説：
The "Three Ways" are foundational principles in DevOps:
* The First Wayfocuses on increasing the flow of work from left (development) to right (operations). It is about optimizing the entire system for fast delivery, limiting bottlenecks, and enabling a rapid flow of features and fixes to customers.
* The Second Wayis about amplifying feedback loops so corrections can be made early.
* The Third Wayemphasizes continual learning and experimentation.
Extract-style reference:
"The First Way emphasizes the performance of the entire system, as opposed to the performance of a specific silo of work or department. The goal is to maximize the flow of work (value) from Development to Operations to the customer."
-Gene Kim, The Phoenix Project / DevOps Handbook
PeopleCert DevOps Foundation v3.6highlights this in the section on "Principles and Practices," emphasizing The First Way as critical to accelerating flow.
質問 # 50
What are the CORRECT set of DevOps values?
- A. Culture, Automation, Lean, Metrics, Sharing
- B. Culture, Collaboration, Communication, Commitment
- C. Culture, Automation, Lean, Measurement, Sharing
- D. Culture, Accountability, Lean, Metrics, Sharing
正解：C
解説：
According to PeopleCert DevOps Foundation v3.6, the five primary values that guide successful DevOps adoption are summarized in theCALMSframework:Culture, Automation, Lean, Measurement, and Sharing.
* Culturefocuses on breaking down silos, encouraging trust, and promoting collaboration between development, operations, security, QA, and business teams.
* Automationis essential for speeding up delivery, reducing manual errors, and ensuring repeatability across the software delivery lifecycle.
* Leanemphasizes the elimination of waste, limiting work in progress (WIP), and improving flow.
* Measurementmeans using metrics and data to inform decisions, identify bottlenecks, and drive continuous improvement.
* Sharingfosters transparency, knowledge transfer, and a unified approach to goals and problem-solving.
Option A replaces automation and lean principles with softer collaboration aspects, which are important but not recognized as the formal value set. Option C replaces "Measurement" with "Metrics," which is only a part of measurement. Option D substitutes "Accountability" for "Automation," which is not part of the CALMS model.
Therefore, the official correct set of values per the DevOps Foundation syllabus isB.
References:
PeopleCert DevOps Foundation v3.6 - Core Values Section (CALMS)
The DevOps Handbook, Gene Kim et al. - Part I: The Three Ways
Accelerate, Forsgren, Humble, Kim - Chapter on Culture and Capabilities
質問 # 51
Which Lean tool provides a collaborative board that makes work visible, allows work in progress to be limited, and optimizes flow?
- A. Value Stream Mapping
- B. Continuous Delivery
- C. Improvement Kata
- D. Kanban
正解：D
解説：
Kanbanis a Lean visual management method that helps teams control and improve workflow. The board displays tasks in columns representing process stages, enabling:
* Visualization of work items and bottlenecks
* Limiting work in progress (WIP) to improve flow and reduce multitasking
* Tracking throughput and cycle time for continuous improvement
B(Value Stream Mapping) is a Lean analysis tool, not a visual board for ongoing work.C(Improvement Kata) is a structured improvement method, andD(Continuous Delivery) is a software delivery practice, not a visual workflow tool.
Therefore,A-Kanban-is correct.
References:
PeopleCert DevOps Foundation v3.6 - Lean Tools and Kanban
Kanbanby David J. Anderson - Principles and Practices
質問 # 52
An organization is finding that defects found in production had frequently already been identified and recorded in testing and staging and sometimes, although they optimized performance locally, they caused global degradation. Upon further inspection, it was found that this was happening because the testing phase was often delayed due to constraints around resource availability, impacting the flow of work from left to right.
Which of The Three Ways should they took to for direction on how to resolve the situation?
- A. The Second Way
- B. The Third Way
- C. The First Way
- D. Continuous Experimentation and Learning
正解：C
解説：
When work is delayed due to resource availability or local optimizations causing global degradation, the issue relates toThe First Way-maximizing flow from left to right.
Organizations should analyze and remove bottlenecks in the delivery pipeline (e.g., in testing).
Extract-style reference:
"Optimizing the flow of work requires eliminating bottlenecks, delays, and handoffs that slow the movement of changes from development to operations."
-The Phoenix Project
DevOps Foundation courseware discusses value stream mapping and the First Way as critical tools for diagnosing and correcting such issues.
質問 # 53
Which of the following is NOT a characteristic of DevOps?
- A. Fast flow of unplanned work into production
- B. World-class stability, reliability, availability and security
- C. Ensuring overall organizational success
- D. Working towards a common goal
正解：A
解説：
A fast flow ofunplanned workinto production isnota characteristic of DevOps. In fact, DevOps practices strive to minimize unplanned work (like emergency changes or outages) through automation, testing, collaboration, and rigorous change control. The other options-ensuring organizational success, working toward a common goal, and world-class stability/reliability-are all key DevOps characteristics.
Reference:DevOps Foundation v3.6 syllabus section 1.4; State of DevOps Report.
質問 # 54
Which of the following is NOT a benefit of using a Kanban board?
- A. It reduces work in progress
- B. It enables people to work collaboratively
- C. It defines policies and procedures
- D. It reduces idle time and waste
正解：C
解説：
Kanban boards are visual management tools used to track work and manage flow. They provide transparency, limit work in progress (WIP), and help teams focus on delivering value quickly.
* A: Reducing WIP is a key Kanban principle that improves flow and delivery speed.
* C: Visibility fosters collaboration and shared ownership.
* D: By identifying bottlenecks and waste, Kanban helps reduce idle time.
B-defining policies and procedures-is not an inherent benefit of Kanban. While teams may display existing policies on a Kanban board, the board itself does not define them. Its role is to visualize work and flow, not to establish governance rules.
Thus,Bis the correct "NOT" benefit.
References:
PeopleCert DevOps Foundation v3.6 - Lean and Kanban Practices
Kanbanby David J. Anderson - Benefits and Principles
質問 # 55
A major retail organization is experiencing declining sales and wants to boost its online business. Teams within Dev and Ops have been independently experimenting with DevOps practices to speed up changes to the company's website but have yet to see tangible benefits.
What can the IT management team do in this situation to achieve bottom-line benefits with DevOps?
- A. Create a shared vision, goals and incentives
- B. Encourage intelligent risk taking
- C. Build a high-trust culture
- D. Promote a customer (outside-in) focus
正解：A
解説：
When independent Dev and Ops teams adopt DevOps practices without coordination, results are limited.
* The most important action IT management can take is tocreate a shared vision, goals, and incentives.
* Shared goals align everyone to business outcomes, reduce conflicting priorities, and foster real collaboration.
Why not the others?
* Intelligent risk taking(A) andhigh-trust culture(C) are important, but without a shared vision, teams won't move in the same direction.
* Customer focus(D) is essential, but won't create cross-team alignment by itself.
Reference/Extract:
"Creating a shared vision and goals across Dev and Ops is critical to breaking down silos and delivering end- to-end value to the business."
-The Phoenix Project,Accelerate, and PeopleCert DevOps Foundation v3.6 Section 3.3
質問 # 56
......
DevOps-Foundation試験問題集でPDF合格保証 成功は正確かつ更新された問題：https://www.goshiken.com/Peoplecert/DevOps-Foundation-mondaishu.html
DevOps-Foundation問題集-[最新2025]Peoplecert試験問題集を掴み取れ：https://drive.google.com/open?id=13Xled_5NNtpxogpPi2EbCE1VuvCBb8oQ