“150”, Aptitude Test Questions and Answers for ICT Officer II (Project Management) – e-GA.
ABSTRACT
This aptitude test preparation guide
contains 150 premium multiple-choice questions and answers designed for
candidates preparing for the ICT Officer Grade II (Project Management) position
at the e-Government Authority (e-GA), Tanzania. The questions focus on
practical understanding of ICT project management, business and systems
analysis, requirements engineering, software development, quality assurance,
business process re-engineering, risk management, stakeholder engagement,
project governance, e-Government implementation, monitoring and evaluation, and
organizational change. Developed around realistic public-sector scenarios, the
questions emphasize critical thinking, professional judgment, and the ability
to distinguish closely related alternatives, reflecting the demanding nature of
online aptitude assessments.
Prepared by: ICT Officer II (Project Management)
– e-GA.
Compiled by ICT Officer II (Project Management)
– e-GA.
0628729934.
Date: September 10, 2026
Dear applicants,
This collection of questions and answers
has been prepared to help all of you to understand the key areas tested during
the interview. The goal is to provide a useful, and practical study guide so
you can all perform confidently and fairly in the selection process. I wish you
the best of luck, and may this resource support you in achieving success!
Warm regards,
ICT Officer II (Project Management)
For Personal Use by Applicants Preparing
for ICT Officer II (Project Management) - at Public Service Recruitment
Service.
ICT OFFICER II
(Project Management) – e-GA
150 Aptitude
Test Questions and Answers
1. An e-Government project is six weeks into
implementation when the business owner requests an additional workflow that was
not included in the approved requirements. The development team says the change
is technically simple and can be completed without changing the delivery date.
What should the ICT Officer recommend FIRST?
A. Authorize the
change because it has no technical complexity
B. Ask developers to implement it before project documentation changes
C. Assess the change through the established change-control process
D. Reject the change because approved requirements cannot be modified
Answer: C
Rationale: The appropriate first action is to
subject the requested change to the established change-control process. Even a
technically simple modification can affect scope, testing, security,
documentation, dependencies, resources, acceptance criteria, or future support.
The fact that developers believe it can be delivered within the existing
schedule does not remove the need for controlled assessment and approval.
Rejecting every change would be unnecessarily rigid, while implementing it
immediately would undermine project governance and traceability.
2. During review of a proposed government
application, the business unit states that the system must “process
applications quickly.” The development team interprets this as a response time
of 10 seconds, while the business unit expected applications to be processed
within two seconds. What is the MOST appropriate action by the ICT
Officer?
A. Allow
developers to select a reasonable performance threshold
B. Convert the business statement into an agreed measurable requirement
C. Accept the business statement because performance can be optimized later
D. Record both interpretations and allow testing to determine compliance
Answer: B
Rationale: “Process applications quickly” is
ambiguous and cannot provide an objective basis for design, development, or
acceptance testing. The ICT Officer should facilitate clarification and
translate the business need into a measurable requirement, such as a defined
response time under specified workload conditions. This creates a shared
understanding between business and technology stakeholders and allows the
requirement to be verified objectively. Deferring the matter until testing
would allow an avoidable misunderstanding to become embedded in the solution.
3. An ICT project has completed development,
but several requirements have no corresponding test cases. The project manager
argues that the system can still proceed to user acceptance testing because the
major functions have already been demonstrated. What should the ICT Officer
identify as the PRIMARY concern?
A. The absence of
traceability between requirements and verification activities
B. The possibility that developers have used an unsuitable programming language
C. The likelihood that project stakeholders will request additional features
D. The possibility that the project team has exceeded its development budget
Answer: A
Rationale: Requirements without corresponding
verification activities create a traceability and quality-assurance gap. The
project team cannot confidently demonstrate that every approved requirement has
been implemented and tested if there is no relationship between requirements
and test cases or other verification evidence. Demonstrating major functions is
not equivalent to systematically verifying the approved requirements. The other
issues may matter in a project, but they do not represent the primary problem described.
4. A public institution proposes replacing a
manual approval process with an electronic workflow. During analysis, the ICT
team discovers that three approval stages exist only because of historical
administrative practices and provide no distinct control or decision value.
What is the BEST approach?
A. Automate all
existing stages without changing the current process
B. Remove the stages immediately because they have no technical value
C. Ask developers to determine which stages should remain during coding
D. Analyse and redesign the process before finalizing the system requirements
Answer: D
Rationale: The situation calls for business process
re-engineering before the electronic solution is finalized. Simply automating
an inefficient process can reproduce unnecessary activities in digital form,
while removing controls without proper institutional analysis can create
governance problems. The ICT Officer should work with relevant business
stakeholders to understand the purpose, risks, controls, and value of each
activity and then redesign the process where appropriate. The resulting
optimized process should inform the system requirements and design.
5. A project progress report states that 80%
of the planned development tasks have been completed. However, the project has
not yet completed integration testing, and several interfaces with existing
government systems remain unresolved. Which conclusion is MOST justified?
A. The project is
80% complete because task completion determines progress
B. The project may be substantially behind functional readiness despite task
completion
C. The project should be accepted because development tasks are mostly
completed
D. The unresolved interfaces should be excluded because they belong to other
systems
Answer: B
Rationale: Completion of individual tasks does not
necessarily mean that the project is close to operational readiness.
Integration testing and unresolved interfaces can represent critical
dependencies that prevent the complete solution from functioning as intended. A
project progress assessment should therefore consider deliverables,
dependencies, quality, integration, risks, and acceptance criteria rather than
relying solely on the percentage of tasks marked complete. The reported 80%
task completion may therefore overstate actual implementation readiness.
6. An e-Government project has an approved
requirement that citizens must authenticate using an existing national identity
service. The development team proposes creating a separate authentication
database because integration with the existing service is taking longer than
expected. What should the ICT Officer do FIRST?
A. Approve the
alternative because it will accelerate development
B. Ask the business owner to remove the authentication requirement
C. Assess the proposed deviation against architecture, security and project
requirements
D. Permit temporary authentication and replace it after deployment
Answer: C
Rationale: The proposed alternative changes an
important architectural and security-related requirement and therefore requires
formal assessment before approval. The ICT Officer should examine its
implications for security, interoperability, architecture, data management,
compliance, project scope, and long-term sustainability. Schedule pressure
alone is not sufficient justification for introducing a separate authentication
mechanism. A temporary workaround that reaches production without proper
assessment could create significant technical and governance risks.
7. During requirements workshops for a new
government service portal, users repeatedly describe desired screen layouts and
buttons but provide little information about the actual business outcomes they
need. What should the ICT Officer MOST appropriately do?
A. Ask developers
to convert the interface ideas directly into specifications
B. Document the requested screens and postpone business analysis until testing
C. Focus only on the interface because users understand their operational needs
D. Probe the underlying business processes, objectives and required outcomes
Answer: D
Rationale: Effective requirements elicitation should
identify the underlying business need rather than simply recording proposed
interface features. Users may describe a preferred solution without fully
understanding alternative ways of achieving the desired outcome. By examining
the process, objectives, actors, rules, inputs, outputs, and expected results,
the ICT Officer can distinguish genuine requirements from solution preferences.
This is particularly important when acting as the bridge between business stakeholders
and technology teams.
8. A project risk register identifies “delay
in obtaining data from the participating institution” as a high-probability
risk. Two weeks later, the institution formally informs the project team that
it will not provide the required data by the agreed date. How should this
situation now be treated?
A. Continue
recording it only as a risk until the project manager confirms impact
B. Remove it from the register because the anticipated event has occurred
C. Treat it as an issue requiring active management and resolution
D. Convert it into a project assumption because the original estimate changed
Answer: C
Rationale: A risk represents an uncertain future
event, whereas an issue is a problem or event that has already occurred and
requires management. Once the institution confirms that the data will not be
delivered as agreed, the uncertainty has materialized and the project team must
manage its actual consequences. The matter should therefore be handled as an
issue, with its impact assessed and appropriate corrective action, ownership,
and escalation applied. The historical risk record may still be useful, but it
no longer represents only a potential event.
9. A system requirements specification
contains a requirement stating: “The system shall provide secure access to
authorized users.” Which improvement would make this requirement MOST
suitable for verification?
A. Specify
measurable authentication and authorization conditions
B. Add a general statement that security is a management responsibility
C. Replace the requirement with a reference to the project security policy
D. Allow the testing team to determine what constitutes secure access
Answer: A
Rationale: A requirement should be sufficiently
precise and testable to establish whether the delivered system satisfies it.
“Secure access” is too broad because different stakeholders may interpret
security differently. Defining measurable authentication, authorization,
session, access-control, or related conditions provides objective acceptance
criteria. Referring generally to a policy may be useful as supporting
documentation, but the system requirement itself should still identify the
expected behaviour or measurable conditions.
10. An ICT project has a fixed statutory
deadline. Midway through implementation, testing reveals a critical defect that
could expose confidential citizen information. A stakeholder proposes
postponing the fix until after deployment to preserve the deadline. What should
the ICT Officer recommend?
A. Deploy on
schedule and classify the defect as a post-implementation issue
B. Evaluate the security risk and prevent deployment unless acceptable controls
exist
C. Reduce testing scope so that the remaining defects do not affect deployment
D. Ask users to sign acceptance documents acknowledging the security limitation
Answer: B
Rationale: A known critical security vulnerability
affecting confidential information cannot reasonably be treated as an ordinary
post-implementation defect merely to preserve schedule performance. The ICT
Officer should ensure that the risk is assessed and that appropriate
remediation or compensating controls are established before deployment. User
acceptance or schedule pressure does not automatically make an unacceptable
security risk acceptable. In a public-sector system handling citizen
information, protection of information assets must be incorporated into the
release decision.
11. While reviewing a project proposal, the
ICT Officer finds that the proposed system duplicates functionality already
provided by another government application, although the two systems serve
related institutions. What should be investigated FIRST?
A. Whether the
proposed system can be delivered with fewer developers
B. Whether the existing application's user interface can be reused
C. Whether integration, reuse or shared services could satisfy the requirement
D. Whether both institutions can operate separate systems under one project
plan
Answer: C
Rationale: The discovery of existing related
functionality should trigger an assessment of reuse, integration,
interoperability, or shared-service possibilities before committing resources
to another standalone solution. Duplicating functionality can increase development
and maintenance costs, create inconsistent data, complicate integration, and
produce fragmented government services. The appropriate question is not merely
whether the new system can technically be built, but whether the institutional
need can be satisfied more efficiently and sustainably using existing
capabilities.
12. A project steering committee asks why a
project dashboard reports 90% schedule completion while only 60% of planned
business functionality has passed acceptance testing. Which explanation is MOST
accurate?
A. Schedule
completion always provides a more reliable measure than acceptance
B. Acceptance testing should only begin after schedule completion reaches 100%
C. Business functionality is irrelevant if planned project activities are
completed
D. Schedule progress and functional acceptance measure different dimensions of
performance
Answer: D
Rationale: Schedule progress and functional
acceptance are distinct project-performance dimensions. A team may complete
many scheduled activities while important functionality remains untested,
defective, integrated incorrectly, or unaccepted by users. Therefore, a high
percentage of completed activities does not automatically demonstrate that the
project's intended outcomes have been achieved. Effective project monitoring
should combine schedule, scope, quality, cost, risk, deliverable, and
acceptance information to provide a meaningful picture of project health.
13. During evaluation of an enterprise
application proposal, the technical team recommends a solution because it has
many advanced features. The business analysis shows that most of those features
are unrelated to the institution's strategic objectives. What should guide the
final recommendation?
A. Alignment of
the proposed capabilities with verified business needs and objectives
B. The total number of features available in the proposed application
C. The technical complexity of the platform compared with competing products
D. The preference of developers for the technology used by the proposed
solution
Answer: A
Rationale: An ICT solution should be assessed
according to its ability to satisfy legitimate business needs and support
institutional objectives, not simply according to the number or sophistication
of its features. Excess functionality can increase cost, complexity, training
requirements, maintenance burden, and implementation risk without creating
corresponding value. The ICT Officer's role as a bridge between business and
technology requires ensuring that technology decisions remain connected to
verified business requirements and strategic outcomes.
14. A project team receives conflicting
requirements from the finance department and the operations department
regarding the same approval workflow. Both departments claim their requirement
is mandatory. What should the ICT Officer MOST appropriately do?
A. Give priority
to the department with the larger number of users
B. Facilitate clarification and resolution using agreed business rules and
governance
C. Allow developers to choose the requirement that is easier to implement
D. Include both requirements in the system and let users decide after
deployment
Answer: B
Rationale: Conflicting requirements should be
resolved through structured stakeholder analysis, business rules, governance,
and appropriate decision authority. The ICT Officer should facilitate
clarification of the underlying objectives, constraints, legal or policy
requirements, process ownership, and consequences of each alternative.
Selecting the requirement based on user population or technical convenience is
not a sound governance method. Implementing contradictory behaviours and
postponing the decision would transfer an unresolved business problem into the
operational system.
15. An e-Government project repeatedly misses
milestones because several activities depend on approval from an external
institution. The project team continues updating the schedule but does not
identify the dependency separately. What is the MOST important improvement?
A. Reduce the
duration of dependent activities to compensate for approval delays
B. Remove external activities from the project schedule to simplify reporting
C. Identify, assign and actively manage the external dependency and related
risk
D. Increase the number of project meetings until the external approval is
obtained
Answer: C
Rationale: An external approval that directly
affects project activities is a dependency that should be explicitly
identified, owned, monitored, and associated with appropriate risk or issue
management. Simply shortening downstream activities does not remove the dependency,
while excluding it from the schedule can produce misleading progress
information. More meetings may improve communication but do not constitute
dependency management by themselves. Effective planning makes dependencies
visible so that the project can anticipate their effects and establish
appropriate actions.
16. A project manager reports that all
deliverables have been produced, but the institution's business owner refuses
to sign acceptance because the system does not support a mandatory business
rule documented in the approved requirements. What is the BEST
interpretation?
A. The business
owner is delaying the project despite completion of all deliverables
B. The requirement should be ignored because the system has already been
developed
C. The project is complete because production deployment is the primary
completion measure
D. The delivered product does not yet satisfy the approved acceptance
requirements
Answer: D
Rationale: Deliverable production does not by itself
establish that the project's product is acceptable. If an approved mandatory
business rule forms part of the agreed requirements and acceptance criteria,
failure to implement it means the product has not fully met the agreed
definition of acceptance. The appropriate response is to assess and address the
gap through the project's quality, defect, change, and acceptance processes.
Deployment or completion of development activities cannot override an unmet
mandatory requirement.
17. An institution wants to digitize a
service but proposes beginning software development before documenting the
existing process because “the developers can discover the process from users
during coding.” What is the PRIMARY weakness in this approach?
A. It may cause
the system to encode an incompletely understood business process
B. It will necessarily require the institution to purchase additional hardware
C. It prevents developers from selecting an appropriate programming framework
D. It guarantees that the final system will contain more functionality than
required
Answer: A
Rationale: Understanding the existing business
process is fundamental to determining what should be digitized, improved,
eliminated, controlled, or automated. Starting development with an incompletely
understood process can result in misunderstood requirements, unnecessary
functionality, missing controls, poor workflow design, and expensive rework.
Developers can contribute to requirements discovery, but relying on informal
discovery during coding is not an adequate substitute for structured
business-process and requirements analysis.
18. During project inspection, an ICT Officer
discovers that the development team has modified several approved system
requirements but cannot produce corresponding change approvals. The resulting
software appears to work correctly. What should be the PRIMARY finding?
A. The system is
technically unacceptable because every modification causes a defect
B. The project has a requirements and change-control traceability deficiency
C. The developers have violated the project schedule by implementing
improvements
D. The software should automatically be rejected because approved requirements
cannot change
Answer: B
Rationale: Requirements may legitimately change
during a project, but changes should be evaluated, authorized, documented, and
traceable through the established change-control process. The absence of
evidence linking modifications to approved changes represents a governance and
traceability deficiency even if the resulting software appears technically
functional. The issue is therefore not simply that requirements changed, but
that the project cannot demonstrate controlled authorization and accountability
for those changes.
19. A project has three major risks with
identical probability ratings. Risk X could cause a one-week delay, Risk Y
could expose sensitive citizen information, and Risk Z could increase project
cost by 15%. Which principle should primarily guide prioritization?
A. Prioritize
risks according to the order in which they were identified
B. Prioritize the risk with the largest numerical probability value
C. Consider probability together with impact and the nature of the consequences
D. Prioritize only risks that have already affected project performance
Answer: C
Rationale: Risk prioritization should consider both
likelihood and impact, together with the nature and significance of the
consequences. A security risk affecting sensitive citizen information may
warrant greater attention than a relatively short schedule delay even when
probability ratings are identical. Similarly, financial and operational impacts
should be evaluated in context. Restricting prioritization to probability,
identification order, or risks that have already occurred would provide an
incomplete basis for risk management.
20. A government institution's project team
has developed a new application, but the proposed implementation plan contains
no activities for user training, operational support or transition from the
existing process. What is the MOST likely consequence?
A. The software
will automatically fail technical acceptance testing
B. The development team will necessarily exceed its programming workload
C. The system's source code will become incompatible with existing
infrastructure
D. The institution may experience operational disruption despite successful
software delivery
Answer: D
Rationale: Successful software development does not
guarantee successful organizational implementation. Without training, support,
transition planning, and preparation for the new operating model, users may be
unable to use the system effectively and business operations may be disrupted.
Implementation planning therefore needs to address not only the technical
deployment but also people, processes, support arrangements, data migration
where applicable, communication, and organizational readiness. These activities
are particularly important in public institutions where service continuity is
critical.
21. A project proposal states that its
objective is to “develop and implement a modern digital platform.” The proposal
does not identify what institutional problem the platform will solve or what
measurable improvement is expected. What is the MOST significant weakness?
A. The project
has not defined a sufficiently measurable business outcome
B. The project has not selected a sufficiently advanced development framework
C. The project has not included enough technical specialists in the proposal
D. The project has not identified the final programming language for
development
Answer: A
Rationale: A meaningful project objective should
establish the intended result or improvement rather than merely describe the
technology to be produced. “Develop and implement a modern digital platform”
describes an output-oriented activity but does not establish the business
problem, expected benefit, service improvement, efficiency gain, or measurable
outcome. Without a clear outcome, it becomes difficult to assess whether the
project is justified, whether the solution is appropriate, and whether
implementation has actually delivered value.
22. During evaluation of a system design
document, the ICT Officer observes that the documented architecture does not
show how the new application will exchange information with two existing
institutional systems, although the approved requirements require such
integration. What should be concluded?
A. Integration
can be omitted from the design because it belongs to implementation
B. The design has a significant gap between approved requirements and proposed
architecture
C. The integration requirement should automatically be transferred to the
operations team
D. The missing interfaces can be designed after deployment without affecting
project acceptance
Answer: B
Rationale: If integration is an approved
requirement, the system design should demonstrate how that requirement will be
satisfied. The absence of integration architecture or interface design
represents a significant gap between requirements and the proposed technical
solution. Integration is not merely an operational detail to be invented after
deployment because it can affect architecture, data exchange, security,
dependencies, testing, performance, and implementation planning. The design
should therefore be reviewed and completed before proceeding on the assumption
that the requirement has been adequately addressed.
23. A project team reports that a critical
module has passed functional testing. However, no evidence shows that the
module was tested under the expected number of simultaneous users specified in
the requirements. Which quality concern is MOST relevant?
A. The module has
not undergone requirements elicitation
B. The module has not undergone source-code compilation
C. The module's required performance characteristics have not been adequately
verified
D. The module has not undergone organizational change management
Answer: C
Rationale: Functional testing verifies whether
specified functions behave correctly, but it does not necessarily demonstrate
that the system performs adequately under expected workload. If the
requirements specify concurrent-user or performance conditions, those characteristics
require appropriate performance or load testing. Passing functional tests
therefore cannot be treated as proof that performance requirements have been
satisfied. The missing evidence represents a verification gap concerning a
non-functional requirement.
24. An e-Government project is approaching
completion. The project team proposes measuring success only by whether the
application was delivered within the approved budget and schedule. Which
additional measure would provide the MOST valuable evidence of project
effectiveness?
A. Number of
internal project meetings conducted during implementation
B. Number of lines of source code produced by the development team
C. Number of technical documents generated before deployment
D. Degree to which intended business and service outcomes were achieved
Answer: D
Rationale: Budget and schedule performance are
important dimensions of project management, but they do not by themselves
demonstrate whether an ICT project delivered its intended value. A project can
be completed on time and within budget while failing to improve the targeted
service, process, efficiency, accessibility, or institutional outcome.
Evaluation should therefore examine the extent to which the intended business
and service outcomes were achieved, alongside cost, schedule, quality, scope,
sustainability, and other relevant measures.
25. A project is implementing an electronic
government service across several public institutions. One institution insists
on retaining a locally customized workflow that conflicts with the agreed
enterprise process model. Its representatives argue that changing their
workflow would require organizational adjustment. What is the BEST response
by the ICT Officer?
A. Allow the
institution's workflow because local operational preferences should prevail
B. Reject the customization because enterprise projects must use identical
processes
C. Assess the business justification, enterprise impact and change implications
before deciding
D. Ask the development team to support both workflows without further
governance review
Answer: C
Rationale: The appropriate response is to evaluate
the customization from both business and enterprise perspectives before making
a decision. The ICT Officer must determine whether the local requirement
represents a legitimate business or regulatory need, what impact it would have
on interoperability, architecture, maintenance, governance, cost, reporting,
and standardization, and what organizational change would be required if the
enterprise process is retained. Automatically accepting local variation can
create fragmentation, while automatically rejecting it can ignore legitimate
institutional requirements. Supporting both workflows without governance
analysis may also introduce unnecessary complexity and technical debt.
26. An institution is preparing a concept
note for an e-Government project. The proposed solution is clearly described,
but the document does not explain the current business problem, affected
stakeholders, expected benefits, or consequences of not implementing the
project. What is the MOST significant deficiency?
A. The technical
solution has not been compared with enough programming frameworks
B. The project justification has not established a clear business case for
intervention
C. The development team has not yet prepared the detailed system architecture
D. The institution has not specified the preferred software testing methodology
Answer: B
Rationale: A concept note should establish why the
proposed intervention is necessary before the project proceeds into detailed
technical planning. Without a clear description of the current problem,
affected stakeholders, expected benefits, and consequences of inaction,
decision-makers cannot properly determine whether the project is justified or
aligned with institutional priorities. Technical architecture and testing
methods are important later, but they do not compensate for an inadequate
justification of the proposed investment.
27. During project planning, the team lists
“develop online application module” as one activity lasting six months. The
project manager argues that breaking it down further is unnecessary because the
development team already understands the work. What is the PRIMARY
project-management concern?
A. The activity
is too technical to be included in a project schedule
B. The activity should be assigned entirely to the project sponsor
C. The work package is insufficiently decomposed for reliable planning and
monitoring
D. The activity should be converted into a project milestone before
implementation
Answer: C
Rationale: A six-month development activity that
contains multiple stages, dependencies, resources, and deliverables is likely
too broad for effective monitoring. Decomposing the work into manageable work
packages and activities makes responsibilities, dependencies, estimates,
progress, and deliverables more visible and controllable. A Work Breakdown
Structure is intended to decompose project scope into manageable components;
simply relying on developers' understanding does not provide the project
manager with sufficient visibility for effective control.
28. During planning of an e-Government project,
the project manager estimates that a major software component will require four
months to complete. The estimate is based only on the developer's initial
judgment, with no documented assumptions, historical data or comparison with
similar work. What should the ICT Officer MOST appropriately recommend?
A. Accept the
estimate because the assigned developer is technically experienced
B. Reduce the
estimate to create additional schedule contingency for the project
C. Validate the
estimate using appropriate assumptions, historical evidence and expert input
D. Replace the
estimate with the duration of the longest task in the project plan
Answer: C
Rationale: A reliable project estimate should be
supported by an appropriate estimating basis rather than relying solely on an
individual's initial judgment. The ICT Officer should examine the assumptions
underlying the estimate and, where available, use historical information from
comparable work, expert judgment, analogous or other suitable estimating
techniques to improve confidence. This does not mean that an estimate must be
exact, but its basis should be transparent and defensible so that schedule and
resource planning can be realistically assessed.
29. A project has an approved completion
date, but several activities have no predecessor relationships recorded in the
schedule. The project manager argues that each team knows what must happen
next. What is the MOST important weakness?
A. The schedule
cannot reliably show the effects of delays and dependencies
B. The project cannot calculate the salaries of the assigned project resources
C. The schedule will automatically contain more activities than the project
requires
D. The absence of predecessors means that every activity must occur
simultaneously
Answer: A
Rationale: Predecessor and successor relationships
establish logical dependencies between project activities. Without them, the
schedule cannot reliably show how a delay in one activity could affect
subsequent work, critical paths, milestones, or the overall completion date.
Team members may understand dependencies informally, but effective project
control requires those relationships to be explicitly represented in the
schedule. The problem is therefore one of schedule logic and predictive control
rather than resource costing.
30. During implementation of a government
system, a key subject-matter expert is transferred to another institution. The
project team believes the transfer is unlikely to affect them because other
staff can provide general operational information. What should the ICT Officer FIRST
assess?
A. Whether the
project office can reduce the number of scheduled meetings
B. Whether the loss creates a capability, knowledge or delivery risk requiring
mitigation
C. Whether the transferred officer can continue approving project expenditure
remotely
D. Whether the development team can immediately replace the expert with a
programmer
Answer: B
Rationale: The departure of a key subject-matter
expert may create a significant knowledge and delivery risk, particularly when
the person possesses unique understanding of institutional processes or
requirements. The ICT Officer should assess the effect on requirements
clarification, validation, decision-making, testing, acceptance, and continuity
of institutional knowledge and then determine appropriate mitigation. Simply
assuming that general staff can replace specialized knowledge may allow a
significant project risk to go unmanaged.
📘 Get the Full Aptitude Test Questions PDF through your Gmail (Questions 1–150)
You’ve just accessed the first 30 questions. The full set of 150 expertly prepared aptitude test questions for ICT Officer II (Project Management) – e-GA, Is available, pay, and get access.
To get access to the full PDF, please make a payment of Tsh 10,000 to the LIPA numbers below:
After payment, please send a text message to notify us of your payment:
⚠️ Important Notice
- The PDF will be watermarked with your name and phone number and protected for personal use only.
- Redistribution, sharing, screenshotting, or copying the contents is strictly prohibited. When you share unlawfully, your name and phone number are visible and easy to trace as you leaked a document to other third parties.
- Legal action may be taken against the misuse of this material.
Thank you for supporting quality content. Best of luck in your interview preparation!
 – e-GA.){kind=link}
0 Comments
PLACE YOUR COMMENT HERE
WARNING: DO NOT USE ABUSIVE LANGUAGE BECAUSE IT IS AGAINST THE LAW.
THE COMMENTS OF OUR READERS IS NOT OUR RESPONSIBILITY.