Architecture & Framework Flashcards
7 cards from real CTA practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Architecture & Framework flashcards as text
In a CTA-level TestStand deployment, what is the recommended approach for distributing a custom process model to multiple test stations?
Answer: Package the process model in a TestStand deployment package and install on each station
TestStand deployment packages bundle all required files and register them correctly on each target station, ensuring consistent configuration across the fleet.
What architectural decision determines whether a custom step type should store its properties in the step type definition versus in the step instance?
Answer: Properties that are the same for every instance belong in the type; instance-specific values belong in the step instance
Shared defaults and schema belong in the type definition, while values that vary per usage (like limit values or signal names) belong at the step instance level.
How does TestStand's 'Expression' data type differ from a 'String' data type when used for step properties?
Answer: Expressions are evaluated at runtime against the current sequence context; strings are literal values
Expression properties are evaluated at runtime, allowing dynamic references to variables and calculations, while string properties are treated as static literal text.
Which TestStand feature enables you to reuse the same sequence file across multiple products with different limit values without modifying the sequence?
Answer: Property Loader step with external limit files (CSV, XML, MDB)
The Property Loader step reads limits and properties from external files at runtime, enabling the same sequence to serve multiple product variants by swapping the limits file.
In the TestStand execution model, what is the difference between 'Terminate' and 'Abort' when stopping an execution?
Answer: Terminate runs Cleanup steps before stopping; Abort stops immediately without Cleanup
Terminate gracefully stops the execution after running Cleanup step groups, while Abort halts immediately without executing Cleanup, potentially leaving resources unreleased.
When architecting a TestStand system for regulatory compliance (e.g., FDA 21 CFR Part 11), which built-in feature primarily addresses the electronic records requirement?
Answer: Audit Trail logging of all sequence modifications and execution events
TestStand's Audit Trail feature logs all changes to sequence files and execution events with timestamps and user identity, satisfying electronic records traceability requirements.
What is the primary architectural benefit of separating test logic into multiple sequence files rather than one monolithic sequence file?
Answer: It enables independent versioning, reuse, and team-parallel development of test modules
Splitting test logic across multiple sequence files promotes modularity, allowing independent version control, reuse across products, and parallel development by multiple engineers.