Topic 11 Practice Test 2 covers NTP/PTP, NAT/PAT, HSRP, and VRRP for Cisco 350-401 ENCOR. For broader exam preparation, review the Cisco 350-401 ENCOR Exam Dumps. Every option includes focused technical reasoning explaining both the Cisco enterprise networking concept and its fit to the scenario.
Question 1
An enterprise switch change is being peer-reviewed. The design must identify the missing function when a router has correct IP reachability to a time server but never establishes an NTP association. Which option should be approved? Choose ONE.
- HSRP object tracking
- NTP client association
- NTP source interface
- PAT overload
Correct Answer(s)
B
Rationale
- HSRP object tracking is not selected because it governs gateway failover based on upstream health. That function belongs to HSRP tracking work. The required task is to identify the missing function when a router has correct IP reachability to a time server but never establishes an NTP association, and that task is handled by NTP client association.
- Select NTP client association for time synchronization from a designated NTP source. The stem makes the requirement explicit: identify the missing function when a router has correct IP reachability to a time server but never establishes an NTP association. That result is governed by this NTP mechanism rather than by the neighboring options. This makes NTP client association the direct fit for this case.
- NTP source interface is technically useful for stable NTP packet sourcing in NTP reachability work. The tested task is to identify the missing function when a router has correct IP reachability to a time server but never establishes an NTP association, however. That behavior is governed by NTP client association, making this option a distractor.
- PAT overload misses the controlling requirement because its result is many-to-one address conservation for outbound sessions. That fits PAT tasks. Here, the network needs engineers to identify the missing function when a router has correct IP reachability to a time server but never establishes an NTP association, so NTP client association is the relevant mechanism.
Question 2
A post-change check found a specific production issue. The engineer now needs to remediate a clock that accepts updates from an unintended NTP server despite a requirement to trust only approved sources. Which choice best resolves it? Choose ONE.
- NAT inside interface role
- VRRP priority and preemption
- PTP grandmaster clock
- NTP authentication
Correct Answer(s)
D
Rationale
- NAT inside interface role solves the wrong problem by producing correct identification of the private-side NAT boundary. It fits NAT direction needs, but the tested task is to remediate a clock that accepts updates from an unintended NTP server despite a requirement to trust only approved sources. That requirement maps directly to NTP authentication.
- VRRP priority and preemption provides preferred VRRP primary selection, which belongs to VRRP election decisions. The stem instead requires engineers to remediate a clock that accepts updates from an unintended NTP server despite a requirement to trust only approved sources. That result comes from NTP authentication; selecting VRRP priority and preemption would leave the tested condition unresolved.
- PTP grandmaster clock is not an equivalent substitute because it creates an authoritative precision-time origin. That serves PTP needs, not the requirement to remediate a clock that accepts updates from an unintended NTP server despite a requirement to trust only approved sources. NTP authentication acts on the condition described in the stem.
- NTP authentication is appropriate because the result is authenticated time synchronization. The scenario requires engineers to remediate a clock that accepts updates from an unintended NTP server despite a requirement to trust only approved sources. This feature controls that NTP security behavior specifically, so it is the best fit. This makes NTP authentication the direct fit for this case.
Question 3
An infrastructure engineer is correcting a production condition. The objective is to explain how to keep a designated NTP server favored without deleting a healthy backup association. Which option should be implemented? Choose ONE.
- NTP preferred server
- VRRP object tracking
- PTP boundary clock
- NAT outside interface role
Correct Answer(s)
A
Rationale
- Choose NTP preferred server because its result is deterministic preference among valid NTP sources. The stem requires the team to explain how to keep a designated NTP server favored without deleting a healthy backup association. That is a direct NTP selection match, not merely a related feature. This makes NTP preferred server the direct fit for this case.
- VRRP object tracking is technically useful for VRRP failover tied to path health in VRRP tracking work. The tested task is to explain how to keep a designated NTP server favored without deleting a healthy backup association, however. That behavior is governed by NTP preferred server, making this option a distractor.
- PTP boundary clock is related but operationally wrong because it yields segmented PTP timing distribution. That supports PTP work. This case requires engineers to explain how to keep a designated NTP server favored without deleting a healthy backup association, so NTP preferred server fits the stated condition.
- Do not select NAT outside interface role; its effect is correct identification of the public-side NAT boundary, a valid NAT direction function. The scenario requires engineers to explain how to keep a designated NTP server favored without deleting a healthy backup association. That requirement maps to NTP preferred server, not to this alternative.
Question 4
A campus engineer is preparing a controlled change. The requirement is to fix NTP packets rejected by an ACL because they leave with the physical-interface address instead of the registered loopback address. Which choice most directly satisfies that requirement? Choose ONE.
- NAT match ACL
- PTP transparent clock
- NTP source interface
- NTP client association
Correct Answer(s)
C
Rationale
- NAT match ACL is a neighboring feature that yields correct selection of addresses that should be translated for NAT policy needs. This scenario requires the team to fix NTP packets rejected by an ACL because they leave with the physical-interface address instead of the registered loopback address. The required behavior belongs to NTP source interface, so this alternative is mismatched.
- PTP transparent clock would change forwarding-delay compensation for PTP, which is appropriate in PTP scenarios. The present stem asks engineers to fix NTP packets rejected by an ACL because they leave with the physical-interface address instead of the registered loopback address. That is why NTP source interface is the correct mechanism instead.
- NTP source interface directly produces stable NTP packet sourcing. That is relevant because the team needs to fix NTP packets rejected by an ACL because they leave with the physical-interface address instead of the registered loopback address. For this NTP reachability decision, the feature changes the condition identified by the evidence. This makes NTP source interface the direct fit for this case.
- NTP client association is not an equivalent substitute because it creates time synchronization from a designated NTP source. That serves NTP needs, not the requirement to fix NTP packets rejected by an ACL because they leave with the physical-interface address instead of the registered loopback address. NTP source interface acts on the condition described in the stem.
Question 5
An enterprise switch change is being peer-reviewed. The design must identify which PTP role should originate time after the current best clock is selected for the precision domain. Which option should be approved? Choose ONE.
- static inside source NAT
- NTP authentication
- PTP grandmaster clock
- show ip nat translations
Correct Answer(s)
C
Rationale
- Static inside source NAT should not be changed for this issue; it provides a fixed private-to-public address mapping for NAT cases. The actual requirement is to identify which PTP role should originate time after the current best clock is selected for the precision domain, which is handled by PTP grandmaster clock.
- NTP authentication is related but operationally wrong because it yields authenticated time synchronization. That supports NTP security work. This case requires engineers to identify which PTP role should originate time after the current best clock is selected for the precision domain, so PTP grandmaster clock fits the stated condition.
- The required mechanism is PTP grandmaster clock, which gives an authoritative precision-time origin. The stem calls for the team to identify which PTP role should originate time after the current best clock is selected for the precision domain. That makes this the direct PTP answer rather than an adjacent workaround. This makes PTP grandmaster clock the direct fit for this case.
- Show ip nat translations does not resolve the requirement; it provides direct inspection of active NAT mappings for NAT verification decisions. Because the stem requires engineers to identify which PTP role should originate time after the current best clock is selected for the precision domain, PTP grandmaster clock is the mechanism that should be selected.
Question 6
A post-change check found a specific production issue. The engineer now needs to choose the PTP role that can synchronize upstream on one port and distribute timing downstream on another segment. Which choice best resolves it? Choose ONE.
- dynamic NAT pool
- PTP boundary clock
- HSRP virtual IP
- NTP preferred server
Correct Answer(s)
B
Rationale
- Dynamic NAT pool would leave the key condition unchanged because it supplies temporary one-to-one mappings from a public pool. That is useful for NAT tasks, while this scenario requires the team to choose the PTP role that can synchronize upstream on one port and distribute timing downstream on another segment using PTP boundary clock.
- PTP boundary clock provides segmented PTP timing distribution. That matches the requirement to choose the PTP role that can synchronize upstream on one port and distribute timing downstream on another segment. It directly controls the relevant PTP behavior, so the alternatives would change a different condition. This makes PTP boundary clock the direct fit for this case.
- HSRP virtual IP fails on scenario fit: it gives a resilient shared default gateway for HSRP decisions. The evidence says engineers must choose the PTP role that can synchronize upstream on one port and distribute timing downstream on another segment, and PTP boundary clock is the option that provides the needed behavior.
- NTP preferred server would change deterministic preference among valid NTP sources, which is appropriate in NTP selection scenarios. The present stem asks engineers to choose the PTP role that can synchronize upstream on one port and distribute timing downstream on another segment. That is why PTP boundary clock is the correct mechanism instead.
Question 7
An infrastructure engineer is correcting a production condition. The objective is to reduce timing error caused specifically by variable switch residence delay without making the switch the time source. Which option should be implemented? Choose ONE.
- PTP transparent clock
- PAT overload
- NTP source interface
- HSRP priority
Correct Answer(s)
A
Rationale
- The best answer is PTP transparent clock, which supplies forwarding-delay compensation for PTP. Because the requirement is to reduce timing error caused specifically by variable switch residence delay without making the switch the time source, this option matches the PTP decision and leaves adjacent functions untouched. This makes PTP transparent clock the direct fit for this case.
- PAT overload controls many-to-one address conservation for outbound sessions and is useful for PAT work. This case requires the team to reduce timing error caused specifically by variable switch residence delay without making the switch the time source. Because PTP transparent clock supplies that behavior, this option acts on the wrong requirement.
- NTP source interface should not be changed for this issue; it provides stable NTP packet sourcing for NTP reachability cases. The actual requirement is to reduce timing error caused specifically by variable switch residence delay without making the switch the time source, which is handled by PTP transparent clock.
- HSRP priority targets intentional HSRP active-router preference, so it fits another HSRP election condition. The question requires the team to reduce timing error caused specifically by variable switch residence delay without making the switch the time source. Since PTP transparent clock produces the needed behavior, this choice would not fix the root requirement.
Question 8
A campus engineer is preparing a controlled change. The requirement is to fix inbound reachability to a server whose public address changes whenever a dynamic translation is recreated. Which choice most directly satisfies that requirement? Choose ONE.
- NAT inside interface role
- HSRP preempt
- PTP grandmaster clock
- static inside source NAT
Correct Answer(s)
D
Rationale
- NAT inside interface role does not match the evidence because it provides correct identification of the private-side NAT boundary. That is a NAT direction function, whereas the stem requires engineers to fix inbound reachability to a server whose public address changes whenever a dynamic translation is recreated. static inside source NAT is the option tied to that task.
- HSRP preempt has a different role: it supplies restoration of the preferred HSRP active router in HSRP election scenarios. The engineer must fix inbound reachability to a server whose public address changes whenever a dynamic translation is recreated here. That makes static inside source NAT the direct answer and this option unsuitable.
- PTP grandmaster clock would leave the key condition unchanged because it supplies an authoritative precision-time origin. That is useful for PTP tasks, while this scenario requires the team to fix inbound reachability to a server whose public address changes whenever a dynamic translation is recreated using static inside source NAT.
- Static inside source NAT matches the desired state by providing a fixed private-to-public address mapping. Since engineers must fix inbound reachability to a server whose public address changes whenever a dynamic translation is recreated, this selection acts on the relevant NAT behavior and directly satisfies the requirement. This makes static inside source NAT the direct fit for this case.
Question 9
An enterprise switch change is being peer-reviewed. The design must explain why a dynamic NAT client fails only when every address in the configured public pool is already allocated. Which option should be approved? Choose ONE.
- NAT outside interface role
- HSRP object tracking
- dynamic NAT pool
- PTP boundary clock
Correct Answer(s)
C
Rationale
- NAT outside interface role would be useful when correct identification of the public-side NAT boundary is needed for NAT direction work. This question instead asks the team to explain why a dynamic NAT client fails only when every address in the configured public pool is already allocated. The correct control is dynamic NAT pool, so this alternative fails scenario fit.
- HSRP object tracking lacks the needed control effect; it provides gateway failover based on upstream health for HSRP tracking situations. Here the team must explain why a dynamic NAT client fails only when every address in the configured public pool is already allocated, which dynamic NAT pool enables directly.
- Choose dynamic NAT pool. It creates temporary one-to-one mappings from a public pool, while the stem requires engineers to explain why a dynamic NAT client fails only when every address in the configured public pool is already allocated. This directly satisfies the NAT condition and avoids changing a feature that is not implicated. This makes dynamic NAT pool the direct fit for this case.
- PTP boundary clock controls segmented PTP timing distribution and is useful for PTP work. This case requires the team to explain why a dynamic NAT client fails only when every address in the configured public pool is already allocated. Because dynamic NAT pool supplies that behavior, this option acts on the wrong requirement.
Question 10
A post-change check found a specific production issue. The engineer now needs to remediate exhausted public addressing when many simultaneous inside clients must share one global address. Which choice best resolves it? Choose ONE.
- PAT overload
- PTP transparent clock
- NAT match ACL
- VRRP priority and preemption
Correct Answer(s)
A
Rationale
- PAT overload fits because it delivers many-to-one address conservation for outbound sessions. The scenario specifically asks engineers to remediate exhausted public addressing when many simultaneous inside clients must share one global address. This is the PAT control that changes the tested behavior directly. This makes PAT overload the direct fit for this case.
- PTP transparent clock does not match the evidence because it provides forwarding-delay compensation for PTP. That is a PTP function, whereas the stem requires engineers to remediate exhausted public addressing when many simultaneous inside clients must share one global address. PAT overload is the option tied to that task.
- NAT match ACL would be an unnecessary change because it controls correct selection of addresses that should be translated. That is relevant to NAT policy requirements, while the current task is to remediate exhausted public addressing when many simultaneous inside clients must share one global address using PAT overload.
- VRRP priority and preemption is plausible because it delivers preferred VRRP primary selection for VRRP election cases. Here the team must remediate exhausted public addressing when many simultaneous inside clients must share one global address. PAT overload directly controls that state, while this option does not.
Question 11
An infrastructure engineer is correcting a production condition. The objective is to fix a translation policy that is correct except the client-facing interface is not classified as the NAT inside. Which option should be implemented? Choose ONE.
- static inside source NAT
- show ip nat translations
- VRRP object tracking
- NAT inside interface role
Correct Answer(s)
D
Rationale
- Static inside source NAT would be useful when a fixed private-to-public address mapping is needed for NAT work. This question instead asks the team to fix a translation policy that is correct except the client-facing interface is not classified as the NAT inside. The correct control is NAT inside interface role, so this alternative fails scenario fit.
- Show ip nat translations solves a different problem by providing direct inspection of active NAT mappings. That matters for NAT verification decisions, but this case requires engineers to fix a translation policy that is correct except the client-facing interface is not classified as the NAT inside. NAT inside interface role matches the evidence more precisely.
- VRRP object tracking would affect VRRP failover tied to path health, a legitimate VRRP tracking purpose. The stem instead depends on engineers being able to fix a translation policy that is correct except the client-facing interface is not classified as the NAT inside. NAT inside interface role provides that exact behavior, leaving this option operationally wrong.
- For this case, NAT inside interface role supplies correct identification of the private-side NAT boundary. The operational need is to fix a translation policy that is correct except the client-facing interface is not classified as the NAT inside. That correspondence makes it the correct NAT direction mechanism for the scenario. This makes NAT inside interface role the direct fit for this case.
Question 12
A campus engineer is preparing a controlled change. The requirement is to fix a correct inside-source rule that never translates toward the ISP because the external interface lacks its NAT role. Which choice most directly satisfies that requirement? Choose ONE.
- NTP client association
- NAT outside interface role
- HSRP virtual IP
- dynamic NAT pool
Correct Answer(s)
B
Rationale
- NTP client association is not selected because it governs time synchronization from a designated NTP source. That function belongs to NTP work. The required task is to fix a correct inside-source rule that never translates toward the ISP because the external interface lacks its NAT role, and that task is handled by NAT outside interface role.
- NAT outside interface role is the functional match: it provides correct identification of the public-side NAT boundary. The question requires the network to fix a correct inside-source rule that never translates toward the ISP because the external interface lacks its NAT role. That makes this the relevant NAT direction choice for the stated evidence. This makes NAT outside interface role the direct fit for this case.
- HSRP virtual IP misses the controlling requirement because its result is a resilient shared default gateway. That fits HSRP tasks. Here, the network needs engineers to fix a correct inside-source rule that never translates toward the ISP because the external interface lacks its NAT role, so NAT outside interface role is the relevant mechanism.
- Dynamic NAT pool would be an unnecessary change because it controls temporary one-to-one mappings from a public pool. That is relevant to NAT requirements, while the current task is to fix a correct inside-source rule that never translates toward the ISP because the external interface lacks its NAT role using NAT outside interface role.
Question 13
An enterprise switch change is being peer-reviewed. The design must identify why one subnet never translates even though interface roles and the address pool are correct. Which option should be approved? Choose ONE.
- NAT match ACL
- PAT overload
- NTP authentication
- HSRP priority
Correct Answer(s)
A
Rationale
- Use NAT match ACL; its operational effect is correct selection of addresses that should be translated. The stated task is to identify why one subnet never translates even though interface roles and the address pool are correct. That mechanism addresses the NAT policy requirement without altering an unrelated control. This makes NAT match ACL the direct fit for this case.
- PAT overload solves a different problem by providing many-to-one address conservation for outbound sessions. That matters for PAT decisions, but this case requires engineers to identify why one subnet never translates even though interface roles and the address pool are correct. NAT match ACL matches the evidence more precisely.
- NTP authentication provides authenticated time synchronization, which belongs to NTP security decisions. The stem instead requires engineers to identify why one subnet never translates even though interface roles and the address pool are correct. That result comes from NAT match ACL; selecting NTP authentication would leave the tested condition unresolved.
- HSRP priority solves the wrong problem by producing intentional HSRP active-router preference. It fits HSRP election needs, but the tested task is to identify why one subnet never translates even though interface roles and the address pool are correct. That requirement maps directly to NAT match ACL.
Question 14
A post-change check found a specific production issue. The engineer now needs to choose the verification output that directly proves the translated global address and port for a live client flow. Which choice best resolves it? Choose ONE.
- HSRP preempt
- NTP preferred server
- NAT inside interface role
- show ip nat translations
Correct Answer(s)
D
Rationale
- Do not select HSRP preempt; its effect is restoration of the preferred HSRP active router, a valid HSRP election function. The scenario requires engineers to choose the verification output that directly proves the translated global address and port for a live client flow. That requirement maps to show ip nat translations, not to this alternative.
- NTP preferred server is technically useful for deterministic preference among valid NTP sources in NTP selection work. The tested task is to choose the verification output that directly proves the translated global address and port for a live client flow, however. That behavior is governed by show ip nat translations, making this option a distractor.
- NAT inside interface role misses the controlling requirement because its result is correct identification of the private-side NAT boundary. That fits NAT direction tasks. Here, the network needs engineers to choose the verification output that directly proves the translated global address and port for a live client flow, so show ip nat translations is the relevant mechanism.
- Show ip nat translations is the precise choice because it yields direct inspection of active NAT mappings. Here, the network must choose the verification output that directly proves the translated global address and port for a live client flow. The feature therefore resolves the tested NAT verification condition instead of a different issue. This makes show ip nat translations the direct fit for this case.
Question 15
An infrastructure engineer is correcting a production condition. The objective is to preserve endpoint gateway configuration while failing first-hop forwarding from one router to its peer. Which option should be implemented? Choose ONE.
- NTP source interface
- NAT outside interface role
- HSRP virtual IP
- HSRP object tracking
Correct Answer(s)
C
Rationale
- NTP source interface is not an equivalent substitute because it creates stable NTP packet sourcing. That serves NTP reachability needs, not the requirement to preserve endpoint gateway configuration while failing first-hop forwarding from one router to its peer. HSRP virtual IP acts on the condition described in the stem.
- NAT outside interface role solves the wrong problem by producing correct identification of the public-side NAT boundary. It fits NAT direction needs, but the tested task is to preserve endpoint gateway configuration while failing first-hop forwarding from one router to its peer. That requirement maps directly to HSRP virtual IP.
- Use HSRP virtual IP to obtain a resilient shared default gateway. That is exactly what the team needs when it must preserve endpoint gateway configuration while failing first-hop forwarding from one router to its peer. The HSRP decision is therefore resolved by this mechanism, not the alternatives. This makes HSRP virtual IP the direct fit for this case.
- HSRP object tracking is a neighboring feature that yields gateway failover based on upstream health for HSRP tracking needs. This scenario requires the team to preserve endpoint gateway configuration while failing first-hop forwarding from one router to its peer. The required behavior belongs to HSRP virtual IP, so this alternative is mismatched.
Question 16
A campus engineer is preparing a controlled change. The requirement is to correct an HSRP election where the intended primary has lower priority than the current active router. Which choice most directly satisfies that requirement? Choose ONE.
- VRRP priority and preemption
- HSRP priority
- NAT match ACL
- PTP grandmaster clock
Correct Answer(s)
B
Rationale
- VRRP priority and preemption does not resolve the requirement; it provides preferred VRRP primary selection for VRRP election decisions. Because the stem requires engineers to correct an HSRP election where the intended primary has lower priority than the current active router, HSRP priority is the mechanism that should be selected.
- HSRP priority is correct because it creates intentional HSRP active-router preference. In this scenario, engineers must correct an HSRP election where the intended primary has lower priority than the current active router. The option acts on the exact HSRP election decision described in the stem. This makes HSRP priority the direct fit for this case.
- Do not select NAT match ACL; its effect is correct selection of addresses that should be translated, a valid NAT policy function. The scenario requires engineers to correct an HSRP election where the intended primary has lower priority than the current active router. That requirement maps to HSRP priority, not to this alternative.
- PTP grandmaster clock is related but operationally wrong because it yields an authoritative precision-time origin. That supports PTP work. This case requires engineers to correct an HSRP election where the intended primary has lower priority than the current active router, so HSRP priority fits the stated condition.
Question 17
An enterprise switch change is being peer-reviewed. The design must explain why a recovered higher-priority HSRP router stays standby instead of taking back the active role. Which option should be approved? Choose ONE.
- PTP boundary clock
- VRRP object tracking
- show ip nat translations
- HSRP preempt
Correct Answer(s)
D
Rationale
- PTP boundary clock would change segmented PTP timing distribution, which is appropriate in PTP scenarios. The present stem asks engineers to explain why a recovered higher-priority HSRP router stays standby instead of taking back the active role. That is why HSRP preempt is the correct mechanism instead.
- VRRP object tracking fails on scenario fit: it gives VRRP failover tied to path health for VRRP tracking decisions. The evidence says engineers must explain why a recovered higher-priority HSRP router stays standby instead of taking back the active role, and HSRP preempt is the option that provides the needed behavior.
- Show ip nat translations is a neighboring feature that yields direct inspection of active NAT mappings for NAT verification needs. This scenario requires the team to explain why a recovered higher-priority HSRP router stays standby instead of taking back the active role. The required behavior belongs to HSRP preempt, so this alternative is mismatched.
- Select HSRP preempt for restoration of the preferred HSRP active router. The stem makes the requirement explicit: explain why a recovered higher-priority HSRP router stays standby instead of taking back the active role. That result is governed by this HSRP election mechanism rather than by the neighboring options. This makes HSRP preempt the direct fit for this case.
Question 18
A post-change check found a specific production issue. The engineer now needs to prevent a black hole where an HSRP active router retains the virtual gateway despite losing its upstream path. Which choice best resolves it? Choose ONE.
- HSRP object tracking
- HSRP virtual IP
- PTP transparent clock
- NTP client association
Correct Answer(s)
A
Rationale
- HSRP object tracking is appropriate because the result is gateway failover based on upstream health. The scenario requires engineers to prevent a black hole where an HSRP active router retains the virtual gateway despite losing its upstream path. This feature controls that HSRP tracking behavior specifically, so it is the best fit. This makes HSRP object tracking the direct fit for this case.
- HSRP virtual IP does not resolve the requirement; it provides a resilient shared default gateway for HSRP decisions. Because the stem requires engineers to prevent a black hole where an HSRP active router retains the virtual gateway despite losing its upstream path, HSRP object tracking is the mechanism that should be selected.
- PTP transparent clock should not be changed for this issue; it provides forwarding-delay compensation for PTP for PTP cases. The actual requirement is to prevent a black hole where an HSRP active router retains the virtual gateway despite losing its upstream path, which is handled by HSRP object tracking.
- NTP client association targets time synchronization from a designated NTP source, so it fits another NTP condition. The question requires the team to prevent a black hole where an HSRP active router retains the virtual gateway despite losing its upstream path. Since HSRP object tracking produces the needed behavior, this choice would not fix the root requirement.
Question 19
An infrastructure engineer is correcting a production condition. The objective is to correct a VRRP election so the designated higher-priority router becomes primary again after recovery. Which option should be implemented? Choose ONE.
- HSRP priority
- NTP authentication
- VRRP priority and preemption
- static inside source NAT
Correct Answer(s)
C
Rationale
- HSRP priority fails on scenario fit: it gives intentional HSRP active-router preference for HSRP election decisions. The evidence says engineers must correct a VRRP election so the designated higher-priority router becomes primary again after recovery, and VRRP priority and preemption is the option that provides the needed behavior.
- NTP authentication has a different role: it supplies authenticated time synchronization in NTP security scenarios. The engineer must correct a VRRP election so the designated higher-priority router becomes primary again after recovery here. That makes VRRP priority and preemption the direct answer and this option unsuitable.
- Choose VRRP priority and preemption because its result is preferred VRRP primary selection. The stem requires the team to correct a VRRP election so the designated higher-priority router becomes primary again after recovery. That is a direct VRRP election match, not merely a related feature. This makes VRRP priority and preemption the direct fit for this case.
- Static inside source NAT would leave the key condition unchanged because it supplies a fixed private-to-public address mapping. That is useful for NAT tasks, while this scenario requires the team to correct a VRRP election so the designated higher-priority router becomes primary again after recovery using VRRP priority and preemption.
Question 20
A campus engineer is preparing a controlled change. The requirement is to avoid keeping a VRRP router primary when its LAN interface is up but the tracked path to the core is down. Which choice most directly satisfies that requirement? Choose ONE.
- NTP preferred server
- VRRP object tracking
- HSRP preempt
- dynamic NAT pool
Correct Answer(s)
B
Rationale
- NTP preferred server lacks the needed control effect; it provides deterministic preference among valid NTP sources for NTP selection situations. Here the team must avoid keeping a VRRP router primary when its LAN interface is up but the tracked path to the core is down, which VRRP object tracking enables directly.
- VRRP object tracking directly produces VRRP failover tied to path health. That is relevant because the team needs to avoid keeping a VRRP router primary when its LAN interface is up but the tracked path to the core is down. For this VRRP tracking decision, the feature changes the condition identified by the evidence. This makes VRRP object tracking the direct fit for this case.
- HSRP preempt targets restoration of the preferred HSRP active router, so it fits another HSRP election condition. The question requires the team to avoid keeping a VRRP router primary when its LAN interface is up but the tracked path to the core is down. Since VRRP object tracking produces the needed behavior, this choice would not fix the root requirement.
- Dynamic NAT pool controls temporary one-to-one mappings from a public pool and is useful for NAT work. This case requires the team to avoid keeping a VRRP router primary when its LAN interface is up but the tracked path to the core is down. Because VRRP object tracking supplies that behavior, this option acts on the wrong requirement.