It's not common to use the password input to exit applications.
Sticking to a more standard behaviour and have an exit button instead is always good, it will make it easier for the user to anticipate how things are to work (no need to write an explanation on the panel...). I have attached a slightly modified version of the VI.
Some other tips:
Try to avoid the caps lock so much and stick to the dialog controls if you want the software to look professional.
Let the sub-VI connectors follow a from left to right design (inputs on the left, outputs on the right). It's often convenient to always use the same connector panel, e.g. to standardize on the 20 connector option. That way adding inputs and/or outputs later will not require a change.
On
ly use sequences when they are needed (lot's of messages on why here on the zone), in the password example you can use data flow instead.
Hightlight the password input so that the user can start typing in the password straight away. In the attached example highlighting when the password is found to be incorrect would also be nice, but hightlighting and events are not always good friends it seems.
Windows can often look better if you use the "Golden Cut" by the way, i.e. make the relationship between the width and hight of the windows equal to 1,618 ("Phi").