Exam PK0-005 topic 1 question 18 discussion

internal doesn't have to be mandatory, but in this case, it has to be mandatory.

internal doesn't have to be mandatory, but in this case, it has to be mandatory.

C. Mandatory. In The Official CompTIA Project+ Guide (PK0-005), mandatory dependencies (also known as hard logic) are those that are legally or contractually required or inherent to the nature of the work. In this case, the software installation can only begin after the desktops have been installed and powered on, which is a logical or physical constraint—this sequence is a necessary condition for the project to proceed.

Per AI source... B. Internal. Internal dependencies are those that are within the control of the project team, such as the sequence of tasks. In this case, the installation of desktops before software installation is an internal sequence that the project team manages.

It is internal: Hard logic dependencies are also known as mandatory dependencies. These dependencies are usually legally or contractually required. They can also be directed by company procedures or physical limitations. Internal dependencies are dependencies between tasks or activities within the project. They involve a precedence relationship between project activities.

Mandatory. It can't be circumvented. The software can only be installed when the system is powered on.

I would agree with B based on the definitions and wording of the question. With internal dependencies, that points to how one task depends on another being completed within the project scope. Mandatory is an absolute no other way hard requirement in the order of tasks. It is true that the software has to come after the system installations and powered on, but it does not absolutely have to be the next step. They could do install > powered on > install peripherals > install software for example. This example would fit internal and not mandatory, and the question does not state that is HAS to be done after the installation, only that it can only begin after that step.

It is B, as we need to break the question and given answer sets down. If internal was not offered in the list, then Mandatory would be the answer. But, since both classification types of Internal and External were offered, the question is looking for a more specific answer. As Mandatory can be applied to either Internal or External, it's not the best/specific answer, hence the "trip up" here. Mandatory is not wrong, but its not the most detailed way to describe this scenario. We aim for the most detailed classification, so we can find a solution more quickly, regardless if the problem is holding the project up or not. Mandatory would only convey the severity on how soon we need to address it.

Internal dependencies are dependencies that occur within the project team or organization. For example, a task can only begin after a team member has completed a training course. Mandatory dependencies are dependencies that are required for the project to be completed. For example, a task can only begin after a new piece of equipment has been delivered. These are very similar in this scenario. A dependency can be both internal and mandatory

Agree with C

Mandatory dependency - is unavoidable. Can often arise because of natural order (example: a user cannot create a password until they first access the site) - pg. 250 - "The Official CompTIA Project+ Guide (PK0-005)"