Refer to the exhibit. An engineer configures VRRP and issues the show commands to verify operation. What does the engineer confirm about VRRP group 1 from the output?
A.
Communication between VRRP members is encrypted using MD5.
B.
There is no route to 10.10.1.1/32 in R2's routing table.
C.
R1 is primary if 10.10.1.1/32 is in its routing table.
D.
If R1 reboots, R2 becomes the primary virtual router until R2 reboots.
Option A is incorrect.
The authentication type is cleartext; 'text' keyword is being used.
We can use md5 authentication by using 'authentication md5' command.
Option B is incorrect, and irrelevant to the context of our question.
We need to use 'show ip route' command to display R2's routing table and confirm.
Option C is correct.
We will track the reachability to IP address '10.10.1.1' in its routing table and if it's not reachable by R1, R1's priority will decrement by 20. This will set R1's priority to '90' making it less than R2's default priority (100,) and R2 becomes the active router.
Option D is incorrect
If R1 reboots, R2 becomes the primary virtual router until R1 comes back. (Tested in PT)
C is correct.
tricky question
b is completely wrong, there is nothing in the question that can be used to identify if b is correct or wrong.
D is correct until you remember that preemption is default in VRRP :D
C seems to be wrong at first, then you look at the track again to see that it's tracking the IP route entry in the routing table not pinging the ip
answer makes sense.
A- Wrong, its cleartext
B- Wrong, not enough information to infer this
C- Correct, if there is reachability to the network 10.10.1.1/32, R1's priority is default 100, which is equal to R2's priority of default 100, so what is the next tie breaker? the higher IP address, R1 wins, and with VRRP having preempt enabled by default, R1 becomes the Master.
D- Wrong
R1's prio is 110. When the tracked object fails, the prio is decremented by 20, lowering it below R2's default prio, 100. But C says when the route is installed (meaning reachable), so R1's prio remains 110, and master. Still C, nevertheless.
It is NOT D, Why ? Because preemption is enabled by default. Which means that if R1 reboots -> R2 will become primary and when R1 reboot is finished will take the role again because of the default preemption ! -> C seems right.
cisco_R3(config-subif)#do s runn interface Ethernet0/0.40
!
interface Ethernet0/0.40
encapsulation dot1Q 40
ip address 172.16.13.2 255.255.255.0
vrrp 10 ip 172.16.13.254
vrrp 10 track 4 decrement 20
end
cisco_R3(config-subif)#do s track 4
Track 4
IP route 5.5.5.55 255.255.255.255 reachability
Reachability is Down (no ip route)
1 change, last change 00:04:13
First-hop interface is unknown
Tracked by:
VRRP Ethernet0/0.40 10
cisco_R3(config-subif)#do s vrrp
Ethernet0/0.40 - Group 10
State is Master
Virtual IP address is 172.16.13.254
Virtual MAC address is 0000.5e00.010a
Advertisement interval is 1.000 sec
Preemption enabled <<<<<<<<<< by default, so it'll become MASTER after high priority
Priority is 80
Track object 4 state Down decrement 20
Master Router is 172.16.13.2 (local), priority is 80
Master Advertisement interval is 1.000 sec
Master Down interval is 3.609 sec
cisco_R3(config-subif)#
cisco_R3(config-subif)#
*Dec 23 20:51:51.008: %TRACK-6-STATE: 4 ip route 5.5.5.55/32 reachability Down -> Up
cisco_R3(config-subif)#
cisco_R3(config-subif)#do s track 4
Track 4
IP route 5.5.5.55 255.255.255.255 reachability
Reachability is Up (BGP)
2 changes, last change 00:00:41
First-hop interface is Ethernet0/0.10
Tracked by:
VRRP Ethernet0/0.40 10
cisco_R3(config-subif)#do s vrrp
Ethernet0/0.40 - Group 10
State is Master
Virtual IP address is 172.16.13.254
Virtual MAC address is 0000.5e00.010a
Advertisement interval is 1.000 sec
Preemption enabled
Priority is 100
Track object 4 state Up decrement 20
Master Router is 172.16.13.2 (local), priority is 100
Master Advertisement interval is 1.000 sec
Master Down interval is 3.609 sec
cisco_R3(config-subif)#
cisco_R3(config-subif)#do s ip ro 5.5.5.55
Routing entry for 5.5.5.55/32
Known via "bgp 3", distance 20, metric 0
Tag 5, type external
Last update from 192.168.255.55 00:01:21 ago
Routing Descriptor Blocks:
* 192.168.255.55, from 192.168.255.55, 00:01:21 ago
Route metric is 0, traffic share count is 1
AS Hops 4
Route tag 5
MPLS label: none
cisco_R3(config-subif)#
tricky question, I hate it ...
D. is true anyway,
C. is unclear, let's say what happens if this route flaps? after that R2 will be master anyway cos no feature PREEMPTION is configured on R1... right?
I believe D is correct because preemption is enabled in VRRP by default.
The answer C says " if 10.10.1.1/32 is in its routing table." if this route is statically configured it will still be there disregarding its reachability.
C is correct because of the tracking feature. Exhibit speaks nothing about availability of routes, so we can not tell which routes are available or not available.
A believe it is C. By ''sh run int fa0/0'' command we are not able to tell if route is in routing table or not. On router 1 is configured IP SLA which is tracking reachability to 10.10.1.1 - so if this route is unavailable, routers 1 priority decrements and it becomes Secondary, but if the route is reachable it will stay Primary because of its 110 priority.
there was no output regarding routing table, so you can't say if yes or no
upvoted 3 times
...
...
This section is not available anymore. Please use the main Exam Page.350-401 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
AbdullahMohammad251
7 months, 1 week ago[Removed]
10 months, 3 weeks ago[Removed]
10 months ago[Removed]
1 year, 9 months agoteikitiz
1 year, 9 months agoechipbk
2 years, 3 months agokewokil120
2 years, 3 months agoJohn13121
2 years, 3 months agonushadu
2 years, 3 months agonushadu
2 years, 3 months agonushadu
2 years, 3 months agonushadu
2 years, 4 months agoXerath
2 years, 4 months agoKOJJY
2 years, 4 months agoInzo
2 years, 4 months agoFeliphus
2 years, 4 months agotinoe
2 years, 6 months agoonkel_andi
2 years, 6 months agomelkij17
2 years, 6 months agoWooker
2 years, 6 months agoWooker
2 years, 6 months agocivan
2 years, 3 months agojdholmes423
2 years, 6 months agoH3kerman
2 years, 5 months ago