CLD-R Exam 2 Q8 ambiguity

[nanocyte]

8. Which of the following is a risk if you execute the following code on a system with the default LabVIEW settings?
a. A memory leak could result from writing the filtered data to the text file
b. The VI will not finish execution unless the Mouse Down? event occurs for the OK Button
c. The While Loop does not stop execution in the event of an error in the Mouse Down? Event case
d. LabVIEW will not update the front panel activity while the Mouse Down? event is executing

C is the correct answer. There's no shift register on the for loop, so an error that occurs in an earlier iteration but clears up before the last itteration won't propagate out and won't stop the while loop

D is not true. Front panel activity (perhaps from a calling VI) can continue to occur.

[nanocyte]

E1 Q26

26. What method of testing is shown in the figure below?
a. Functional testing
b. Usability testing
c. Stress testing
d. Performance testing

Seems like this could be functional testing if a higher level VI is checking the output.

Could also be performance testing if the tester wanted to be sure a certain number of iterations completed in a certain amount of time.

Is there a reference to what is "stress testing" in the context of LabVIEW? Usually software doesn't fail under "stress"

[JÞB]

---

@nanocyte wrote:

8. Which of the following is a risk if you execute the following code on a system with the default LabVIEW settings?
a. A memory leak could result from writing the filtered data to the text file
b. The VI will not finish execution unless the Mouse Down? event occurs for the OK Button
c. The While Loop does not stop execution in the event of an error in the Mouse Down? Event case
d. LabVIEW will not update the front panel activity while the Mouse Down? event is executing

C is the correct answer. There's no shift register on the for loop, so an error that occurs in an earlier iteration but clears up before the last itteration won't propagate out and won't stop the while loop

D is not true. Front panel activity (perhaps from a calling VI) can continue to occur.

---

Again, you might want to check out the help.... that is a Filter Event with the right node unwired.... yup 

[nanocyte]

Are you saying "the front panel activity" refers only to the "OK button" front panel control? That is horrible phrasing if so. The most natural interpretation would be that the entire UI will be frozen. There will be no front panel activity. Which is not true. The front panel is still active and can receive updates from, say, a calling VI.

[Freelance_LV]

Hi

I believe option D to be the answer.

Option A is not likely.

The chances of option B to be the answer depend on an error being generated.

The Open/Create/Replace File function before the while loop most likely would generate an error.

The default setting for this function is to Open a file and I have had errors due to not changing this setting to Open or Create each time. So I would guess this would generate an error.

For option C, the loop WILL stop when an error occurs either in the Mouse Down? event or before entering the while loop.

Option D is definitely true. Events are configured by default to Defer user activity till the event is processed.

[nanocyte]

D doesn't say "User activity will be deferred" it says LabVIEW won't update the front panel, which is not inherently true. Front panel updates could occur if generated. For example, a calling VI could change the panel color.

Meanwhile, C could be checking if the test taker knows what proper error handling looks like (they should use a shift register).

[BrenS]

Hi,

For option C, you state the "loop WILL stop" - are you referring to the For loop?

Cheers.

(Running LV 2017) 

I built the For loop portion of the code and as long as the error wires are connected, the error (set True at the beginning of the for loop) will be passed into the For loop and then out of the For loop and reported in the Error Out indicator at the end. If the error wires are disconnected after the "write to text file" VI, Labview then stops and reports an error "Error 12 occurred at an unidentified location" and lets the user stop the code.