First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Model concepts and organization
In SysML, which element is the primary structural unit used to represent a system or component and to own its parts, ports, and behavior?
- ValueType
- ConstraintProperty
- Actor
- Block Correct answer.
Explanation
A Block is the fundamental structural element in SysML, analogous to a class, and it can own parts, ports, operations, and behaviors. Actors and value types do not serve as the general-purpose structural container for system decomposition.
Question 2Model concepts and organization
Which SysML relationship indicates that one block is a specialization of another, inheriting its features?
- Allocation
- Generalization Correct answer.
- Dependency
- Association
Explanation
Generalization is the SysML relationship that expresses inheritance, where the specific block inherits features from the more general block. Association links instances, dependency conveys a weaker usage relationship, and allocation maps model elements between domains.
Question 3Model concepts and organization
In a block definition diagram, what does a composition (black diamond) association convey about the relationship between a whole and its parts?
- The parts must be modeled as separate actors.
- The whole is a subtype of each part.
- The whole owns the parts and their lifetimes are tied to it. Correct answer.
- The parts can be shared among multiple wholes simultaneously.
Explanation
Composition is a strong form of aggregation in which the whole owns its parts, so the parts' existence is bound to the whole. Shared aggregation (white diamond) is the weaker form where parts may be shared among multiple wholes.
Question 4Model concepts and organization
A modeler needs to show that a 'Vehicle' block has a property 'wheels' typed by a 'Wheel' block with a multiplicity of 4. Which modeling construct directly expresses this?
- A part property on Vehicle typed by Wheel with multiplicity 4 Correct answer.
- A generalization from Vehicle to Wheel
- A value property on Wheel typed by Vehicle
- An actor named Wheel associated with Vehicle
Explanation
Part properties are the standard way to model owned components of a block, and multiplicity 4 specifies exactly four wheels. Generalization and value properties express inheritance or data typing, not structural containment with multiplicity.
Question 5Model concepts and organization
Which diagram in SysML is best suited to depict the internal structure of a block, showing its parts, ports, and connectors?
- Requirement diagram
- Package diagram
- Use case diagram
- Internal block diagram Correct answer.
Explanation
An internal block diagram (IBD) shows the internal structure of a single block, including its parts, ports, and the connectors between them. Use case, requirement, and package diagrams serve different purposes and do not depict internal component wiring.
Question 6Model concepts and organization
In an internal block diagram, what is the purpose of a connector between two ports?
- It shows that the parts communicate through those ports. Correct answer.
- It defines a generalization hierarchy between the ports.
- It declares a new block type.
- It assigns a requirement to the port.
Explanation
Connectors in an IBD represent communication paths between parts through their ports, indicating how items or signals flow. They do not create type hierarchies, assign requirements, or declare new block types.
Question 7Model concepts and organization
Which SysML element represents a point of interaction through which a block can exchange items or signals with its environment?
- ValueType
- Allocation
- Constraint
- Port Correct answer.
Explanation
A Port is a property of a block that specifies a distinct interaction point through which the block communicates with its surroundings. Constraints, value types, and allocations do not model interaction points.
Question 8Model concepts and organization
A modeler wants to reuse a set of common properties across several unrelated blocks without implying a subtype relationship. Which mechanism is most appropriate?
- Generalization from each block to a common supertype
- A shared interface block referenced by ports Correct answer.
- Copying the properties into each block manually
- A package import of the properties
Explanation
Interfaces (often modeled as blocks or interface blocks) let multiple blocks share a defined set of features without creating an inheritance relationship. Generalization would impose a subtype hierarchy, package import brings in namespaces rather than features, and manual copying duplicates rather than reuses.
Question 9Model concepts and organization
Which relationship should be used to show that a 'SafetyRequirement' is refined by a 'BrakeController' block?
- Trace
- Satisfy
- Derive
- Refine Correct answer.
Explanation
The refine relationship indicates that a model element provides more detailed specification or elaboration of a requirement. Satisfy indicates a design element fulfills a requirement, derive creates a new requirement, and trace is a general-purpose link.
Question 10Model concepts and organization
In SysML, which relationship is used when a design element fulfills a requirement?
- Allocate
- Compose
- Satisfy Correct answer.
- Generalize
Explanation
The satisfy relationship asserts that a model element meets or fulfills a requirement. Compose and generalize are structural relationships, and allocate maps elements between domains rather than asserting requirement fulfillment.
Question 11Model concepts and organization
Which diagram type is used to organize model elements into namespaces and show dependencies among them?
- Parametric diagram
- Package diagram Correct answer.
- Activity diagram
- Sequence diagram
Explanation
Package diagrams depict the namespace structure of a model, showing packages and the dependencies between them. Activity, sequence, and parametric diagrams focus on behavior and constraints rather than model organization.
Question 12Model concepts and organization
A modeler wants a package to reuse elements from another package without physically moving them. Which construct accomplishes this?
- Package import Correct answer.
- Allocation
- Package merge
- Element copy
Explanation
A package import makes the elements of a target package visible within the importing package without relocating them. Merge combines package contents, copying duplicates elements, and allocation maps between domains.
Question 13Model concepts and organization
Which view in a SysML model is intended to show a system's behavior over time as a sequence of interactions between parts?
- Package diagram
- Requirement diagram
- Sequence diagram Correct answer.
- Block definition diagram
Explanation
A sequence diagram depicts interactions as messages exchanged among lifelines ordered in time. Block definition, requirement, and package diagrams are structural or organizational and do not show time-ordered interaction.
Question 14Model concepts and organization
Which SysML construct is used to specify that a block's behavior can be described by a state machine?
- A classifier behavior assigned to the block Correct answer.
- A port with a flow property
- A part property typed by the state machine
- An allocation to the state machine
Explanation
A classifier behavior is a behavior owned by a classifier that specifies how instances of the classifier behave, and a state machine can serve in that role. Parts, ports, and allocations do not designate the owning block's behavior.
Question 15Model concepts and organization
In a parametric diagram, what does a constraint property bind together?
- Two packages through an import
- Value properties through constraint parameters Correct answer.
- Actors and use cases
- Two blocks in a generalization hierarchy
Explanation
Parametric diagrams show constraint properties whose parameters are bound to value properties, enabling engineering analysis. They do not express generalization, package imports, or use case associations.
Question 16Model concepts and organization
Which element in SysML is used to define a reusable type for quantities such as mass or length, including units?
- Port
- Block
- Constraint
- ValueType Correct answer.
Explanation
A ValueType defines a type for values, including quantity kinds and units, and is used to type value properties. Blocks model structural components, ports model interaction points, and constraints model rules.
Question 17Model concepts and organization
A modeler needs to show that a 'FlightController' block communicates with a 'Sensor' block through a specific interface. Which combination best expresses this?
- A requirement satisfied by Sensor
- A value property on Sensor typed by FlightController
- A port on each block typed by a shared interface block, joined by a connector Correct answer.
- A generalization from Sensor to FlightController
Explanation
Ports typed by a shared interface block, connected by a connector, express that two blocks communicate through a defined interface. Generalization, value properties, and requirement satisfaction do not model interface-based communication.
Question 18Model concepts and organization
When modeling a system hierarchy, which relationship most directly represents that a subsystem is a structural component of a larger system?
- Refine
- Composition Correct answer.
- Dependency
- Generalization
Explanation
Composition expresses that a subsystem is an owned part of the larger system, with lifetime dependency. Generalization expresses inheritance, dependency a weaker usage link, and refine elaborates a requirement.
Question 19Model concepts and organization
Which statement best describes the relationship between a block definition diagram and an internal block diagram for the same block?
- The IBD replaces the BDD for behavioral modeling.
- The BDD shows message sequences that the IBD summarizes.
- The BDD shows the block's definition and relationships, while the IBD shows its internal structure. Correct answer.
- The IBD defines new block types that the BDD cannot show.
Explanation
A block definition diagram presents the definition of blocks and their relationships, while an internal block diagram presents the internal structure of a single block with its parts and connectors. The two views are complementary, not replacements for each other.
Question 20Model concepts and organization
Which SysML element is used to capture a textual statement of a capability or condition that the system must meet?
- Port
- Connector
- Block
- Requirement Correct answer.
Explanation
A Requirement is a SysML element that captures a text-based statement of a capability or condition the system must satisfy, and it can be related to design elements. Blocks, ports, and connectors are structural elements, not requirement statements.
Question 21Model concepts and organization
A modeler creates a 'Vehicle' block and a 'Car' block and draws a generalization arrow from Car to Vehicle. What does this assert?
- Car inherits the features of Vehicle. Correct answer.
- Car and Vehicle are the same block.
- Car is a part of Vehicle.
- Vehicle is a part of Car.
Explanation
A generalization arrow from Car to Vehicle means Car is the specific classifier and inherits features from the general classifier Vehicle. It does not express composition, reversal of containment, or identity of the two blocks.
Question 22Model concepts and organization
Which modeling approach best supports traceability from requirements to design elements in a SysML model?
- Using satisfy and derive relationships between requirements and design elements Correct answer.
- Placing all requirements in a single package with no relationships
- Embedding requirement text in block names
- Modeling requirements only as comments
Explanation
Traceability is achieved by relating requirements to design elements through relationships such as satisfy and derive, which can be queried and visualized on requirement diagrams. Isolating requirements, encoding them in names, or using comments does not provide queryable traceability.
Question 23Model concepts and organization
In SysML, which relationship type is used to map model elements from one domain (such as requirements) to another (such as design)?
- Composition
- Association
- Allocation Correct answer.
- Generalization
Explanation
Allocation is a cross-cutting relationship that maps elements between domains, such as allocating requirements to design elements or functions to components. Generalization, composition, and association express structural or inheritance relationships within a domain.
Question 24Model concepts and organization
A modeler wants to capture that a 'PowerSupply' block provides a specific voltage through a port. Which element combination best models this?
- A requirement satisfied by Voltage
- An actor named Voltage associated with PowerSupply
- A flow property on a port typed by a voltage value type Correct answer.
- A generalization from PowerSupply to Voltage
Explanation
A flow property on a port specifies the kind of item that can flow through that port, and typing it by a voltage value type captures the voltage characteristic. Generalization, actors, and requirements do not model item flow through a port.
Question 25Model concepts and organization
Which diagram type would best show how a system's functions are allocated to its structural components?
- Allocation relationship shown on a block definition or internal block diagram Correct answer.
- Package diagram
- Use case diagram
- Sequence diagram
Explanation
Allocations between functions and structural components are typically shown using allocation relationships on block definition or internal block diagrams. Use case, sequence, and package diagrams do not primarily depict function-to-component allocation.
Question 26Purposes and benefits of modeling a system
In an MBSE context, which statement best describes the primary purpose of building a system model rather than relying only on document-based specifications?
- To satisfy a regulatory requirement that models exist
- To provide a single coherent, verifiable representation that integrates requirements, structure, and behavior across the lifecycle Correct answer.
- To generate the final contractual documents that replace all engineering review meetings
- To reduce the number of stakeholders who need to review the design
Explanation
A system model's core value is integrating disparate views-requirements, structure, behavior, and parametrics-into one consistent representation that can be analyzed and verified across the lifecycle. Documents remain necessary but are derived outputs, not replaced entirely.
Question 27Purposes and benefits of modeling a system
A program manager asks why the team should invest in SysML models for a new product line. Which benefit most directly addresses managing complexity across many interacting subsystems?
- Guaranteeing the product will pass all physical testing on the first attempt
- Automatically generating manufacturing tooling from the model
- Enabling precise, shared abstractions that expose interfaces and dependencies among subsystems Correct answer.
- Removing the need for systems engineers once the model is complete
Explanation
Models manage complexity by providing precise, shared abstractions that make interfaces and dependencies explicit and reviewable. They support but do not guarantee physical test success, and they do not eliminate the need for engineers.
Question 28Purposes and benefits of modeling a system
Which outcome is most characteristic of using a model as a communication medium among a cross-disciplinary team?
- Each discipline keeps its own private notation and shares only summary slides
- Stakeholders review a common, unambiguous representation instead of interpreting separate prose documents Correct answer.
- Ambiguity is intentionally preserved to allow flexible interpretation
- Communication is deferred until the design is fully frozen
Explanation
A shared model gives disciplines a common, precise reference so that reviews focus on the design rather than on reconciling inconsistent wording. It reduces, rather than preserves, ambiguity and supports earlier communication.
Question 29Purposes and benefits of modeling a system
How does a system model typically support requirements traceability compared with a document-only approach?
- Traceability is achieved by placing all requirements in a single appendix
- Requirements are traced implicitly through reviewer memory
- Requirements can be linked explicitly to model elements that satisfy or verify them, allowing impact analysis when either changes Correct answer.
- Traceability is only possible after the product is delivered
Explanation
Model-based traceability creates explicit links between requirements and the design or verification elements, enabling systematic impact analysis. Document approaches can trace too, but the explicit, queryable links are a distinguishing model benefit.
Question 30Purposes and benefits of modeling a system
A team wants to evaluate a design against performance budgets before committing to hardware. Which modeling purpose does this most directly represent?
- Using models only for user-interface mockups
- Using models to replace the verification phase entirely
- Using models purely as a documentation archive
- Using parametric and analytical models to assess performance and trade-offs early Correct answer.
Explanation
Parametric and analytical modeling lets teams evaluate performance, constraints, and trade-offs before hardware exists. This early analysis reduces risk and informs design decisions, but it complements rather than replaces verification.
Question 31Purposes and benefits of modeling a system
Which statement best captures why models are described as enabling 'early verification' of a system design?
- Models are verified only after final integration
- Behavioral and analytical models can be executed or simulated to detect inconsistencies before physical prototypes exist Correct answer.
- Models automatically certify compliance with all standards
- Models eliminate the need to define acceptance criteria
Explanation
Executable or simulatable models let engineers detect inconsistencies and validate behavior early, when changes are inexpensive. Acceptance criteria are still needed, and certification remains a separate activity.
Question 32Purposes and benefits of modeling a system
During a design review, an engineer points out that a model change to one interface immediately revealed affected requirements and test cases. Which modeling benefit does this illustrate?
- Reduced need for configuration management
- Faster hardware fabrication
- Automated impact analysis through explicit relationships among model elements Correct answer.
- Elimination of the interface control document process
Explanation
Explicit relationships let tools traverse links to show what a change affects, which is impact analysis. Configuration management is still required, and interface control processes remain relevant.
Question 33Purposes and benefits of modeling a system
Why is a model often considered more precise than natural-language prose for specifying system behavior?
- Modeling languages permit any interpretation the reader prefers
- Prose is always shorter and therefore clearer
- The modeling language has defined semantics that constrain interpretation, reducing ambiguity Correct answer.
- Models cannot express behavior, so prose is preferred
Explanation
A modeling language has defined syntax and semantics, so constructs mean the same thing to all readers. Prose is flexible and therefore prone to divergent interpretation, which models help reduce.
Question 34Purposes and benefits of modeling a system
A stakeholder asks how modeling supports managing requirements volatility over a multi-year program. Which answer is most accurate?
- Explicit links and a single source model make it faster to assess and propagate the effects of requirement changes Correct answer.
- Models freeze requirements so they cannot change
- Models guarantee that no requirement will be renegotiated
- Models remove the need for change control boards
Explanation
Volatility is managed, not eliminated: explicit relationships let teams assess impact and propagate changes consistently. Change control and negotiation remain part of the process.
Question 35Purposes and benefits of modeling a system
Which scenario best demonstrates using a system model to support decision-making rather than documentation?
- Storing meeting minutes as model comments
- Renaming model packages to match the org chart
- Comparing simulated alternatives against weighted criteria to select an architecture Correct answer.
- Printing the model as a PDF for the project archive
Explanation
Decision support means using the model analytically-for example, evaluating alternatives against criteria-to inform a choice. Archiving, storing minutes, and reorganizing packages are documentation or housekeeping activities.
Question 36Purposes and benefits of modeling a system
How do system models typically improve consistency across multiple engineering views such as structure, behavior, and requirements?
- Each view is authored independently and reconciled only at delivery
- Consistency is achieved by prohibiting changes after baseline
- Views are kept consistent by manual proofreading alone
- Shared model elements are referenced across views, so a change in one view is reflected wherever that element appears Correct answer.
Explanation
When views reference the same underlying elements, consistency is maintained by construction rather than by reconciliation. Manual proofreading or late reconciliation is exactly what integrated modeling reduces.
Question 37Purposes and benefits of modeling a system
An organization claims its models will 'eliminate risk.' Which critique is most consistent with sound MBSE practice?
- Models are irrelevant to risk management
- Models reduce and reveal risk by exposing assumptions and dependencies, but they cannot eliminate risk Correct answer.
- Models eliminate risk because simulation is always accurate
- Models eliminate risk only if no one changes the design
Explanation
Modeling makes assumptions, interfaces, and dependencies visible so risks can be identified and mitigated earlier. It cannot remove risk, and simulation fidelity is itself a source of uncertainty.
Question 38Purposes and benefits of modeling a system
Which benefit of modeling most directly supports reuse of engineering knowledge across product variants?
- Restarting each variant from a blank document
- Reusable model libraries and patterns that capture proven designs and interfaces Correct answer.
- Avoiding any standardization of notation
- Storing all knowledge in individual engineers' notes
Explanation
Reusable libraries and patterns let teams carry proven designs, interfaces, and constraints forward to new variants. Personal notes, blank restarts, and non-standard notation all work against reuse.
Question 39Purposes and benefits of modeling a system
A team uses a model to generate consistent documentation and reports automatically. Which underlying modeling benefit does this rely on?
- The assumption that prose documents are never needed
- The elimination of stakeholder review
- The ability of models to predict market demand
- A structured, machine-readable repository from which views and documents can be derived Correct answer.
Explanation
Derived documentation depends on a structured repository whose content can be queried and rendered. This complements, rather than removes, documentation and review needs.
Question 40Purposes and benefits of modeling a system
Which statement best explains how modeling supports verification planning?
- Verification coverage cannot be assessed from a model
- Model elements can be linked to verification methods and test cases, making coverage gaps visible Correct answer.
- Verification is planned only after all testing is complete
- Models remove the need to define verification methods
Explanation
Linking requirements and design elements to verification methods and test cases lets teams see which items are covered and where gaps exist. Verification planning therefore benefits from explicit model relationships.
Question 41Purposes and benefits of modeling a system
A program is distributed across suppliers who use different tools. Which modeling-related practice most improves shared understanding across that boundary?
- Agreeing on a standard modeling language and exchange format for interfaces and requirements Correct answer.
- Sharing only final test reports
- Relying on verbal agreements at kickoff meetings
- Allowing each supplier to invent its own notation
Explanation
A common language and exchange format let distributed teams exchange precise, tool-independent model content. Idiosyncratic notations, late reports, and verbal agreements all increase misunderstanding risk.
Question 42Purposes and benefits of modeling a system
Which statement best describes how a system model supports the 'single source of truth' concept?
- Authoritative information is held once in the model and referenced by views, rather than duplicated across documents Correct answer.
- The model is updated only at project closeout
- Each engineer maintains a private authoritative copy
- Every document is treated as equally authoritative and never reconciled
Explanation
A single source of truth means authoritative content lives in one place and is referenced elsewhere, preventing divergence. Duplicated or private copies and late updates undermine this.
Question 43Purposes and benefits of modeling a system
An engineer argues that because the model is 'just a picture,' it adds no value over a slide deck. Which rebuttal is most accurate?
- Models and slides are identical in every respect
- Slides cannot be shared with stakeholders
- Pictures are always more accurate than models
- A model is a structured repository with semantics and relationships that can be queried and analyzed, unlike a static picture Correct answer.
Explanation
The value lies in underlying semantics and relationships, which enable queries, analysis, and consistency checks that a static image cannot provide. A diagram is only one rendering of the model.
Question 44Purposes and benefits of modeling a system
Which combination best explains why modeling can lower total lifecycle cost despite upfront investment?
- Modeling costs are always zero after the first year
- Rework costs are unaffected by when defects are found
- Earlier defect detection and reduced rework offset the cost of building and maintaining the model Correct answer.
- Models remove all engineering labor from the program
Explanation
The economic case rests on finding and fixing defects earlier, when change is cheaper, plus reduced rework and better reuse. Modeling does not remove labor, and defect timing strongly affects cost.
Question 45Purposes and benefits of modeling a system
A team's model has become so detailed that reviews take longer and stakeholders stop engaging. Which modeling principle is most relevant to this problem?
- Remove all abstraction so every detail is visible to everyone
- Abandon modeling and return to prose
- Always model every element to the lowest level of detail
- Tailor model scope, abstraction, and views to the purpose and audience of each review Correct answer.
Explanation
Models should be purpose-driven: abstraction and views are selected to serve the audience and decision at hand. Excessive detail for the wrong audience defeats communication and review efficiency.
Question 46Purposes and benefits of modeling a system
Which statement best captures the relationship between a system model and the system it represents?
- The model is a purposeful abstraction that omits details irrelevant to the questions it is meant to answer Correct answer.
- The model is valid only if it includes every stakeholder's opinion
- The model is a complete one-to-one copy of every physical detail
- The model is unrelated to the real system and purely decorative
Explanation
A model is an abstraction chosen to answer specific questions, deliberately omitting irrelevant detail. It is neither a complete copy nor unrelated to the system it represents.
Question 47Purposes and benefits of modeling a system
Which benefit most directly explains why modeling improves traceability from stakeholder needs to verification evidence?
- Verification evidence is unnecessary once a model exists
- Traceability is achieved by filing documents in numbered folders
- End-to-end relationships can be traversed so that each need is linked through design to the evidence that satisfies it Correct answer.
- Stakeholder needs are traced only at the start of the program
Explanation
Traversable end-to-end relationships let teams confirm that each need is addressed and verified. Folder numbering and one-time tracing do not provide this continuous, queryable linkage.
Question 48Purposes and benefits of modeling a system
Which statement best describes how modeling supports stakeholder communication with non-technical audiences?
- Every audience must read the full model repository
- Non-technical audiences cannot benefit from models
- Selected views and abstractions can be tailored to show only what each audience needs to understand Correct answer.
- Models are only meaningful to the engineers who built them
Explanation
Tailored views let modelers present relevant abstractions to different audiences, making models accessible beyond the modeling team. Requiring everyone to read the full repository is impractical.
Question 49Purposes and benefits of modeling a system
Which statement best explains the role of modeling in supporting system-of-systems understanding?
- Models are limited to a single subsystem and cannot show context
- System-of-systems behavior is unpredictable and cannot be modeled at all
- Models make interfaces and dependencies among constituent systems explicit so emergent behavior can be analyzed Correct answer.
- Models assume constituent systems never interact
Explanation
Making interfaces and dependencies explicit allows analysis of interactions and emergent behavior across constituent systems. Assuming no interaction or refusing to model context defeats the purpose.
Question 50Purposes and benefits of modeling a system
A reviewer asks what 'purpose-driven modeling' means in practice. Which answer is most accurate?
- Modeling only what is easiest to draw
- Modeling every conceivable aspect regardless of need
- Choosing what to model, at what fidelity, based on the questions the model must answer Correct answer.
- Letting the tool decide the model content automatically
Explanation
Purpose-driven modeling aligns scope and fidelity with the questions the model must answer, avoiding wasted effort and irrelevant detail. Modeling everything or only what is easy both miss the intent.