CompTIA Project+ Certification - (PK0-005) Exam Questions

OBJ 1.7: Smoke testing is a high-level system test that confirms that the main features of the software are working before detailed testing is conducted. It helps detect flawed builds early, saving time and effort. Unit testing is a software testing approach that involves testing the smallest functional unit or component of software to ensure that it functions as expected. It works well with modular coding approaches and is usually automated to save time and money. Regression testing is a testing technique that involves running existing tests after a code change to ensure that the change does not affect any existing functionality. Performance testing Performance testing is a testing approach that evaluates the system's stability and speed under various workloads. It measures the expected conditions and evaluates the system's performance under normal usage scenarios. For support or reporting issues, include Question ID: 64a5c444880e767450f00e8f in your ticket. Thank you.

OBJ 2.4: A breach of contract occurs when one party fails to fulfill the terms and conditions specified in the agreement. In vendor management, this happens when the vendor does not provide services as agreed upon, leading to non-compliance with the service level expectations detailed in the contract. The organization may respond by enforcing penalties or seeking legal resolution to address the breach and ensure the contract's terms are upheld. Unlike a Non-Disclosure Agreement (NDA), which is designed to protect sensitive information, a breach of contract pertains specifically to service standards. Rules of Engagement (ROEs) provide guidelines for specific activities and do not address a vendor's failure. Service Level Agreements (SLAs) set service levels and expectations but do not describe a vendor's failure to meet them. For support or reporting issues, include Question ID: 64c29c7b71a5f84f324e85a7 in your ticket. Thank you.

OBJ 2.3: The asset turnover plan is the part of the transition plan in which the team strategizes how equipment and resources will be moved from the project team to the maintenance team. The maintenance schedule is the part of the transition plan that indicates what activities are needed to ensure the work of the project continues. Activities is part of the transition plan, which lists all of the tasks needed during the handoff. Roles and responsibilities are part of the transition plan that ensure everyone involved in the transition knows who owns the overall plan and who will be in charge of each of the transition activities and the maintenance activities. For support or reporting issues, include Question ID: 64c170ad2e60209dbaac2202 in your ticket. Thank you.

OBJ 1.11: Buying is the best option here. Buying a resource involves transferring ownership from the seller to you and usually requires a higher up-front cost but slower ongoing costs. For example, if you decide to buy that same 'end-of-days' bunker, you would pay a higher initial cost if you paid for it in full or smaller initial costs if you financed it with a loan, but you would be responsible for ongoing maintenance and fuel expenses. While more expensive up front, the length of time they plan to use the software means buying is more cost-effective than leasing and subscribing. Building isn't a good option since the software they are buying does everything they want it to do. For support or reporting issues, include Question ID: 6689608c0780878b7c4596e5 in your ticket. Thank you.

OBJ 2.1: To calculate Return on Investment (ROI), you can use the following formula: ROI = ((Total Revenue - Total Cost) / Total Cost) x 100 In this case: Total Revenue = $120,000 (additional revenue generated by the marketing campaign) Total Cost = $50,000 (investment in the marketing campaign) ROI = (($120,000 - $50,000) / $50,000) x 100 ROI = ($70,000 / $50,000) x 100 ROI = 1.4 x 100 = 140% So, the ROI for the marketing campaign is 140% For support or reporting issues, include Question ID: 64b98aa81faf34908821118a in your ticket. Thank you.

OBJ 1.9: Meeting minutes can track discussions, decisions, and action items in meetings. They can be quite valuable as reference after the meeting because they summarize what took place and can be easily reviewed later. Time boxes limit the meeting or its parts to a specific time frame. This helps decisions get made and reduces the amount of time wasted, making meetings more efficient. Action items are tasks that somebody will complete after the meeting. They should be added to a list so they can be tracked. By creating a list and focusing on action items as tasks to be done later, it is less likely that people will try to complete the task during the meeting. Follow-ups provide additional information and recap information. They are sent out after the meeting to reinforce decisions made or provide information that wasn't included in the meeting. For support or reporting issues, include Question ID: 64b588a27291b6126a5fdeb1 in your ticket. Thank you.

OBJ 2.2: Units of work result from the project being decomposed into small units, which can be completed in the sprint or other chosen work periods. They are defined during the planning phase. Establishing accepted communication channels and developing the RAM (Responsibility Assignment Matrix) are completed during the initiation phase. Planning the next steps takes place during the closing phase. For support or reporting issues, include Question ID: 64c54a852a3ecf8bc080ba22 in your ticket. Thank you.

OBJ 2.3: Lessons learned from older projects will likely provide the most benefit. Artifacts are documents created throughout a project's lifespan. As the project manager, Jonah will already be familiar with the current RAM (Responsibility Assignment Matrix) and the business case for the current project. Competitors' software manuals aren't likely to provide as much insight into the current project as lessons that were learned from other projects at the same company. For support or reporting issues, include Question ID: 649201f9cf035e4cc2829fb7 in your ticket. Thank you.

OBJ 3.1: Issue logs track events that are occurring that are outside of the team’s control. Keeping these logs helps to organize and prioritize the list of issues, focusing on the highest-priority items as it may not be possible to address everything. Each issue is recorded with a description, the date found, and the person who found it. The list is then prioritized, and a plan is developed to address each issue. The log includes a number that identifies the issue, the description, impact, who found it, who will address it, and statuses so the issue can be tracked. The snowstorm isn't in the team's control, but this issue may still cause delays. Defect logs record any situation in which the product doesn’t meet the requirements. Defects are usually found during testing and after release. The log should provide enough information for the engineer to research, recreate, and resolve the defect and become a sort of work list for the team moving forward. Defects should be prioritized and evaluated so that the most important or impactful defects are addressed first. The list includes the number that identifies the defect, the description, how it is reproduced, the priority, who found it, who will address it, and statuses so the defect can be tracked. Change log: record all situations in which activities performed during the project deviate from its original plan. This includes alterations that are requested, the addition of new features, and unplanned alterations. The log includes a number that identifies the change, the description, the type of request, the impact, who requested it, who will address it, and statuses so the change can be tracked. The change may not be required, so recording the issue in the change log isn't appropriate yet. A timeline contains events that are going to happen, and no one yet knows if the delay will happen. For support or reporting issues, include Question ID: 64c81e3559261fd94983921c in your ticket. Thank you.

OBJ 4.5: The test environment is the tier of software architecture where the beta version of the code is put before developers and even sample users to help find and resolve issues before launch. The development environment is the tier of software architecture where code is written, changed, and adjusted. The production environment is the tier of software architecture where the software can be deployed. It is in this tier that the real end users have access to the software. The live environment exists after the release of the software. For support or reporting issues, include Question ID: 64cfc9b15d755db34ffc02ea in your ticket. Thank you.