Practice Exams:

Cisco 400-007 Dumps

EXAM: Cisco Certified Design Expert
Verified By Experts
Premium Bundle
$19.99
$54.99 $74.98

400-007 Premium Bundle


  • Premium File 349 Questions & Answers
  • Study Guide 934 Pages

Cisco 400-007 Practice Test 37

Question 360

In a separate customer architecture review, this issue arises: A multinational chooses where to separate IS-IS core transit from regional routing detail. Out-of-hours operations staff cannot perform manual changes at every remote site. Which failure is the most direct risk of taking the tempting design shortcut?

  1. A single control-plane fault can suppress route visibility across unrelated regions
  2. Traffic may exit through an unapproved path despite apparently healthy route adjacencies
  3. A model false positive can propagate a widespread outage or violate an SLA
  4. Control-plane churn and database scale can degrade backbone convergence

Answer & Explanations

Correct answer: D

A.

The offered consequence belongs to the alternative control path: Build redundant route-reflector clusters with policy-consistent hierarchy and independent failure domains. The relevant failure for the current situation is: Control-plane churn and database scale can degrade backbone convergence. The distinction follows from: IS-IS hierarchy can keep detailed local topology from burdening the backbone while preserving needed reachability.

B.

The offered consequence belongs to the alternative control path: Implement documented local preference and community policy at controlled BGP boundaries. The relevant failure for the current situation is: Control-plane churn and database scale can degrade backbone convergence. The distinction follows from: IS-IS hierarchy can keep detailed local topology from burdening the backbone while preserving needed reachability.

C.

The offered consequence belongs to the alternative control path: Use AI recommendations as evidence with simulation and gated human-controlled network changes. The relevant failure for the current situation is: Control-plane churn and database scale can degrade backbone convergence. The distinction follows from: IS-IS hierarchy can keep detailed local topology from burdening the backbone while preserving needed reachability.

D.

Control-plane churn and database scale can degrade backbone convergence. That is the risk in the reported situation—A multinational chooses where to separate IS-IS core transit from regional routing detail. The corrective action is: Use L1/L2 boundaries and leak only policy-approved interlevel routes. Technical basis: IS-IS hierarchy can keep detailed local topology from burdening the backbone while preserving needed reachability.

Question 361

A network design team is assessing this customer situation: A merger introduces a second routing protocol and route feedback is possible through two borders. The operational team has limited access to a remote carrier demarcation. Which technical rationale best explains the proposed design choice under these constraints?

  1. Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains
  2. IS-IS hierarchy can keep detailed local topology from burdening the backbone while preserving needed reachability
  3. Unnecessary hairpin forwarding increases delay and consumes shared uplinks without adding required inspection value
  4. Coexistence protects service continuity only when route ownership and address overlaps are resolved

Answer & Explanations

Correct answer: A

A.

Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains. This explains the action: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes. For the described facts—A merger introduces a second routing protocol and route feedback is possible through two borders—test the outcome through: A failure simulation finds no duplicated route feedback and verifies the intended administrative preference.

B.

The alternative principle is: IS-IS hierarchy can keep detailed local topology from burdening the backbone while preserving needed reachability. It instead explains this action: Use L1/L2 boundaries and leak only policy-approved interlevel routes. For the present requirement, the controlling mechanism is: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains.

C.

The alternative principle is: Unnecessary hairpin forwarding increases delay and consumes shared uplinks without adding required inspection value. It instead explains this action: Keep latency-sensitive east-west paths local with policy-consistent segmentation and service discovery. For the present requirement, the controlling mechanism is: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains.

D.

The alternative principle is: Coexistence protects service continuity only when route ownership and address overlaps are resolved. It instead explains this action: Use a time-bounded dual-running migration with explicit route authority and per-site cutover controls. For the present requirement, the controlling mechanism is: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains.

Question 362

A network design team is assessing this customer situation: A merger introduces a second routing protocol and route feedback is possible through two borders. The operational team has limited access to a remote carrier demarcation. Which acceptance result would most convincingly demonstrate that the design addresses the critical requirement?

  1. Application traces show local flows meet latency and segmentation policy during peak replication
  2. A failure simulation finds no duplicated route feedback and verifies the intended administrative preference
  3. Route tests show each classified prefix chooses the intended next hop before and after peer failure
  4. A probe from partner sites reaches the approved service but not unrelated customer prefixes

Answer & Explanations

Correct answer: B

A.

The offered observation would test: Keep latency-sensitive east-west paths local with policy-consistent segmentation and service discovery. It would not establish that the stated requirement has been met. The direct evidence needed here is: A failure simulation finds no duplicated route feedback and verifies the intended administrative preference.

B.

Direct verification: A failure simulation finds no duplicated route feedback and verifies the intended administrative preference. This is the relevant evidence for the action: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes. The reason is: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains.

C.

The offered observation would test: Implement documented local preference and community policy at controlled BGP boundaries. It would not establish that the stated requirement has been met. The direct evidence needed here is: A failure simulation finds no duplicated route feedback and verifies the intended administrative preference.

D.

The offered observation would test: Restrict VPN import/export using explicit route targets and service-specific policy. It would not establish that the stated requirement has been met. The direct evidence needed here is: A failure simulation finds no duplicated route feedback and verifies the intended administrative preference.

Question 363

A network design team is assessing this customer situation: A merger introduces a second routing protocol and route feedback is possible through two borders. The operational team has limited access to a remote carrier demarcation. Which failure is the most direct risk of taking the tempting design shortcut?

  1. Traffic may exit through an unapproved path despite apparently healthy route adjacencies
  2. Route feedback and divergent policies can strand sites during staged conversion
  3. Routing feedback can create loops, unstable preference or unexpected reachability
  4. Sensitive traffic can violate contractual or regulatory boundaries during recovery

Answer & Explanations

Correct answer: C

A.

The offered consequence belongs to the alternative control path: Implement documented local preference and community policy at controlled BGP boundaries. The relevant failure for the current situation is: Routing feedback can create loops, unstable preference or unexpected reachability. The distinction follows from: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains.

B.

The offered consequence belongs to the alternative control path: Use a time-bounded dual-running migration with explicit route authority and per-site cutover controls. The relevant failure for the current situation is: Routing feedback can create loops, unstable preference or unexpected reachability. The distinction follows from: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains.

C.

Routing feedback can create loops, unstable preference or unexpected reachability. That is the risk in the reported situation—A merger introduces a second routing protocol and route feedback is possible through two borders. The corrective action is: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes. Technical basis: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains.

D.

The offered consequence belongs to the alternative control path: Translate data classification and service ownership into explicit path and segmentation policy. The relevant failure for the current situation is: Routing feedback can create loops, unstable preference or unexpected reachability. The distinction follows from: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains.

Question 364

A network design team is assessing this customer situation: A merger introduces a second routing protocol and route feedback is possible through two borders. The operational team has limited access to a remote carrier demarcation. Which prerequisite should the architect confirm before choosing and defending this design?

  1. Define traffic classes, upstream policy, local preference scope and failover requirements
  2. Map site ownership, aggregate reachability, return paths and route-withdrawal behavior
  3. Map actual service dependencies, data sensitivity, inspection requirements and failure behavior
  4. Catalog prefix ownership, redistribution points, tags and route preference rules

Answer & Explanations

Correct answer: D

A.

The offered preparation belongs with the alternative action: Implement documented local preference and community policy at controlled BGP boundaries. Here the necessary starting condition is: Catalog prefix ownership, redistribution points, tags and route preference rules. It supports: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes.

B.

The offered preparation belongs with the alternative action: Summarize at stable boundaries while retaining explicitly required more-specific exceptions. Here the necessary starting condition is: Catalog prefix ownership, redistribution points, tags and route preference rules. It supports: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes.

C.

The offered preparation belongs with the alternative action: Keep latency-sensitive east-west paths local with policy-consistent segmentation and service discovery. Here the necessary starting condition is: Catalog prefix ownership, redistribution points, tags and route preference rules. It supports: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes.

D.

The necessary starting condition is: Catalog prefix ownership, redistribution points, tags and route preference rules. This enables the action: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes. Validate the result with: A failure simulation finds no duplicated route feedback and verifies the intended administrative preference.

Question 365

In a separate customer architecture review, this issue arises: A branch migration temporarily redistributes OSPF and BGP at separate hubs. The customer requires clear acceptance tests before a new contract is signed. Which high-level network design choice most directly meets the stated technical and operational requirement?

  1. Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes
  2. Use L1/L2 boundaries and leak only policy-approved interlevel routes
  3. Translate data classification and service ownership into explicit path and segmentation policy
  4. Create area boundaries and resilient ABRs that localize topology changes without isolating reachability

Answer & Explanations

Correct answer: A

A.

Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains. First establish the prerequisite: Catalog prefix ownership, redistribution points, tags and route preference rules. The proposed response is: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes. Validation: A failure simulation finds no duplicated route feedback and verifies the intended administrative preference.

B.

The alternative addresses a different technical concern: IS-IS hierarchy can keep detailed local topology from burdening the backbone while preserving needed reachability. The governing mechanism here is: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains. Accordingly, use: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes.

C.

Reachability should reflect differentiated business constraints, not a single cheapest route for all traffic. That supports the alternative intervention: Translate data classification and service ownership into explicit path and segmentation policy. The present situation—A branch migration temporarily redistributes OSPF and BGP at separate hubs—instead calls for: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes. Technical basis: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains.

D.

The alternative addresses: Create area boundaries and resilient ABRs that localize topology changes without isolating reachability. Its principle is: OSPF flooding domains and summary design affect CPU load, SPF frequency and fault propagation. In this case the needed action is: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes. Confirm by: A failure simulation finds no duplicated route feedback and verifies the intended administrative preference.

Question 366

In a separate customer architecture review, this issue arises: A branch migration temporarily redistributes OSPF and BGP at separate hubs. The customer requires clear acceptance tests before a new contract is signed. Which acceptance result would most convincingly demonstrate that the design addresses the critical requirement?

  1. A sample site expansion consumes only its delegated block and maintains summarized announcements
  2. A failure simulation finds no duplicated route feedback and verifies the intended administrative preference
  3. A simulated access churn changes local LSPs without exhausting backbone routing state
  4. Route tests show each classified prefix chooses the intended next hop before and after peer failure

Answer & Explanations

Correct answer: B

A.

The offered observation would test: Allocate hierarchical IPv6 prefixes per region and role with room for subnet growth. It would not establish that the stated requirement has been met. The direct evidence needed here is: A failure simulation finds no duplicated route feedback and verifies the intended administrative preference.

B.

Direct verification: A failure simulation finds no duplicated route feedback and verifies the intended administrative preference. This is the relevant evidence for the action: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes. The reason is: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains. The scenario is: A branch migration temporarily redistributes OSPF and BGP at separate hubs.

C.

The offered observation would test: Use L1/L2 boundaries and leak only policy-approved interlevel routes. It would not establish that the stated requirement has been met. The direct evidence needed here is: A failure simulation finds no duplicated route feedback and verifies the intended administrative preference.

D.

The offered observation would test: Implement documented local preference and community policy at controlled BGP boundaries. It would not establish that the stated requirement has been met. The direct evidence needed here is: A failure simulation finds no duplicated route feedback and verifies the intended administrative preference. The scenario is: A branch migration temporarily redistributes OSPF and BGP at separate hubs.

Question 367

In a separate customer architecture review, this issue arises: A branch migration temporarily redistributes OSPF and BGP at separate hubs. The customer requires clear acceptance tests before a new contract is signed. Which failure is the most direct risk of taking the tempting design shortcut?

  1. Traffic may exit through an unapproved path despite apparently healthy route adjacencies
  2. The enterprise faces brittle routing policy and difficult renumbering as sites multiply
  3. Routing feedback can create loops, unstable preference or unexpected reachability
  4. Sensitive traffic can violate contractual or regulatory boundaries during recovery

Answer & Explanations

Correct answer: C

A.

The offered consequence belongs to the alternative control path: Implement documented local preference and community policy at controlled BGP boundaries. The relevant failure for the current situation is: Routing feedback can create loops, unstable preference or unexpected reachability. The distinction follows from: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains. The scenario is: A branch migration temporarily redistributes OSPF and BGP at separate hubs.

B.

The offered consequence belongs to the alternative control path: Allocate hierarchical IPv6 prefixes per region and role with room for subnet growth. The relevant failure for the current situation is: Routing feedback can create loops, unstable preference or unexpected reachability. The distinction follows from: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains.

C.

Routing feedback can create loops, unstable preference or unexpected reachability. That is the risk in the reported situation—A branch migration temporarily redistributes OSPF and BGP at separate hubs. The corrective action is: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes. Technical basis: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains.

D.

The offered consequence belongs to the alternative control path: Translate data classification and service ownership into explicit path and segmentation policy. The relevant failure for the current situation is: Routing feedback can create loops, unstable preference or unexpected reachability. The distinction follows from: Route tags and constrained policy prevent loops when the same prefix traverses multiple protocol domains. The scenario is: A branch migration temporarily redistributes OSPF and BGP at separate hubs.

Question 368

In a separate customer architecture review, this issue arises: A branch migration temporarily redistributes OSPF and BGP at separate hubs. The customer requires clear acceptance tests before a new contract is signed. Which prerequisite should the architect confirm before choosing and defending this design?

  1. Know upstream delegation size, segment roles, growth and address management requirements
  2. Inventory LSA count, ABR redundancy, summarization assumptions and failure-path needs
  3. Assess L1/L2 connectivity, leaking policy, default routing behavior and dual-stack support
  4. Catalog prefix ownership, redistribution points, tags and route preference rules

Answer & Explanations

Correct answer: D

A.

The offered preparation belongs with the alternative action: Allocate hierarchical IPv6 prefixes per region and role with room for subnet growth. Here the necessary starting condition is: Catalog prefix ownership, redistribution points, tags and route preference rules. It supports: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes.

B.

The offered preparation belongs with the alternative action: Create area boundaries and resilient ABRs that localize topology changes without isolating reachability. Here the necessary starting condition is: Catalog prefix ownership, redistribution points, tags and route preference rules. It supports: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes.

C.

The offered preparation belongs with the alternative action: Use L1/L2 boundaries and leak only policy-approved interlevel routes. Here the necessary starting condition is: Catalog prefix ownership, redistribution points, tags and route preference rules. It supports: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes.

D.

The necessary starting condition is: Catalog prefix ownership, redistribution points, tags and route preference rules. This enables the action: Bound redistribution to explicit prefixes and tags, preventing reintroduction of learned routes. Validate the result with: A failure simulation finds no duplicated route feedback and verifies the intended administrative preference. The scenario is: A branch migration temporarily redistributes OSPF and BGP at separate hubs.

Question 369

A network design team is assessing this customer situation: One campus core change currently requires a company-wide freeze because all sites share the same change domain. A fixed procurement ceiling rules out indefinite capacity overprovisioning. Which high-level network design choice most directly meets the stated technical and operational requirement?

  1. Partition modules by failure, ownership and change cadence with carefully designed routed boundaries
  2. Separate reusable intent modules from region variables and enforce code ownership and review contracts
  3. Define prechange snapshots, staged checkpoints and objective rollback triggers for each dependency
  4. Select a topology that provides loop-free alternates and verify fast reroute feasibility for critical destinations

Answer & Explanations

Correct answer: A

A.

Modularity limits correlated operational impact without eliminating necessary inter-module connectivity. For the documented situation—One campus core change currently requires a company-wide freeze because all sites share the same change domain—the targeted response is: Partition modules by failure, ownership and change cadence with carefully designed routed boundaries. Check: A staged module maintenance test leaves unrelated applications within stated SLOs.

B.

Clear module interfaces reduce configuration drift without hiding region-specific routing requirements. That supports the alternative intervention: Separate reusable intent modules from region variables and enforce code ownership and review contracts. The present situation—One campus core change currently requires a company-wide freeze because all sites share the same change domain—instead calls for: Partition modules by failure, ownership and change cadence with carefully designed routed boundaries. Technical basis: Modularity limits correlated operational impact without eliminating necessary inter-module connectivity.

C.

The alternative addresses: Define prechange snapshots, staged checkpoints and objective rollback triggers for each dependency. Its principle is: Explicit go/no-go measurements allow reversible progress before hidden state diverges too far. In this case the needed action is: Partition modules by failure, ownership and change cadence with carefully designed routed boundaries. Confirm by: A staged module maintenance test leaves unrelated applications within stated SLOs.

D.

The alternative addresses a different technical concern: Fast local repair requires a valid alternate next hop; timer tuning cannot create nonexistent physical diversity. The governing mechanism here is: Modularity limits correlated operational impact without eliminating necessary inter-module connectivity. Accordingly, use: Partition modules by failure, ownership and change cadence with carefully designed routed boundaries.

Question 370

A network design team is assessing this customer situation: One campus core change currently requires a company-wide freeze because all sites share the same change domain. A fixed procurement ceiling rules out indefinite capacity overprovisioning. Which technical rationale best explains the proposed design choice under these constraints?

  1. Aggregation reduces control-plane scale but indiscriminate masking can hide the only valid failure path
  2. Modularity limits correlated operational impact without eliminating necessary inter-module connectivity
  3. OSPF flooding domains and summary design affect CPU load, SPF frequency and fault propagation
  4. Business expansion changes administrative domains, latency demands and allowed traffic paths

Answer & Explanations

Correct answer: B

A.

The alternative principle is: Aggregation reduces control-plane scale but indiscriminate masking can hide the only valid failure path. It instead explains this action: Summarize at stable boundaries while retaining explicitly required more-specific exceptions. For the present requirement, the controlling mechanism is: Modularity limits correlated operational impact without eliminating necessary inter-module connectivity.

B.

Modularity limits correlated operational impact without eliminating necessary inter-module connectivity. This explains the action: Partition modules by failure, ownership and change cadence with carefully designed routed boundaries. For the described facts—One campus core change currently requires a company-wide freeze because all sites share the same change domain—test the outcome through: A staged module maintenance test leaves unrelated applications within stated SLOs.

C.

The alternative principle is: OSPF flooding domains and summary design affect CPU load, SPF frequency and fault propagation. It instead explains this action: Create area boundaries and resilient ABRs that localize topology changes without isolating reachability. For the present requirement, the controlling mechanism is: Modularity limits correlated operational impact without eliminating necessary inter-module connectivity.

D.

The alternative principle is: Business expansion changes administrative domains, latency demands and allowed traffic paths. It instead explains this action: Define regional route, policy and service boundaries from business geography and data constraints. For the present requirement, the controlling mechanism is: Modularity limits correlated operational impact without eliminating necessary inter-module connectivity.

Cisco Certified Design Expert (400-007) Practice Tests