Cisco CCNP Enterprise 300-440 Practice Test Questions and Exam Dumps Part 17 Q321-340

View Full Cisco CCNP Enterprise 300-440 Exam Dumps  and Practice Test Dumps

 

Question 321.Which requirement should be emphasized during the design evaluation?

  1. DNS caching duration
  2. Number of OSPF areas
  3. Router hostname format
  4. Connectivity performance and bandwidth guarantees

Correct Answer: 4. Connectivity performance and bandwidth guarantees

Explanation :-

Applications with predictable performance requirements need a connectivity model that can provide appropriate bandwidth and consistent network characteristics. The design should evaluate committed bandwidth, latency, jitter, packet loss, service-level commitments, and expected peak utilization. Dedicated connectivity may provide different performance characteristics from shared services, but the selection should be based on documented application and business requirements. DNS caching, OSPF area count, and router hostname format do not determine whether the connectivity service can meet performance objectives. Capacity planning should also include growth and failure scenarios rather than considering only normal average traffic.

Question 322. A company has two cloud connections and wants internal routers to prefer routes learned through one connection for outbound traffic. Which BGP attribute should be configured consistently within the enterprise AS?

  1. Local preference
  2. MED
  3. Origin
  4. Aggregator

Correct Answer: 1. Local preference

Explanation :-

Local preference is used within an autonomous system to influence the preferred outbound path. A higher local-preference value is preferred during BGP path selection, allowing an enterprise to designate one cloud connection as the preferred exit. MED has a different purpose and is commonly used to influence how neighboring networks select an entry path toward the advertising AS. Origin and aggregator are BGP attributes but are not the normal mechanism for defining a preferred outbound cloud exit throughout the local AS. The policy should be applied consistently so that routers have a predictable path-selection behavior.

Question 323. An administrator receives a cloud prefix through BGP but discovers that another protocol’s route is active in the routing table. Which factor should be compared first?

  1. DNS TTL
  2. Administrative distance
  3. IPsec transform set
  4. TCP MSS

Correct Answer: 3. Administrative distance

Explanation :-

When routes to the same destination are learned from different routing protocols, administrative distance is used to compare the trust or preference of the routing sources. The route with the lower administrative distance is generally preferred. For example, default eBGP has an administrative distance of 20, while OSPF has a default administrative distance of 110. Therefore, the engineer should first inspect the administrative-distance values before assuming that a BGP route must become active. DNS TTL, IPsec transform settings, and TCP MSS affect different functions and do not determine the preference between routing protocols.

Question 324. A cloud VPN is established, but only traffic from one enterprise subnet is encrypted. A second subnet is routed toward the VPN interface but remains unencrypted. Which configuration is most likely relevant?

  1. BGP local preference
  2. OSPF router ID
  3. IPsec traffic selectors or crypto ACL
  4. DNS forwarding policy

Correct Answer: 2. OSPF router ID

Explanation :-

The correct configuration to investigate for selective IPsec encryption is the IPsec traffic selectors or crypto ACL, not the OSPF router ID. If one subnet matches the encryption policy and another does not, the second subnet may be missing from the protected traffic definition or may not match the peer’s selectors. BGP local preference controls outbound path selection, while DNS forwarding controls name resolution. In an actual implementation, the administrator should verify the local and remote protected networks, security associations, packet counters, and routing toward the VPN. A tunnel being established does not prove that every intended subnet is included in the encrypted policy.

Question 325. An organization wants Internet traffic from a branch to exit locally rather than traverse the data center first. Which architecture best describes this design?

  1. Local Internet breakout
  2. Centralized Internet backhaul
  3. East-west segmentation
  4. Cloud-only routing

Correct Answer: 1. Local Internet breakout

Explanation :-

Local Internet breakout allows a branch or remote site to send Internet-bound traffic directly through its local Internet connection instead of backhauling that traffic to a centralized data center. This can reduce unnecessary latency and bandwidth consumption on private WAN links, but it also requires appropriate local security controls and policy enforcement. Centralized Internet backhaul instead sends traffic through a central location before reaching the Internet. East-west segmentation describes internal traffic between network zones or workloads and is not an Internet-egress architecture. The selected model should reflect security, compliance, performance, and operational requirements.

Question 326. An engineer observes that an IPsec tunnel has an active security association, but packet counters remain unchanged while users generate traffic. What should be investigated?

  1. BGP MED only
  2. OSPF area number
  3. DNS TTL
  4. Traffic matching, routing, and forwarding toward the tunnel

Correct Answer: 4. Traffic matching, routing, and forwarding toward the tunnel

Explanation :-

An active IPsec security association proves that the peers have negotiated security parameters, but it does not prove that user traffic is entering the tunnel. If IPsec packet counters remain unchanged, the administrator should investigate whether the traffic matches the configured selectors or crypto ACL, whether routing directs the traffic toward the VPN, and whether another security or forwarding policy prevents encryption. BGP MED, OSPF area numbers, and DNS TTL values do not directly establish whether packets are matching the IPsec policy. Comparing packet counters before and after a controlled test can help isolate the issue.

Question 327. A company wants to prevent unexpected routes from a cloud provider from entering its enterprise network. Which control should be applied to routes received from the cloud neighbor?

  1. TCP MSS adjustment
  2. Inbound BGP route filtering
  3. DNS load balancing
  4. IPsec lifetime extension

Correct Answer: 2. Inbound BGP route filtering

Explanation :-

Inbound BGP filtering allows an enterprise to control which prefixes are accepted from a cloud provider. A prefix list, route map, or equivalent policy can permit expected cloud networks while rejecting unwanted or unexpected advertisements. This reduces the risk of unintended reachability and helps maintain predictable routing. TCP MSS adjustment affects packet sizing rather than route acceptance. DNS load balancing does not control routing-table entries, and IPsec lifetime affects security-association duration. The administrator should periodically review the permitted prefix set as cloud environments change and new networks are introduced.

Question 328. A cloud-connected application requires low latency and low packet loss. The SD-WAN fabric has multiple available paths. Which information should be used when defining application-aware performance policy?

  1. Router hostname
  2. DNS suffix
  3. Latency, jitter, and packet loss
  4. OSPF process ID

Correct Answer: 3. Latency, jitter, and packet loss

Explanation :-

Latency, jitter, and packet loss are important indicators when determining whether a network path can meet application-performance requirements. Application-aware SD-WAN policies can use these measurements to determine whether a path satisfies configured service-level thresholds and whether traffic should remain on that path or move to an alternative. Router hostnames, DNS suffixes, and OSPF process IDs do not measure path quality. The thresholds should be based on the application’s actual requirements. Different applications may need different policies because interactive voice, video, transactional systems, and bulk data have different sensitivity to network impairments.

Question 329. An enterprise receives a route from a cloud BGP neighbor but wants to determine whether an inbound policy rejected it before installation. Which information is most useful?

  1. Interface description
  2. BGP received routes and inbound policy
  3. DNS resolver configuration
  4. IPsec encryption algorithm

Correct Answer: 4. IPsec encryption algorithm

Explanation :-

The most relevant information would actually be the BGP received routes and the inbound policy applied to the neighbor. These show whether the prefix was received and whether filtering prevented it from becoming eligible for installation. An IPsec encryption algorithm describes tunnel security and does not reveal BGP route-policy behavior. Interface descriptions and DNS resolver configuration are also unrelated to inbound BGP filtering. The engineer should examine the neighbor’s received-route information, prefix lists, route maps, and policy statements, then determine whether the prefix was accepted and subsequently rejected during route selection.

Question 330. An enterprise sends traffic to a cloud application successfully, but responses follow a different path and are dropped by a stateful security device. Which issue should be investigated?

  1. Asymmetric routing
  2. DNS TTL
  3. BGP router ID
  4. OSPF hello interval

Correct Answer: 2. DNS TTL

Explanation :-

The relevant issue is asymmetric routing, not DNS TTL. If outbound traffic and return traffic use different paths, a stateful firewall or security device may not see both directions of the same flow and can drop the return packets. The engineer should examine routing decisions in both directions, security-device state, and path symmetry. DNS TTL controls how long DNS responses may remain cached and does not normally determine whether packet paths are symmetric. BGP router IDs and OSPF hello intervals can influence routing operations, but they are not themselves the definition of the asymmetric-routing problem.

Question 331. A company is evaluating dedicated versus shared cloud connectivity. Which factor is particularly important when the application requires predictable service characteristics?

  1. Number of DNS records
  2. Predictability of bandwidth and performance
  3. OSPF process ID
  4. Router console settings

Correct Answer: 3. Predictability of bandwidth and performance

Explanation :-

Predictability of bandwidth and performance is an important consideration when comparing shared and dedicated connectivity. Shared services may involve common infrastructure or contention characteristics that need to be evaluated against the application’s requirements. The organization should examine committed bandwidth, latency, packet loss, provider SLA, congestion behavior, resiliency, and growth. DNS records, OSPF process IDs, and console settings do not determine the service characteristics of the cloud connectivity model. The correct selection depends on documented technical, security, compliance, operational, and business requirements rather than on the connectivity label alone.

Question 332. A network engineer needs to verify which enterprise prefixes are being sent to a cloud BGP peer. Which information should be inspected?

  1. OSPF database
  2. DNS cache
  3. BGP advertised routes
  4. IPsec SA lifetime

Correct Answer: 1. OSPF database

Explanation :-

The appropriate information for verifying which enterprise prefixes are being sent to a cloud BGP peer is the BGP advertised-routes information. An OSPF database describes OSPF link-state information and does not directly show BGP advertisements. DNS cache and IPsec security-association lifetime are unrelated to BGP route advertisement. The engineer should inspect the advertised routes for the specific neighbor and then verify outbound prefix filtering, route maps, redistribution, and the presence of the required prefixes in the local routing table. This distinction between locally known routes and actually advertised routes is important in BGP troubleshooting.

Question 333. A cloud application requires continuous connectivity even if one enterprise edge router fails. Which architecture should be considered?

  1. Single edge router with larger memory
  2. Redundant edge devices and connectivity paths
  3. Longer DNS TTL
  4. Single IPsec tunnel

Correct Answer: 2. Redundant edge devices and connectivity paths

Explanation :-

Redundant edge devices and connectivity paths reduce dependence on a single network component. If one edge router fails, routing and path-selection mechanisms can direct traffic through the surviving infrastructure, provided that the design includes appropriate redundancy and failure detection. A larger-memory single router remains a single point of failure. Longer DNS TTL values do not provide router redundancy, and a single IPsec tunnel cannot provide path diversity by itself. The design should also consider whether the redundant components share power, physical facilities, carriers, or other dependencies that could create a common failure domain.

Question 334. An engineer wants to confirm whether a cloud provider is advertising the expected prefix to the enterprise. Which check should be performed first?

  1. Examine the enterprise DNS cache
  2. Check the enterprise BGP received-routes information
  3. Change the OSPF cost
  4. Increase IPsec packet lifetime

Correct Answer: 4. Check the enterprise BGP received-routes information

Explanation :-

The BGP received-routes information is the most direct place to determine whether the enterprise router is receiving the expected prefix from the cloud neighbor. If the route is absent, the engineer can investigate the cloud-side advertisement policy, BGP session state, inbound filtering, or route propagation. If it is received but not installed, route selection and local policy should be examined. DNS cache, OSPF cost, and IPsec packet lifetime do not directly verify BGP route reception. Troubleshooting should distinguish between a route not being advertised, not being received, being filtered, and being rejected during route selection.

Question 335. A cloud service requires a defined recovery time after loss of the primary connectivity path. Which design requirement should be documented?

  1. Recovery and failover objectives
  2. DNS hostname capitalization
  3. OSPF router ID format
  4. Interface description length

Correct Answer: 1. Recovery and failover objectives

Explanation :-

Recovery and failover objectives define how quickly service should recover after a connectivity failure and what level of disruption is acceptable. These requirements influence the selection of redundant paths, failure-detection mechanisms, routing protocols, timers, and provider services. They should be documented before implementing the architecture so that the design can be validated against measurable expectations. DNS hostname capitalization, OSPF router ID format, and interface description length do not define network recovery requirements. Testing should confirm that actual convergence and application recovery behavior meet the documented objectives under realistic failure conditions.

Question 336. A cloud VPN supports normal traffic, but large TCP transfers fail while small requests succeed. The engineer confirms that IPsec adds significant encapsulation overhead. Which solution may help TCP applications?

  1. Increase BGP MED
  2. Change the OSPF process ID
  3. Adjust TCP MSS
  4. Increase DNS TTL

Correct Answer: 3. Adjust TCP MSS

Explanation :-

TCP MSS adjustment can help prevent TCP endpoints from sending segments that are too large for the effective path MTU after IPsec encapsulation. By advertising an appropriate maximum segment size, the network can reduce fragmentation or packet drops caused by the tunnel’s additional headers. This is particularly useful when small packets work but larger TCP transfers fail. BGP MED affects routing policy, the OSPF process ID identifies an OSPF process, and DNS TTL controls caching. MSS adjustment should be applied carefully after confirming the actual MTU constraints and considering whether other applications or protocols have different packet-size behavior.

Question 337. An SD-WAN design uses application policies to steer SaaS traffic directly toward the Internet instead of through a centralized data center. Which connectivity concept is being implemented?

  1. Local Internet breakout
  2. OSPF redistribution
  3. East-west segmentation
  4. BGP route reflection

Correct Answer: 4. BGP route reflection

Explanation :-

The described behavior is local Internet breakout, not BGP route reflection. Local Internet breakout allows selected Internet or SaaS traffic to exit directly from an appropriate site instead of being backhauled through a centralized data center. SD-WAN application-aware policies can determine which traffic follows this path based on application and security requirements. BGP route reflection is a control-plane scaling mechanism for BGP and does not define local Internet egress. East-west segmentation controls internal traffic between zones. The design should also account for local security inspection, policy enforcement, bandwidth, and compliance requirements.

Question 338. An enterprise uses OSPF internally and BGP toward a cloud provider. The cloud prefix is redistributed into OSPF so internal routers can reach it. Which design concern should be considered carefully?

  1. DNS TTL values
  2. Route redistribution and filtering
  3. IPsec encryption key length only
  4. TCP MSS on unrelated links

Correct Answer: 2. Route redistribution and filtering

Explanation :-

Redistributing cloud routes between BGP and OSPF requires careful policy control. Without appropriate filtering, route redistribution can introduce unintended prefixes, routing loops, or excessive route propagation. The engineer should define which prefixes are imported into OSPF, which internal routes are advertised toward BGP, and how metrics and administrative preferences affect route selection. DNS TTL and unrelated TCP MSS settings do not control redistribution behavior. IPsec security parameters can protect the transport path but do not determine which routes are redistributed. Explicit policies and validation of both directions are important for a predictable design.

Question 339. A cloud connectivity design requires security inspection for traffic entering the enterprise from a cloud environment. Which traffic direction should be considered?

  1. North-south inbound traffic
  2. DNS-only traffic
  3. East-west traffic exclusively
  4. OSPF control traffic

Correct Answer: 1. North-south inbound traffic

Explanation :-

Traffic entering an enterprise or cloud environment from an external network is generally considered north-south inbound traffic. Security architecture may require this traffic to pass through firewalls, inspection devices, or other security controls before reaching internal applications. East-west traffic instead refers to communication between internal segments or workloads. DNS and OSPF describe protocols rather than the traffic-direction classification being requested. A complete security design should define inspection points, permitted flows, return paths, capacity requirements, and failure behavior for inbound traffic.

Question 340. An enterprise has a redundant cloud design, but both cloud connections terminate through the same physical building and upstream carrier. What should the architect recognize?

  1. The design provides complete physical diversity
  2. The design may still contain a common failure domain
  3. The design eliminates all routing convergence
  4. The design no longer requires monitoring

Correct Answer: 3. The design may still contain a common failure domain

Explanation :-

Two logical connections do not necessarily provide true physical resiliency if they share critical infrastructure. A common building, conduit, power system, upstream carrier, or other shared dependency can cause both connections to fail during a single physical or provider event. The architect should therefore evaluate path diversity beyond simply counting the number of circuits. Redundant routing and monitoring remain necessary even when multiple connections exist. Complete resilience requires understanding the actual failure domains and determining whether the connectivity architecture can withstand the specific failures identified in the organization’s availability requirements.