Does virtual server status affect the Order of precedence for virtual server matching?

If you have 2 virtual servers, VS1 (specific) and VS2 (general). In the case where the client request matches the more specific VS (VS1), and If VS1 status is DOWN (due to either pool down being disabled) and VS2 status is UP, will LTM choose VS2 or still pick VS1 (even if ot was in a DOWN status)?

 

Scenario

VS1: Src IP:port -> Any/Any -----Dst IP:Port -> 10.1.10.20:80 -----Status: DOWN

 

VS2: Src IP:port-> Any/Any -----Dst IP:Port -> 10.1.10.20:* ---------Status: UP

 

Client Request --> Dst: 10.1.10.20:80

 

Outcome in vlab ->LTM picked VS1 for processing traffic (which in turn sent a TCP RST (the RST is an expected behaviour)

 

However, according to an official F5 301a prep video -> LTM should choose VS2 since it is available and VS1 is down (even if VS1 was exactly matching)

 

So What I am seeing in my vlab is different to what was instructed in the official F5 video, which making me doubt whether my vlab VE is misbehaving.

 

So the general question is: Does a VS status play a role in the order of precedence for VS matching?

 

Appreciate your help.

 

PS: I am running VE v13 in my vlab.