This PRINCE2F practice question tests your understanding of prince2 processes. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
What is the difference between Starting Up a Project and Initiating a Project?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Starting Up a Project is done before the Project Board authorizes initiation; Initiating a Project follows that authorization
Starting Up a Project is a pre-project process to check viability before committing resources, while Initiating a Project formally establishes the project with detailed plans and management strategies.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Starting Up a Project produces the PID; Initiating a Project produces the Project Brief
Why it's wrong here
This is reversed: SU produces the Project Brief; IP produces the PID.
✗
There is no difference; they are the same process
Why it's wrong here
They are distinct processes with different purposes.
✗
Starting Up a Project is done by the Project Board; Initiating a Project is done by the Project Manager
Why it's wrong here
The Project Board is not involved in the day-to-day of SU; the Executive and PM are appointed in SU.
✓
Starting Up a Project is done before the Project Board authorizes initiation; Initiating a Project follows that authorization
Why this is correct
SU is a pre-project process to decide whether to initiate; IP is the first stage after initiation is authorized.
Related concept
Authentication checks who the user is.
Common exam traps
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
Authentication checks who the user is.
Authorization controls what the user is allowed to do after login.
Privilege levels affect access to EXEC and configuration commands.
AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
→Do not assume successful login means full administrative access.
→Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
→Separate login problems from permission problems before choosing the answer.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Real-world example
How this comes up in practice
A junior network technician can log in to a core router but cannot reach the enable prompt or configuration mode. The AAA server is authenticating the login — but the authorisation policy only grants privilege level 1, not 15. Authentication (who you are) is working; authorisation (what you can do) is not.
What to study next
Got this wrong? Here's your next step.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related PRINCE2F questions on access control and AAA configuration.
PRINCE2 Processes — This question tests PRINCE2 Processes — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Starting Up a Project is done before the Project Board authorizes initiation; Initiating a Project follows that authorization — Starting Up a Project is a pre-project process to check viability before committing resources, while Initiating a Project formally establishes the project with detailed plans and management strategies.
What should I do if I get this PRINCE2F question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related PRINCE2F questions on access control and AAA configuration.
What is the key concept behind this question?
Authentication checks who the user is.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This PRINCE2F practice question is part of Courseiva's free PeopleCert certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PRINCE2F exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.