In this lab, we$-$investigate the$-$management$-$of a $-$notional$*($and$-$very$-$simplified$).$VLAN$-$based$-$distribution$-$layerbackbone$-$network.$-$The$-$startup$-$software$-$development$-$firm$-$you work for$-$occupies$-$three.floors$-$of an officebuilding. The firm is$-$structured$-$as$-$a matrixed$-$organization, with development teams$-$composed$-$of a software engineer.$($SE$),$ a$.$tester$/$quality assurance engineer$*($QA$),$ and$*$a$-$marketing$/$sales$/$business$-$developmentrepresentative $($MSB$)..$ These$-$teams$-$sit together in bullpen areas, with $2.$teams on each floor. $-$This integratedproduct team approach works well $-$in$-$many ways, but presents a challenge for network administration. While traditional$-$networks$-$are often$-$segmented according to physical$-$location, this$-$network needs to be$-$segmentedaccording to function, with the$-$SE$,$ QA and$-$MSB members being connected to their own function$-$orientedsubnets.$-$Fortunately, the building has already been equipped with a$.$VLAN$-$capable$-$switch on each floor, with VLAN$-$Switch $1-$including a connection to a traditional$-$router, as pictured in the figure. $-$The router includes$-$NATcapability, assigning private.IP$-$addresses within the building$-$network$-$in the$-192\mathrm{.}168.$x$.$x$-$range.q