Free CLAD (NI) Questions and Answers — Questions and Answers
Question 1: How do you document a VI so that the summary shows up in the pop-up box for Show Context Help?
- Create a free label on the front panel
- Edit the LabVIEW help files
- Use the VI Properties Documentation window (Correct answer)
- Type in the Show Context Help window
Correct answer: Use the VI Properties Documentation window
Documentation typed into the VI Properties Documentation window is exactly what LabVIEW shows in the Context Help pop-up for that VI. A front-panel free label stays on the panel, editing LabVIEW's help files changes the application's manuals, and the Context Help window only displays text rather than accepting input.
Question 2: Can data be sent over a wire between parallel-running loops?
- NOT SURE
- NO (Correct answer)
- YES
- MAYBE
Correct answer: NO
No—under LabVIEW's dataflow model a wire imposes execution order between its endpoints, but parallel loops have no shared data-dependency, so you cannot simply wire data from one into the other. Passing data between independently running loops requires constructs such as queues, notifiers, or variables.
Question 3: Of the following, which best characterizes a Tab Control?
- A control that outputs ASCII values equal to the selected tab label
- A control that outputs a cluster of the controls / indicators on the tabs
- A controls that outputs the tab order of the controls on the front panel
- A type of enumerated control (Correct answer)
Correct answer: A type of enumerated control
A Tab Control is essentially an enumerated control—each tab maps to an integer value, the same way an enum's items do, and the control returns that value for the selected tab. The other options (ASCII output, cluster output, or tab-order output) do not describe how a Tab Control represents its data.
Question 4: What benefit does utilizing a Strictly Typed VI refnum offer?
- Causes dynamically loaded VIs to be loaded at the start of execution
- The data types of the target VI are known at compile time (Correct answer)
- The data types passed to the VI can change programmatically
- You can flatten the data to a string to improve code performance
Correct answer: The data types of the target VI are known at compile time
A Strictly Typed VI refnum locks in the connector-pane data types of the target VI, so those types are known at compile time, enabling compile-time type checking and safe Call By Reference. A weakly (non-strictly) typed refnum is what allows types to vary; strict typing does the opposite, and it has nothing to do with preloading VIs or flattening data to strings.
Question 5: A coercion dot signifies:
- Data values are being coerced because they are out of range
- A polymorphic operation will be performed on the data
- A data buffer is created to handle data conversion (Correct answer)
- The data types are consistent
Correct answer: A data buffer is created to handle data conversion
A coercion dot marks an automatic data-type conversion, and LabVIEW creates a buffer to store the converted copy of the value at that point. It does not indicate out-of-range values, matching/consistent types, or a polymorphic operation.
Question 6: Which of the subsequent cannot be used for data transfer?
- Local variables
- Semaphores (Correct answer)
- Queues
- Notifiers
Correct answer: Semaphores
Explanation: <br> Semaphores are not typically used to directly transfer data between different parts of a program or different threads. Semaphores are synchronization mechanisms used to control access to shared resources and coordinate the execution of multiple threads or processes.
Question 7: You need to change a control's run-time property. It is located on the front panel of a VI. Which of the following would you choose as your best course of action?
- Create a control reference, pass the reference to a property node and select the property to modify
- Create a linked shared variable and select the property to modify the property
- Create an implicit property node and select the property to modify (Correct answer)
- Create a local variable and select the property to modify
Correct answer: Create an implicit property node and select the property to modify
Because the control is on the same VI's own front panel, the simplest and best approach is an implicit property node, which is already tied to that control and needs no reference passed in. The control-reference-plus-property-node method also works but is the explicit form meant for accessing controls indirectly; local and shared variables modify values, not run-time properties.
Free CLAD (NI) Questions and Answers
How do you document a VI so that the summary shows up in the pop-up box for Show Context Help?