“150”, Aptitude Test Questions and Answers for ICT Officer II (Business Analyst) – e-GA.
ABSTRACT
This publication provides 150 Aptitude
Test Questions and Answers for ICT Officer Grade II (Business Analyst),
designed to help candidates prepare for competitive public-service online
aptitude assessments in Tanzania, particularly within the e-Government
environment. The questions assess practical knowledge, analytical reasoning,
problem-solving, requirements analysis, business-process modelling, systems
analysis and design, stakeholder management, software development, testing and
quality assurance, project management, ICT governance, interoperability, and
e-Government initiatives. Each question contains four plausible multiple-choice
options, the correct answer, and a concise rationale, with emphasis on
realistic scenarios that require candidates to identify the most appropriate
solution and apply professional judgment rather than rely on simple
memorization.
Prepared by: ICT Officer II (Business
Analyst) – e-GA.
Compiled by ICT Officer II (Business
Analyst) – e-GA.
0628729934.
Date: September 06, 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 (Database Administration)
For Personal Use by Applicants Preparing
for ICT Officer II (Business Analyst) - at Public Service Recruitment Service.
ICT OFFICER II
(Business Analyst) – e-GA
150 Aptitude
Test Questions and Answers
1. A Government institution intends to
replace a manual process with an enterprise application. During initial
interviews, each department describes the problem differently, and some users
immediately propose specific software features. What should the Business
Analyst do first?
A. Document the
requested features and submit them to developers for estimation.
B. Select the department with the largest workload as the primary requirements
owner.
C. Establish the underlying business problems, objectives, stakeholders and
current processes.
D. Compare available software products before determining the detailed business
requirements.
Answer: C.
Establish the underlying business problems, objectives, stakeholders and
current processes.
Rationale: The strongest starting point is to
understand the business problem and its context before allowing proposed
features or technology preferences to shape the solution. Establishing
objectives, stakeholders and the current process provides the foundation for
distinguishing genuine business needs from assumptions about solutions. Sending
preliminary feature requests directly to developers risks embedding incomplete
or conflicting requirements, while selecting one department prematurely may
ignore enterprise-wide interests. Product comparison is also premature because
the institution has not yet established what the solution must accomplish.
2. A Business Analyst discovers that a
proposed electronic approval system will automate an inefficient manual process
without changing any of its unnecessary approval stages. What is the most
appropriate response?
A. Proceed with
automation because electronic processing will remove most inefficiencies.
B. Analyse and redesign the business process before finalizing the system
requirements.
C. Ask developers to reproduce the existing workflow and optimize it after
deployment.
D. Replace the approval stages with automated rules without consulting process
owners.
Answer: B.
Analyse and redesign the business process before finalizing the system
requirements.
Rationale: Automating a poor process can simply make
an inefficient process operate faster without addressing its underlying
weaknesses. The Business Analyst should therefore understand the AS-IS process,
identify unnecessary steps, bottlenecks, controls and responsibilities, and
help establish an improved TO-BE process before requirements are finalized.
This ensures that the application supports an improved business process rather
than merely reproducing existing inefficiencies.
3. During requirements validation for a
Government revenue-related application, users request that the system
"respond quickly." Developers interpret this differently from the
users. Which action would provide the strongest improvement to the
requirement?
A. Convert the
requirement into a preferred programming technology.
B. Replace the requirement with a statement that the system must be modern.
C. Ask developers to determine an acceptable response time during
implementation.
D. Define measurable response-time criteria under specified operating
conditions.
Answer: D.
Define measurable response-time criteria under specified operating conditions.
Rationale: A requirement such as "respond
quickly" is ambiguous because different stakeholders may interpret it
differently. A stronger non-functional requirement should specify measurable
performance criteria, such as a maximum response time under defined workload
and network conditions. This gives developers a clear target and enables
testers to determine objectively whether the requirement has been satisfied.
Leaving the interpretation to developers transfers an important business
requirement decision to the implementation team.
4. A project team has documented 80
functional requirements. During review, the Business Analyst discovers that
several requirements cannot be traced to any stated business objective,
stakeholder need or process problem. What is the best interpretation?
A. The
requirements should remain because all user requests are valid project
requirements.
B. The requirements should be converted into non-functional requirements for
better traceability.
C. The requirements should be assigned directly to developers so their
technical value can be assessed.
D. The requirements should be reviewed to establish their business
justification before acceptance.
Answer: D. The
requirements should be reviewed to establish their business justification
before acceptance.
Rationale: A requirement should have a defensible
relationship to a business need, objective, process, stakeholder need or
necessary system constraint. A requirement without such justification may
represent scope creep, a personal preference, duplication or an unnecessary
feature. Traceability is therefore not merely a documentation exercise; it
helps establish why the requirement exists and whether it contributes to the
intended business outcome. Assigning unsupported requirements to developers
does not resolve the underlying business justification problem.
5. A project involves a Ministry, several
agencies and an external vendor. The Ministry wants strict controls, one agency
wants maximum flexibility, another wants rapid implementation, and the vendor
proposes a solution that satisfies only some requirements. What should the
Business Analyst do first when addressing the conflict?
A. Ask the
project manager to select the stakeholder whose requirements have priority.
B. Analyse stakeholder interests, business objectives, constraints and
conflicting requirements.
C. Accept the vendor proposal temporarily and resolve the conflicts during
system testing.
D. Prioritize requirements according to which stakeholder has the strongest
institutional influence.
Answer: B.
Analyse stakeholder interests, business objectives, constraints and conflicting
requirements.
Rationale: Stakeholder conflict cannot be resolved
professionally merely by hierarchy, vendor preference or implementation
convenience. The Business Analyst should first understand each stakeholder's
interests, authority, objectives, constraints and the business consequences of
the competing requirements. This creates an evidence-based basis for
prioritization and negotiation. A stakeholder's influence is important, but
influence alone does not determine whether a requirement is necessary or
appropriate, while postponing conflicts until testing makes resolution
considerably more expensive.
6. A Business Analyst receives a requirement
stating: "Only authorized officers should access confidential case
records." Which interpretation is most appropriate?
A. The
requirement primarily describes an access-control security constraint.
B. The requirement primarily describes a user-interface navigation preference.
C. The requirement primarily describes a database storage optimization
requirement.
D. The requirement primarily describes a business reporting frequency
requirement.
Answer: A. The
requirement primarily describes an access-control security constraint.
Rationale: The requirement concerns who may access
protected information and therefore represents an authorization and
access-control requirement. A Business Analyst should recognize that such
requirements can affect roles, permissions, authentication, authorization,
auditability and system design. It is not primarily about interface navigation,
database performance or reporting frequency. e-GA's application guidance
specifically identifies security requirements, including authentication,
authorization, user management and audit logging, as requirements that should
form part of Government applications.
7. A developer tells the Business Analyst
that a requirement cannot be implemented exactly as written because it
conflicts with an existing system interface. The business owner insists that
the requirement must remain unchanged. What is the best next step?
A. Tell the
developer to implement the requirement regardless of the integration
limitation.
B. Remove the requirement because the existing interface is already
operational.
C. Ask the business owner to accept the limitation without further technical
investigation.
D. Facilitate analysis of alternative solutions and their business and
technical impacts.
Answer: D.
Facilitate analysis of alternative solutions and their business and technical
impacts.
Rationale: The Business Analyst's role is to bridge
business needs and technology constraints rather than automatically siding with
either party. The correct response is to investigate alternatives, understand
the integration constraint, assess the effect on the business objective, and
present viable options for an informed decision. Automatically overriding the
developer ignores a technical dependency, while automatically abandoning the
requirement ignores the business need. The Business Analyst should make the trade-off
visible and support an evidence-based decision.
8. During analysis of a Government service,
users report that applications are frequently returned for correction. The
Business Analyst finds that different officers interpret the same eligibility
conditions differently, even though the underlying policy is the same. What
should the Analyst investigate first?
A. Whether the
application interface should provide more data-entry fields.
B. Whether the database should be migrated to a different technology.
C. Whether the business rules are sufficiently defined and consistently
interpreted.
D. Whether additional officers should be assigned to review the applications.
Answer: C.
Whether the business rules are sufficiently defined and consistently
interpreted.
Rationale: When the same eligibility conditions are
interpreted differently by officers, the primary analytical concern is whether
the governing business rules are clear, complete and consistently understood.
The Business Analyst should establish the authoritative rules, identify
ambiguities or conflicting interpretations, and determine how they should be
represented in the improved process and system requirements. Adding fields,
changing database technology or increasing staffing would not address the
underlying inconsistency in business-rule interpretation.
9. During User Acceptance Testing, users
identify a defect that causes an approved transaction to appear as pending. The
developer argues that the system behaves according to the technical
specification. What should the Business Analyst check first?
A. Whether the
defect can be hidden through a user-interface modification.
B. Whether the developer followed the organization's preferred coding
standards.
C. Whether the expected business behaviour is correctly defined in the approved
requirements and acceptance criteria.
D. Whether the database administrator can modify the transaction status
directly.
Answer: C.
Whether the expected business behaviour is correctly defined in the approved
requirements and acceptance criteria.
Rationale: The Business Analyst should establish
whether the system behaviour contradicts an agreed business requirement or
acceptance criterion. If the requirement clearly states that an approved
transaction must no longer appear as pending, the behaviour represents a defect
against the expected business outcome. If the requirement itself is ambiguous,
the discrepancy may instead indicate a requirements problem that must be
clarified. The developer's claim about technical compliance does not by itself
establish business correctness. e-GA's QA guidance emphasizes requirements
documentation and User Acceptance Testing involving the user department.
10. A project sponsor asks the Business
Analyst to add a new reporting module halfway through development because
senior management has requested it. The module is not in the approved scope.
What is the most appropriate action?
A. Assess the
requested change through the established change-control process before
incorporation.
B. Add the module immediately because senior management has requested the
functionality.
C. Ask developers to implement the module only if they have unused development
capacity.
D. Reject the module because requirements cannot be changed after project
approval.
Answer: A.
Assess the requested change through the established change-control process
before incorporation.
Rationale: Approved requirements can change, but
uncontrolled changes create scope, cost, schedule, quality and dependency
risks. The Business Analyst should document and analyse the requested change,
determine its business value and impacts, and ensure it follows the project's
approved change-control mechanism. Senior management interest does not
automatically eliminate governance requirements, while rejecting every change
contradicts the reality that legitimate business needs can evolve. e-GA
guidance requires project changes to follow institutional ICT project
change-management procedures.
11. A Business Analyst is mapping a process in
which one application validates information, another application stores the
official record, and a third system sends notifications. Which concern should
receive particular attention during analysis?
A. Whether every
application uses the same programming language.
B. Whether the interfaces and data exchanges support the required end-to-end
process.
C. Whether all participating applications have identical user-interface
layouts.
D. Whether each application can independently perform the entire business
process.
Answer: B.
Whether the interfaces and data exchanges support the required end-to-end
process.
Rationale: When a business process spans multiple
applications, the Business Analyst must understand how information moves
between systems, what data is exchanged, when exchanges occur, and what happens
when an interface fails. Interoperability is therefore central to the analysis.
Identical programming languages or interfaces are not prerequisites for
successful integration, and requiring every application to perform the entire
process would undermine the purpose of specialized enterprise systems.
Tanzania's e-Government Regulations specifically emphasize interoperability and
consideration of interoperability during business-process re-engineering.
12. A department requests a new system because
officers spend significant time entering the same citizen information into
three separate applications. What should the Business Analyst investigate before
recommending a new application?
A. Whether the
department can employ additional officers to perform the data entry.
B. Whether developers can create three faster interfaces for the existing
applications.
C. Whether the repeated entry results from inadequate interoperability or poor
process design.
D. Whether the existing applications should all be replaced with one identical
application.
Answer: C.
Whether the repeated entry results from inadequate interoperability or poor
process design.
Rationale: Repeated data entry is a symptom, not
necessarily evidence that an entirely new application is required. The Business
Analyst should determine whether the underlying cause is duplicated processes,
missing integration, incompatible data structures, unclear ownership or another
process weakness. This prevents the institution from procuring or developing
another system without solving the actual problem. e-Government guidance places
emphasis on interoperability and business-process re-engineering as part of integrated
Government systems.
13. A Business Analyst is preparing acceptance
criteria for an electronic permit application. Which criterion is most
suitable?
A. The system
should be user-friendly and technologically advanced.
B. The system should provide an attractive interface for permit applicants.
C. A submitted application shall display a confirmation reference after
successful submission.
D. The system should use an efficient architecture that supports future
improvements.
Answer: C. A
submitted application shall display a confirmation reference after successful
submission.
Rationale: Good acceptance criteria should be
specific enough to determine objectively whether the expected behaviour has
been achieved. A confirmation reference following successful submission can be
tested directly and has a clear expected outcome. Terms such as "user-friendly,"
"attractive" and "technologically advanced" are subjective
and require further clarification before they can serve as reliable acceptance
criteria. Similarly, architectural efficiency is important but is not expressed
as a directly testable business outcome in the alternatives given.
14. A project team proposes purchasing a
commercial application. The vendor demonstrates impressive functionality, but
the Business Analyst finds that several critical institutional processes would
need to be changed merely to fit the product. What should the Analyst
recommend?
A. Select the
product because changing business processes is always preferable to
customization.
B. Evaluate the gap between institutional requirements and the product before
making the decision.
C. Reject the product because commercial applications cannot support Government
institutions.
D. Approve the product and document the process changes as implementation
assumptions.
Answer: B.
Evaluate the gap between institutional requirements and the product before
making the decision.
Rationale: Product selection should be based on how
well the solution satisfies validated business requirements, not simply on
demonstrations or the product's number of features. A structured gap analysis
should identify which requirements are supported, configurable, unavailable, or
dependent on customization or process changes. The institution can then
evaluate cost, risk, operational impact and feasibility before deciding.
Commercial solutions can be appropriate in some circumstances; the critical
issue is fit with the institution's justified requirements. e-GA guidance
requires applications to fulfil institutional business requirements.
15. A Business Analyst is asked to prepare
requirements for an application that will be developed by an external vendor.
Which approach provides the strongest protection against misunderstandings
during development?
A. Describe the
desired system mainly through high-level objectives and allow the vendor to
interpret details.
B. Allow the vendor to gather requirements because it understands the
technology better than users.
C. Provide only screen designs because detailed requirements can constrain
technical innovation.
D. Produce clear, validated requirements with traceability, acceptance criteria
and stakeholder sign-off.
Answer: D.
Produce clear, validated requirements with traceability, acceptance criteria
and stakeholder sign-off.
Rationale: External development increases the
importance of precise communication because the vendor does not possess the
same implicit understanding of institutional processes as internal users. Clear
requirements, traceability and acceptance criteria reduce interpretation gaps,
while stakeholder validation and sign-off establish a common baseline. Screen
designs alone cannot capture business rules, integrations, exceptions,
security, data requirements or non-functional requirements. e-GA QA guidance
specifically recognizes the importance of reviewed requirements, an SRS,
user-department sign-off and UAT.
16. A Business Analyst discovers that a
proposed Government application will store sensitive transaction information
but the requirements document contains no provisions for audit trails, user
authorization or recovery of data after failure. What is the best action?
A. Identify and
incorporate appropriate security and resilience requirements before solution
approval.
B. Leave the issue to the cybersecurity team because it is outside business
analysis responsibilities.
C. Wait until system testing to determine whether security controls are
technically sufficient.
D. Allow the vendor to select security controls based on its preferred
application architecture.
Answer: A.
Identify and incorporate appropriate security and resilience requirements
before solution approval.
Rationale: Security and resilience are system
requirements and should be considered during requirements analysis rather than
discovered only after development. The Business Analyst should work with
relevant ICT and security specialists to establish requirements for
authorization, auditability, backup, recovery and other appropriate controls.
Leaving security entirely until testing can result in expensive architectural
changes, while allowing a vendor to define institutional security needs
independently weakens business and governance control. Current e-GA application
guidance expressly identifies audit logs, authentication, authorization, user
management, session management, backup and recovery as relevant application
requirements.
17. A project has two proposed solutions.
Solution X costs less initially but requires extensive manual reconciliation
between systems. Solution Y costs more initially but eliminates most
reconciliation and significantly reduces processing time. Which analysis would
best support the business decision?
A. Compare only
the initial acquisition prices because future benefits are uncertain.
B. Select Solution X because lower initial cost is the strongest measure of
value.
C. Evaluate total costs, measurable benefits, operational impacts, risks and
strategic alignment.
D. Select Solution Y because automation always provides greater long-term
organizational value.
Answer: C.
Evaluate total costs, measurable benefits, operational impacts, risks and
strategic alignment.
Rationale: A sound business case considers more than
purchase price. The Business Analyst should help evaluate total cost of
ownership, expected benefits, operational savings, productivity effects, risks,
dependencies, strategic alignment and implementation implications. Lower
initial cost does not necessarily mean lower overall cost, while automation
does not automatically guarantee value. The decision should therefore be
supported by structured evidence rather than a single financial or
technological factor.
18. During stakeholder interviews, a senior
officer provides detailed requirements that conflict with the documented legal
and operational process. The officer insists that the system must follow his
preferred approach. What should the Business Analyst do?
A. Accept the
officer's requirements because senior stakeholders should determine system
behaviour.
B. Reject the requirements immediately because individual preferences cannot
influence system design.
C. Ask developers to determine which interpretation is technically easier to
implement.
D. Validate the requirements against authoritative business rules, policies and
process ownership.
Answer: D.
Validate the requirements against authoritative business rules, policies and
process ownership.
Rationale: Stakeholder seniority does not
automatically make a requested behaviour an authoritative business requirement.
The Analyst should establish the governing business rules, policies, legal
requirements and accountable process ownership, then determine whether the
requested change is legitimate and whether formal approval is required. This
approach preserves stakeholder engagement while preventing personal preferences
from becoming uncontrolled system rules. It also helps identify situations
where an organizational process itself requires authorized change rather than
simply being encoded into software.
19. A Business Analyst is reviewing a use-case
model for a public-service application. One use case states: "Process
Application." During analysis, the team discovers that processing includes
validation, fee assessment, approval, rejection, notification and appeal
handling. What is the best response?
A. Keep the use
case unchanged because use cases should always represent complete business
processes.
B. Analyse whether the broad use case should be decomposed to clearly represent
meaningful interactions and outcomes.
C. Replace the use case with database entities because those provide greater
implementation precision.
D. Remove the use case because detailed workflows belong exclusively in
technical design documents.
Answer: B.
Analyse whether the broad use case should be decomposed to clearly represent
meaningful interactions and outcomes.
Rationale: "Process Application" may be
too broad to communicate the distinct user goals and system interactions
involved. The Business Analyst should examine whether meaningful use cases can
be separated around identifiable goals, actors and outcomes while preserving
the overall business context. Use cases should help stakeholders and technical
teams understand required system behaviour; replacing them with database
entities confuses business interaction modelling with data modelling, while
removing them entirely loses valuable requirements information.
20. A Government ICT project has completed
requirements gathering, but the project team discovers that the proposed
solution depends on infrastructure that is unavailable within the institution
and cannot be provided within the approved implementation period. What should
the Business Analyst contribute first?
A. Ask developers
to redesign the application without considering the infrastructure limitation.
B. Recommend immediate cancellation because infrastructure constraints make the
project impossible.
C. Record the constraint and continue implementation while infrastructure
arrangements are resolved.
D. Assess the dependency's impact on feasibility, scope, schedule, cost and
alternative solution options.
Answer: D.
Assess the dependency's impact on feasibility, scope, schedule, cost and
alternative solution options.
Rationale: A critical infrastructure dependency can
affect whether the proposed solution is feasible within the approved project
constraints. The Business Analyst should help quantify the impact, identify
alternatives, and support a decision based on evidence. Immediate cancellation
may be premature, while continuing blindly exposes the project to avoidable
failure. Government ICT project guidance emphasizes structured project
planning, implementation considerations and assessment of project conditions
before delivery.
21. An institution wants to introduce an
electronic workflow that will eliminate several manual duties performed by
staff. The technical solution is feasible, but affected employees strongly
oppose the project. What is the most important Business Analysis
consideration?
A. Whether the
software can technically perform the affected employees' existing tasks.
B. Whether the project budget contains sufficient funds for additional
application features.
C. Whether the organizational change, stakeholder impact and adoption
requirements have been addressed.
D. Whether the vendor can provide additional developers to accelerate system
implementation.
Answer: C.
Whether the organizational change, stakeholder impact and adoption requirements
have been addressed.
Rationale: Technical feasibility does not guarantee
successful organizational adoption. When a solution changes responsibilities,
workflows or roles, the Business Analyst should consider stakeholder impact,
communication, training, readiness, resistance, revised procedures and adoption
measures. Ignoring these factors can cause a technically successful system to
fail operationally. This directly reflects the responsibility to participate in
business-process improvement, organizational change and implementation of e-Government
initiatives.
22. A Business Analyst is preparing a
requirements traceability matrix for a new Government application. Which
relationship provides the most useful end-to-end traceability?
A. Business
objective → requirement → design component → test case → acceptance result.
B. User name → department → programming language → database table → deployment
server.
C. Project budget → vendor name → developer → source-code module → operating
system.
D. Business process → meeting minutes → project manager → infrastructure →
maintenance contract.
Answer: A.
Business objective → requirement → design component → test case → acceptance
result.
Rationale: Effective traceability connects the
original business need to the requirement and then through implementation and
verification to evidence that the expected outcome was achieved. This allows
the team to determine why a requirement exists, where it is implemented, how it
is tested and whether it has been accepted. The other chains contain useful
project information but do not establish a coherent
requirement-to-business-outcome relationship.
23. A public institution is considering
acquisition of a SaaS application. The vendor offers an attractive subscription
but cannot clearly explain data-handling responsibilities, contractual
obligations, service limitations and exit arrangements. What should the
Business Analyst recommend?
A. Approve the
service because SaaS reduces the institution's infrastructure responsibilities.
B. Ask the vendor to clarify only the application's functional features before
approval.
C. Conduct a detailed assessment of contractual, business, technical, security
and exit requirements.
D. Reject SaaS entirely because Government institutions should develop all
applications internally.
Answer: C.
Conduct a detailed assessment of contractual, business, technical, security and
exit requirements.
Rationale: SaaS acquisition creates dependencies
beyond application functionality, including subscription conditions, data
responsibilities, service availability, security, integration, continuity and
what happens when the institution terminates the service. These considerations
should be analysed before commitment. Current e-GA guidance specifically states
that institutions intending to acquire SaaS should intensively analyse
purchase-contract and subscription requirements, and that SaaS applications
used by public institutions are subject to e-GA approval requirements.
24. A testing team reports that all documented
functional test cases have passed, but users still report that the system does
not support an important real-world business scenario. What is the most
likely explanation?
A. The testers
necessarily used an incorrect testing methodology.
B. The requirements or acceptance criteria may have failed to capture the
business scenario adequately.
C. The developers necessarily implemented the system using an inappropriate
programming framework.
D. The database design must necessarily be responsible for the missing business
capability.
Answer: B. The
requirements or acceptance criteria may have failed to capture the business
scenario adequately.
Rationale: Passing documented tests demonstrates
compliance with the tested expectations, but it does not prove that the
requirements themselves completely represent the business need. If an important
real-world scenario was omitted from the requirements or acceptance criteria,
the system can pass every recorded test while still failing an operational
need. This illustrates why requirements validation, stakeholder involvement and
realistic acceptance criteria are essential before and during development. e-GA
QA guidance specifically emphasizes requirements review, user-department
involvement and User Acceptance Testing.
25. A Government institution proposes
developing an application independently of existing Government systems. During
analysis, the Business Analyst discovers that another public institution
already operates a solution that performs most of the required functions and
could potentially be shared or integrated. What should the Business Analyst most
appropriately do?
A. Continue with
independent development because each institution should control its own
application.
B. Recommend purchasing a new commercial product to avoid dependency on another
institution.
C. Ignore the existing solution until the new application's requirements have
been fully implemented.
D. Evaluate the existing solution and shared-service or integration options
against the institution's requirements.
Answer: D.
Evaluate the existing solution and shared-service or integration options
against the institution's requirements.
Rationale: The existence of a potentially reusable
Government solution should trigger analysis rather than automatic rejection or
adoption. The Business Analyst should determine whether the existing capability
satisfies the institution's functional and non-functional requirements, whether
it can be shared or integrated, what gaps exist, and what the operational,
technical and governance implications would be. This can reduce duplication and
improve Government-wide value where appropriate. e-GA's current project-review
guidance highlights reducing duplication of effort and increasing benefits
through reusable solutions, while its application guidance requires shared
systems to fulfil stakeholder requirements.
26. A Government institution is introducing an
electronic service that depends on information from several existing systems.
During analysis, the Business Analyst discovers that one system uses a
citizen's national identifier as the primary reference, while another
identifies the same citizen using an internally generated customer number. What
should the Analyst investigate first?
A. Whether the
systems can exchange the identifiers through an agreed mapping or common
identification approach.
B. Whether both systems should immediately be replaced with a single enterprise
database.
C. Whether users should manually enter both identifiers whenever information is
transferred.
D. Whether developers can select whichever identifier is easier to implement in
the new application.
Answer: A.
Whether the systems can exchange the identifiers through an agreed mapping or
common identification approach.
Rationale: Different identifiers for the same
real-world entity can create data-matching and interoperability problems when
systems exchange information. The Business Analyst should establish the
meaning, ownership and authority of each identifier and determine whether an
approved mapping, common identifier or other integration mechanism can reliably
associate the records. Replacing systems or requiring manual entry would be
premature, while allowing developers to choose an identifier based on
implementation convenience could create inconsistent business data.
27. During requirements workshops for a
Government-wide application, one department repeatedly describes requirements
in terms of specific screens and buttons, while another department focuses on
the outcomes it needs to achieve. What should the Business Analyst do to
establish a common requirements baseline?
A. Adopt the
screen-based requirements because they are easier for developers to estimate.
B. Translate both sets of inputs into underlying business capabilities, rules
and outcomes.
C. Ask each department to produce its own separate specification for later
consolidation.
D. Prioritize the department whose requirements contain more implementation
details.
Answer: B.
Translate both sets of inputs into underlying business capabilities, rules and
outcomes.
Rationale: Stakeholders often express needs at
different levels of abstraction. A strong Business Analyst separates the
desired business outcome from proposed implementation mechanisms, identifies
common objectives and rules, and then determines the appropriate system
capabilities. Screen layouts may eventually be useful, but they should not
become the requirements baseline simply because they appear detailed. Separate
specifications without reconciliation would preserve inconsistencies rather
than establish a coherent enterprise requirement set.
28. A Government service currently requires an
officer to make a judgement based on several conditions, but the institution
wants the decision to be automated. During analysis, the Business Analyst finds
that the conditions interact in different combinations depending on the
applicant's circumstances. Which technique would be most useful for
clarifying the decision logic?
A. A context
diagram showing the systems connected to the service.
B. A data dictionary defining the fields used by the application.
C. A decision table showing condition combinations and corresponding outcomes.
D. A deployment diagram showing where the application components will operate.
Answer: C. A
decision table showing condition combinations and corresponding outcomes.
Rationale: A decision table is particularly useful
when a business decision depends on multiple conditions whose combinations
produce different outcomes. It allows the Analyst and business stakeholders to
identify valid combinations, expected decisions and potentially missing or
contradictory rules before the logic is automated. A context diagram focuses on
system boundaries, a data dictionary defines information elements, and a
deployment diagram describes technical deployment rather than business decision
logic.
29. A Business Analyst compares the AS-IS and
TO-BE processes and discovers that the proposed electronic process removes two
approval stages. Senior management asks whether this creates a control
weakness. What is the best analytical response?
A. Restore both
approvals because removing controls increases implementation risk.
B. Retain one approval automatically because every electronic process requires
human approval.
C. Remove the approvals permanently because automation should minimize human
intervention.
D. Determine the control objectives served by the approvals and assess how the
TO-BE process addresses them.
Answer: D.
Determine the control objectives served by the approvals and assess how the
TO-BE process addresses them.
Rationale: Process redesign should not treat every
existing control as either mandatory or unnecessary merely because the workflow
is being automated. The Analyst should understand why each approval exists,
identify its control objective, and determine whether another mechanism in the
TO-BE process provides equivalent or stronger control. Automation may replace
some manual controls with system controls, but removing controls without
analysing their purpose could introduce operational, financial or compliance
risks.
30. A Government institution is reviewing a
proposed electronic service and discovers that different departments use
different names for the same business event. One department calls it
"registration," another calls it "enrolment," while both
refer to the same point at which an applicant becomes officially recorded. What
should the Business Analyst establish?
A. A common
business definition and agreed terminology for the event.
B. Separate system functions so each department can retain its preferred
terminology.
C. Different database fields so each department can store its own
interpretation.
D. A user-interface configuration allowing each department to rename the event
independently.
Answer: A. A
common business definition and agreed terminology for the event.
Rationale: In an enterprise environment,
inconsistent terminology can cause misunderstandings in requirements,
workflows, reports and integration. The Analyst should establish the
authoritative meaning of the business event and agree on terminology that
accurately represents the shared process. Allowing departments to maintain
different meanings under separate labels may preserve the underlying
inconsistency rather than resolving it. Technical structures and interface
configuration should follow the agreed business meaning, not substitute for it.
📘 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 (Business Analyst) – 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.