CTA Security & User Management Flashcards
6 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 6 CTA Security & User Management flashcards as text
In a regulated manufacturing environment, which TestStand audit capability records what parameter values were changed and by whom?
Answer: Change audit trail tied to user login and Station Options modifications
The TestStand change audit trail logs configuration and parameter changes alongside the authenticated user's identity, providing the required traceability.
Which TestStand mechanism allows an architect to require re-authentication after a configurable idle timeout, meeting security policy requirements?
Answer: TestStand Login Options idle timeout with re-login prompt
The idle timeout setting in TestStand Login Options automatically prompts for re-authentication after a set period of inactivity.
A CTA architect must ensure that removing a user from TestStand User Manager does not affect historical test results attributed to that user. How is this handled?
Answer: User names are stored as strings in result records independent of the live account
TestStand stores the user name as a string in each result record at the time of the run, so historical records remain intact even if the account is later removed.
Which security practice should a CTA architect implement to protect TestStand sequence files stored on a network share from unauthorized modification?
Answer: Share files in read-only mode for all station users; only the deployment system has write access
Granting station users read-only access and restricting write access to the deployment system ensures unauthorized users cannot alter the production sequence files.
When implementing a dual-authorization ('two-person rule') workflow in TestStand, which mechanism is typically used to require a second user's credentials before proceeding?
Answer: A custom sequence step that prompts for a second user's TestStand login via the Engine API
A custom sequence step uses the TestStand Engine API to present a second login dialog, verifying the second user's credentials programmatically before allowing the sequence to continue.
What is the significance of the TestStand 'Run As' feature in the context of station security?
Answer: It allows the TestStand engine to execute tests under a specific user context for privilege isolation
The 'Run As' capability lets the architect configure which Windows user context the TestStand engine runs under, enabling OS-level privilege isolation from the operator's session.