Skip to main content

FE · 8% of the exam

Systems Engineering, Analysis, and Design practice questions

10 free Systems Engineering, Analysis, and Design questions for the FE Industrial and Systems Exam (FE) exam, each with the correct answer and an explanation for every option.

What this domain covers

Engineering whole systems across their life: requirements, functional analysis, system design, reliability, configuration management and risk.

Exam weight
8%
On a real exam
≈ 9 questions
In our bank
48 questions

Topics that come up most

  • Requirements and functional analysis
  • System life cycle stages
  • Series, parallel and redundant reliability
  • Configuration and change management
  • Risk identification and mitigation

How to study it

Practise reducing mixed series and parallel block diagrams to a single reliability value; work from the innermost group outwards.

Sample Systems Engineering, Analysis, and Design questions

Try each one before opening the answer. Original questions written to the official exam objectives.

  1. Question 1

    The cost of making a design change generally:

    • AFalls the later it occurs
    • BRises the later it occurs in the life cycle
    • CStays constant
    • DIs zero after production starts
    Show answer and explanation

    Answer: B) Rises the later it occurs in the life cycle

    • AIncorrect. Later changes cost more.
    • BCorrect. Early changes are cheapest.
    • CIncorrect. It increases over time.
    • DIncorrect. It's highest then.
  2. Question 2

    Preventive replacement is most worthwhile for components in which life-cycle phase?

    • AAny phase equally
    • BUseful life, where the rate is constant
    • CInfant mortality, where the rate falls
    • DWear-out, where the failure rate rises
    Show answer and explanation

    Answer: D) Wear-out, where the failure rate rises

    • AIncorrect. It depends on the failure pattern.
    • BIncorrect. Replacement doesn't lower a constant rate.
    • CIncorrect. Replacement restarts infant failures.
    • DCorrect. Replacing before wear-out avoids failures.
  3. Question 3

    Three components in series each have reliability 0.95. The system reliability is about:

    • A0.857
    • B0.950
    • C0.900
    • D0.999
    Show answer and explanation

    Answer: A) 0.857

    • ACorrect. Series reliability is 0.95³.
    • BIncorrect. Multiply all three.
    • CIncorrect. That's about 0.95²; use 0.95³.
    • DIncorrect. That's a parallel arrangement.
  4. Question 4

    In systems engineering, validation answers the question:

    • ADid we build the right system for the user's needs?
    • BDid we build the system to its specifications?
    • CIs the project on budget?
    • DIs the code compiled?
    Show answer and explanation

    Answer: A) Did we build the right system for the user's needs?

    • ACorrect. Verification asks whether it meets its specifications.
    • BIncorrect. That's verification.
    • CIncorrect. That's cost control.
    • DIncorrect. Validation concerns user needs.
  5. Question 5

    Two identical components in series must give a system reliability of 0.9. Each needs a reliability of about:

    • A0.9
    • B0.949
    • C0.45
    • D0.81
    Show answer and explanation

    Answer: B) 0.949

    • AIncorrect. The product would be 0.81.
    • BCorrect. \(\sqrt{0.9}\).
    • CIncorrect. That halves it.
    • DIncorrect. That's the product of two 0.9s.
  6. Question 6

    Maintainability is commonly measured by:

    • AMean time between failures
    • BMean time to repair (MTTR)
    • CUnit cost
    • DThroughput
    Show answer and explanation

    Answer: B) Mean time to repair (MTTR)

    • AIncorrect. That's reliability.
    • BCorrect. Lower MTTR means easier maintenance.
    • CIncorrect. That isn't maintainability.
    • DIncorrect. That isn't maintainability.
  7. Question 7

    In systems engineering, the activity called requirements elicitation is mainly concerned with:

    • AIdentifying stakeholders and drawing out their needs, constraints, and expectations
    • BConfirming through inspection and test that the built system meets its specifications
    • CAssigning each system function to specific hardware, software, or human elements
    • DTracking and approving design changes against an established configuration baseline
    Show answer and explanation

    Answer: A) Identifying stakeholders and drawing out their needs, constraints, and expectations

    Requirements elicitation finds the stakeholders and draws out their needs and constraints, which then become formal requirements. Verification, functional allocation and configuration management are separate, later activities.

    • ACorrect. Elicitation is the first step of requirements work. It finds the stakeholders and draws out their needs and constraints, which are later analyzed and written as formal requirements.
    • BIncorrect. This is verification, which happens after design and build. It checks the product against requirements that already exist; it does not find out what stakeholders need.
    • CIncorrect. This is functional allocation, a design activity. It comes after requirements have been gathered and analyzed.
    • DIncorrect. This is configuration management. It controls changes to baselined items; it does not discover stakeholder needs.
  8. Question 8

    Two subcontractors are separately building a flight computer and a sensor package that must exchange data over a shared bus. Which document should set out the connector pinouts, signal characteristics, and message formats so the two units work together at integration?

    • AWork breakdown structure
    • BConcept of operations
    • CInterface control document
    • DRequirements traceability matrix
    Show answer and explanation

    Answer: C) Interface control document

    An interface control document sets out the physical, electrical, and data connections between subsystems, so separately developed parts are compatible when integrated.

    • AIncorrect. A WBS splits the project's work and deliverables into manageable elements for planning and cost control. It does not specify technical connections between units.
    • BIncorrect. A ConOps describes, from the user's point of view, how the system will be operated and used. It does not specify pinouts or message formats.
    • CCorrect. An ICD defines the physical, electrical, and data connections between systems or subsystems, so independently developed units fit together at integration.
    • DIncorrect. An RTM links requirements to their sources, design elements, and verification activities. It does not define how two units physically or logically connect.
  9. Question 9

    In systems engineering, which statement best describes an emergent property of a system?

    • AIt results from interactions among components and is not found in any single part
    • BIt can be found by adding up the properties of each component on its own
    • CIt belongs to the most critical component and sets that component's function
    • DIt appears only after the system is fielded and fails during operation
    Show answer and explanation

    Answer: A) It results from interactions among components and is not found in any single part

    An emergent property is a whole-system property that comes from interactions among components. It cannot be found in, or predicted from, any single component on its own.

    • ACorrect. Emergent properties, such as safety or overall performance, exist only when the whole system is considered. They come from the way components interact.
    • BIncorrect. That describes an additive (aggregate) property. Emergent properties cannot be predicted from the components alone, because they depend on interactions.
    • CIncorrect. A property owned by one component is a component-level property. An emergent property exists only at the level of the whole system.
    • DIncorrect. Emergent properties can be desirable or undesirable, and they are present whenever the system operates, not only when it fails. Systems engineering tries to anticipate them during design.
  10. Question 10

    In an FMEA, a failure mode rated severity 8, occurrence 5 and detection 3 has a risk priority number of:

    • A16
    • B120
    • C40
    • D24
    Show answer and explanation

    Answer: B) 120

    • AIncorrect. Multiply, don't add.
    • BCorrect. RPN = S × O × D.
    • CIncorrect. Include detection.
    • DIncorrect. Include occurrence.

Systems Engineering, Analysis, and Design: FAQs

How much of the FE exam is Systems Engineering, Analysis, and Design?

Systems Engineering, Analysis, and Design is 8% of the FE exam by the official exam guide's weighting, which on a 110-question form works out to roughly 9 questions. The real exam's exact split varies by form.

What does the Systems Engineering, Analysis, and Design domain cover?

Engineering whole systems across their life: requirements, functional analysis, system design, reliability, configuration management and risk.

How should I study Systems Engineering, Analysis, and Design for FE?

Practise reducing mixed series and parallel block diagrams to a single reliability value; work from the innermost group outwards.

Where can I practise more Systems Engineering, Analysis, and Design questions?

This page has 10 free Systems Engineering, Analysis, and Design questions with answers. The ExamWize FE question bank has 48 questions in this domain. Every practice exam result breaks your score down by domain, and Review Mode re-drills the questions you missed.

Get Systems Engineering, Analysis, and Design exam-ready

The full FE bank has 48 Systems Engineering, Analysis, and Design questions. Timed practice exams match the real exam's length and domain weights, every result shows your score per domain, and Review Mode re-drills the questions you missed.

Not affiliated with NCEES; questions are original, written from the official exam outline, and never copied from the real exam.