PMP-KR 문제 1011
프로젝트 계획 회의 중에 고객은 새로운 제품을 만드는 방법을 잘 모르고 추가 비용과 작업에 대해 걱정합니다.
고객이 프로젝트 관리자에게 지침을 요청하고 있습니다.
프로젝트 관리자는 무엇을 해야 하나요?
고객이 프로젝트 관리자에게 지침을 요청하고 있습니다.
프로젝트 관리자는 무엇을 해야 하나요?
정답: D
This answer is based on the concept of adaptive life cycle or agile project management, which is one of the approaches to managing projects in the PMBOK Guide1. Adaptive life cycle is suitable for projects that have high uncertainty, changing requirements, and complex or innovative products1. The main characteristics of adaptive life cycle are:
Delivering products in iterations or increments, each with a fixed duration and scope1.
Seeking frequent feedback from customers and stakeholders to validate the product value and quality1.
Embracing changes and responding to them quickly and effectively1.
Empowering the project team to make decisions and collaborate with each other1.
A minimum viable product (MVP) is a version of the product that has enough features to satisfy the initial needs of the customers and stakeholders, and to provide feedback for future development2. By focusing on releasing an MVP quickly, the project manager can:
Reduce the risk of wasting time and resources on building a product that does not meet the customer's expectations or needs2.
Increase the customer's satisfaction and engagement by involving them in the product development process2.
Learn from the feedback and data collected from the MVP and use them to improve the product in the next iteration2.
Adapt to the changing requirements and market conditions by delivering value incrementally2.
Therefore, option D is the best answer, as it aligns with the adaptive life cycle approach and the benefits of MVP. Option A is not a good answer, as it implies a predictive life cycle or waterfall project management, which is more suitable for projects that have low uncertainty, stable requirements, and well-defined products1. Waiting to start the project execution phase until all requirements and acceptance criteria are clear can result in:
Missing the opportunity to deliver value early and often to the customers and stakeholders1.
Increasing the risk of scope creep, change requests, and rework due to changing customer needs or expectations1.
Reducing the flexibility and responsiveness of the project team to adapt to changes1.
Limiting the collaboration and communication between the project team and the customers and stakeholders1.
Option B is also not a good answer, as it assumes that the customer knows all of the requirements at the beginning of the project, which is unlikely for a brand new product. Asking the customer to include all of the requirements in the project charter can lead to:
Creating a rigid and unrealistic scope that does not reflect the customer's actual needs or preferences3.
Overwhelming the customer and the project team with too many details and specifications that may not be relevant or necessary3.
Ignoring the feedback and learning opportunities that can arise during the project execution phase3.
Reducing the chances of innovation and creativity by restricting the product features and functions3.
Option C is a better answer than option A and B, as it involves the customer in the requirement elicitation process and prioritizes the most important requirements. However, it is still not the best answer, as it does not address the customer's concern about extra costs and work. Scheduling a brainstorming session and selecting the top ten most important requirements can still result in:
Spending too much time and resources on planning and analysis, instead of delivering value and testing assumptions.
Failing to validate the requirements with the end users and other stakeholders, who may have different needs or expectations.
Missing the opportunity to learn from the feedback and data collected from the product delivery and use.
Delaying the adaptation and improvement of the product based on the changing requirements and market conditions.
References:
1: A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Sixth Edition, Chapter 1 and
4, Project Management Institute, 2017. 2: The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses, Chapter 3 and 6, Eric Ries, 2011. 3: Software Requirements, Third Edition, Chapter 2 and 3, Karl Wiegers and Joy Beatty, 2013. : Agile Project Management with Scrum, Chapter 1 and 2, Ken Schwaber, 2004.
Delivering products in iterations or increments, each with a fixed duration and scope1.
Seeking frequent feedback from customers and stakeholders to validate the product value and quality1.
Embracing changes and responding to them quickly and effectively1.
Empowering the project team to make decisions and collaborate with each other1.
A minimum viable product (MVP) is a version of the product that has enough features to satisfy the initial needs of the customers and stakeholders, and to provide feedback for future development2. By focusing on releasing an MVP quickly, the project manager can:
Reduce the risk of wasting time and resources on building a product that does not meet the customer's expectations or needs2.
Increase the customer's satisfaction and engagement by involving them in the product development process2.
Learn from the feedback and data collected from the MVP and use them to improve the product in the next iteration2.
Adapt to the changing requirements and market conditions by delivering value incrementally2.
Therefore, option D is the best answer, as it aligns with the adaptive life cycle approach and the benefits of MVP. Option A is not a good answer, as it implies a predictive life cycle or waterfall project management, which is more suitable for projects that have low uncertainty, stable requirements, and well-defined products1. Waiting to start the project execution phase until all requirements and acceptance criteria are clear can result in:
Missing the opportunity to deliver value early and often to the customers and stakeholders1.
Increasing the risk of scope creep, change requests, and rework due to changing customer needs or expectations1.
Reducing the flexibility and responsiveness of the project team to adapt to changes1.
Limiting the collaboration and communication between the project team and the customers and stakeholders1.
Option B is also not a good answer, as it assumes that the customer knows all of the requirements at the beginning of the project, which is unlikely for a brand new product. Asking the customer to include all of the requirements in the project charter can lead to:
Creating a rigid and unrealistic scope that does not reflect the customer's actual needs or preferences3.
Overwhelming the customer and the project team with too many details and specifications that may not be relevant or necessary3.
Ignoring the feedback and learning opportunities that can arise during the project execution phase3.
Reducing the chances of innovation and creativity by restricting the product features and functions3.
Option C is a better answer than option A and B, as it involves the customer in the requirement elicitation process and prioritizes the most important requirements. However, it is still not the best answer, as it does not address the customer's concern about extra costs and work. Scheduling a brainstorming session and selecting the top ten most important requirements can still result in:
Spending too much time and resources on planning and analysis, instead of delivering value and testing assumptions.
Failing to validate the requirements with the end users and other stakeholders, who may have different needs or expectations.
Missing the opportunity to learn from the feedback and data collected from the product delivery and use.
Delaying the adaptation and improvement of the product based on the changing requirements and market conditions.
References:
1: A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Sixth Edition, Chapter 1 and
4, Project Management Institute, 2017. 2: The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses, Chapter 3 and 6, Eric Ries, 2011. 3: Software Requirements, Third Edition, Chapter 2 and 3, Karl Wiegers and Joy Beatty, 2013. : Agile Project Management with Scrum, Chapter 1 and 2, Ken Schwaber, 2004.
PMP-KR 문제 1012
프로젝트 관리자가 반복적 접근 방식을 사용하여 정부 소유 기업의 프로젝트를 관리하고 있습니다. 운영 환경에 대한 첫 번째 유용한 릴리스는 세 번의 반복으로 구성되었습니다. 각 반복은 테스트 환경에서 고객 담당자의 검토를 성공적으로 마쳤습니다. 그러나 팀이 운영 환경에 배포를 시작하자 보안팀에서 배포를 거부했습니다.
이런 일이 일어나는 것을 막기 위해 프로젝트 관리자는 무엇을 했어야 했을까?
이런 일이 일어나는 것을 막기 위해 프로젝트 관리자는 무엇을 했어야 했을까?
정답: B
To prevent the situation where the security team declined the deployment to the production environment, the project manager should have reviewed the compliance requirements with stakeholders. Here's why:
1.Compliance Requirements: Compliance requirements are essential for any project, especially in government- owned companies. These requirements ensure that the project adheres to legal, regulatory, and security standards. By reviewing compliance requirements early in the project, the project manager can identify any potential gaps or issues related to security.
2.Stakeholder Alignment: Engaging stakeholders, including the security team, during the planning phase allows the project manager to understand their expectations and concerns. It also provides an opportunity to address security-related matters proactively.
3.Risk Assessment: By reviewing compliance requirements, the project manager can assess potential risks related to security and take necessary actions. This includes implementing security measures, conducting vulnerability assessments, and ensuring that the project aligns with organizational security policies.
4.Iterative Approach: The iterative approach used in this project allows for incremental development and testing. However, security considerations should be part of each iteration. By involving stakeholders early and continuously, the project manager can address security concerns throughout the development process.
5.Communication: Regular communication with stakeholders ensures that everyone is on the same page regarding security expectations. It also helps in identifying any changes or updates to compliance requirements during the project lifecycle.
In summary, reviewing compliance requirements with stakeholders and addressing security concerns throughout the iterative process would have helped prevent the security team's decline during deployment to the production environment.
References:
*PMI, PMBOK Guide, 6th Edition, p. 357
*PMI, PMP Certification Exam Outline, p. 9
*Additional Reference: Asana - Understanding the Iterative Process
*Additional Reference: Monday.com - How to Use an Iterative Process for Projects
*Additional Reference: Asana - Understanding the Iterative Process
*Additional Reference: Monday.com - How to Use an Iterative Process for Projects
1.Compliance Requirements: Compliance requirements are essential for any project, especially in government- owned companies. These requirements ensure that the project adheres to legal, regulatory, and security standards. By reviewing compliance requirements early in the project, the project manager can identify any potential gaps or issues related to security.
2.Stakeholder Alignment: Engaging stakeholders, including the security team, during the planning phase allows the project manager to understand their expectations and concerns. It also provides an opportunity to address security-related matters proactively.
3.Risk Assessment: By reviewing compliance requirements, the project manager can assess potential risks related to security and take necessary actions. This includes implementing security measures, conducting vulnerability assessments, and ensuring that the project aligns with organizational security policies.
4.Iterative Approach: The iterative approach used in this project allows for incremental development and testing. However, security considerations should be part of each iteration. By involving stakeholders early and continuously, the project manager can address security concerns throughout the development process.
5.Communication: Regular communication with stakeholders ensures that everyone is on the same page regarding security expectations. It also helps in identifying any changes or updates to compliance requirements during the project lifecycle.
In summary, reviewing compliance requirements with stakeholders and addressing security concerns throughout the iterative process would have helped prevent the security team's decline during deployment to the production environment.
References:
*PMI, PMBOK Guide, 6th Edition, p. 357
*PMI, PMP Certification Exam Outline, p. 9
*Additional Reference: Asana - Understanding the Iterative Process
*Additional Reference: Monday.com - How to Use an Iterative Process for Projects
*Additional Reference: Asana - Understanding the Iterative Process
*Additional Reference: Monday.com - How to Use an Iterative Process for Projects
PMP-KR 문제 1013
프로젝트 관리자가 프로젝트 현장에서 납품을 수락했지만 품목의 품질이 좋지 않습니다. 프로젝트 관리자는 현지 공급업체에 품목 수정을 요청했지만 이 공급업체로부터 더 많은 납품이 예상됩니다.
프로젝트 관리자는 앞으로 무엇을 해야 할까요?
프로젝트 관리자는 앞으로 무엇을 해야 할까요?
정답: C
According to the PMBOK Guide, 7th edition, one of the key activities in the monitoring and controlling phase of a project is to control quality by verifying that the project deliverables conform to the quality standards and requirements. This involves inspecting and testing the deliverables, reviewing the quality documentation, and requesting corrective actions if needed. The other options are either inefficient, ineffective, or not aligned with the quality management principles. References: PMBOK Guide, 7th edition, page 123-124, section 3.5.2.1.
PMP-KR 문제 1014
회사는 범위 관리 계획에 정의된 대로 특정 구성 요소의 개발을 위해 예측 접근 방식을 사용하고 있습니다. 정기적으로 변경되는 규제 요구 사항으로 인해 개발 팀은 민첩한 접근 방식을 활용하도록 요청했습니다.
개발팀의 요청에 대해 프로젝트 관리자는 어떻게 해야 하나요?
개발팀의 요청에 대해 프로젝트 관리자는 어떻게 해야 하나요?
정답: D
According to the PMBOK Guide, the project manager should consider the project delivery approach (predictive, agile, or hybrid) based on the project characteristics, such as complexity, uncertainty, stability, and adaptability. The project manager should also evaluate the impact of any changes to the project delivery approach on the project scope, schedule, cost, quality, risk, and stakeholder satisfaction. Therefore, the project manager should analyze the requirements that will need to be addressed under the agile approach and determine the feasibility, benefits, and drawbacks of switching from the predictive approach. This will help the project manager to make an informed decision and communicate it to the relevant stakeholders. References: PMBOK Guide, 6th edition, pages 19-20, 141-142.
PMP-KR 문제 1015
프로젝트 관리자는 신제품 개발 프로젝트를 이끌고 있습니다. 법무팀 담당자가 프로젝트 팀에 접근하여 제품 출시 전에 법률 검토를 거쳐야 한다고 요청했습니다. 이 검토로 인해 일정이 길어지고 중요한 출시 시기를 놓칠 수 있다는 것입니다.
프로젝트 관리자는 무엇을 해야 할까요?
프로젝트 관리자는 무엇을 해야 할까요?
정답: D
The correct answer is D because the scenario requires disciplined compliance and quality governance rather than an immediate, informal, or purely administrative reaction. The selected response - D. Request a cost- benefit analysis of launching to market considering the legal review addition. - directly addresses the condition described in the question and keeps the project aligned with authorized objectives. PMBOK-aligned practice requires the project manager to verify mandatory requirements, analyze impact, and prevent uncontrolled delivery decisions that could create audit or acceptance exposure. This is especially important when project constraints, stakeholder expectations, quality expectations, delivery cadence, or business value may be affected. The competing options are weaker because they either bypass the accountable role, defer action without analysis, escalate before the project manager has prepared decision-quality information, or solve a symptom without correcting the underlying process issue. The selected answer also preserves transparency, ownership, and traceability, which are essential for sound project governance and effective delivery. PMBOK Guide Eighth Edition topics: process, compliance and quality governance, stakeholder communication, impact analysis, governance, value delivery, and continuous improvement.
- 다른 버전
- 5139PMI.PMP-KR.v2026-08-21.q86
- 796PMI.PMP-KR.v2026-08-21.q927
- 7582PMI.PMP-KR.v2026-06-01.q1069
- 6022PMI.PMP-KR.v2026-05-07.q925
- 1585PMI.PMP-KR.v2026-03-28.q242
- 4797PMI.PMP-KR.v2026-03-27.q939
- 5158PMI.PMP-KR.v2026-03-09.q911
- 5038PMI.PMP-KR.v2026-03-07.q681
- 5568PMI.PMP-KR.v2026-03-05.q857
- 3080PMI.PMP-KR.v2026-03-04.q280
- 5439PMI.PMP-KR.v2025-03-29.q751
- 5400PMI.PMP-KR.v2024-02-27.q469
- 1572PMI.PMP-KR.v2024-02-10.q164
- 3585PMI.PMP-KR.v2023-12-04.q235
- 1454PMI.PMP-KR.v2023-10-19.q177
- 2477PMI.PMP-KR.v2023-05-15.q244
- 최근 업로드
- 117Microsoft.DP-300.v2026-08-28.q542
- 124Workday.Workday-Pro-Absence.v2026-08-28.q36
- 160ACAMS.CAMS.v2026-08-28.q850
- 155Microsoft.DP-420-KR.v2026-08-28.q136
- 208Microsoft.AZ-500-KR.v2026-08-28.q246
- 337PMI.PMP-KR.v2026-08-27.q1110
- 250ISACA.CISA-KR.v2026-08-27.q676
- 142Workday.Workday-Procure-to-Pay.v2026-08-26.q20
- 247Microsoft.DP-300-KR.v2026-08-26.q212
- 287EC-COUNCIL.312-49.v2026-08-25.q265
[×]
PDF 파일 다운로드
메일 주소를 입력하시고 다운로드 하세요. PMI.PMP-KR.v2026-08-27.q1110 모의시험 시험자료를 다운 받으세요.