Pass Cisco 350-901 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
Cisco 350-901 Practice Test 13
Question 120
In the related Cisco ACI scenario: A finance application's database tier is attached to another application profile despite its correct tenant. Which focused diagnostic AND post-change acceptance evidence BEST demonstrate resolution?
Explanation
Correct Answer
The pre-change check should compare case-specific ACI object and operational records with this deciding evidence: APIC distinguished names and automation references show the database EPG beneath the wrong profile. Success criterion: Both approved tiers appear in the intended profile and use expected contracts. That check directly concerns APIC distinguished names and automation references show the database EPG beneath the wrong profile.
Incorrect Answers
Another investigation would compare case-specific ACI object and operational records with this deciding evidence: A single host outage would remove the entire virtual controller deployment. Success criterion: The intended controller service remains available during a tested underlying host failure. It does not directly establish the reported condition: APIC distinguished names and automation references show the database EPG beneath the wrong profile.
That check concerns a different signal: Compare case-specific ACI object and operational records with this deciding evidence: Its transport address and discovery logs disagree with the approved fabric TEP assignment. Success criterion: The leaf receives approved fabric addressing and joins the intended ACI pod. The case-relevant check is: Compare case-specific ACI object and operational records with this deciding evidence: APIC distinguished names and automation references show the database EPG beneath the wrong profile. Success criterion: Both approved tiers appear in the intended profile and use expected contracts.
Another investigation would compare case-specific ACI object and operational records with this deciding evidence: One fabric node cannot reach the NTP source configured by its fabric policy. Success criterion: Fabric logs align for a common event without rewriting preserved original evidence. It does not directly establish the reported condition: APIC distinguished names and automation references show the database EPG beneath the wrong profile.
Question 121
A fictional Cisco ACI engineering project has this problem: A request assumes two different tenant VRFs will exchange packets solely because they share a subnet name. Diagnostic observation: Routing tables remain logically separate despite each bridge domain having a valid gateway. Which scoped engineering response is BEST?
Explanation
Correct Answer
Routing tables remain logically separate despite each bridge domain having a valid gateway. Separate VRFs are distinct Layer 3 routing contexts, not automatically interconnected by matching subnet names. The appropriate response is: Preserve VRF segmentation and design only explicitly authorized supported external connectivity. Confirm it with: Each application routes in its VRF and unapproved cross-context traffic is blocked.
Incorrect Answers
Another proposed action is: Use a supported ACI leaf-spine topology with endpoints on leaf access interfaces. It targets a different dependency; the evidence here is Routing tables remain logically separate despite each bridge domain having a valid gateway.
Another option proposes: Separate governance boundaries into suitable tenant containers with explicit approved sharing. The specific correction is: Preserve VRF segmentation and design only explicitly authorized supported external connectivity. The deciding evidence is: Routing tables remain logically separate despite each bridge domain having a valid gateway.
That alternative concerns: Check discovery prerequisites and correct the address and registration path rather than reimage blindly. The relevant evidence is Routing tables remain logically separate despite each bridge domain having a valid gateway. The corresponding fix is: Preserve VRF segmentation and design only explicitly authorized supported external connectivity.
Question 122
An ACI implementation encounters: A request assumes two different tenant VRFs will exchange packets solely because they share a subnet name. Which technical evidence BEST identifies the particular failure?
Explanation
Correct Answer
Consider this evidence: Routing tables remain logically separate despite each bridge domain having a valid gateway. The applicable explanation is: Separate VRFs are distinct Layer 3 routing contexts, not automatically interconnected by matching subnet names. The matching response is: Preserve VRF segmentation and design only explicitly authorized supported external connectivity.
Incorrect Answers
This other option describes: Decisive observed evidence: Policy inspection finds orphaned logical objects without end-to-end workload classification. The problem to explain is different: Routing tables remain logically separate despite each bridge domain having a valid gateway.
Another proposed finding is: Decisive observed evidence: The APIC audit log records an EPG contract removal at the beginning of the outage. It is not the recorded discriminator, which is Routing tables remain logically separate despite each bridge domain having a valid gateway.
That alternative considers the following evidence: The endpoint inventory follows a shared security label across different bridge domains as decisive. The actual evidence in this case is Routing tables remain logically separate despite each bridge domain having a valid gateway.
Question 123
An engineer proposes this ACI correction: Preserve VRF segmentation and design only explicitly authorized supported external connectivity. Which independently observable outcome BEST verifies it?
Explanation
Correct Answer
Each application routes in its VRF and unapproved cross-context traffic is blocked. This verifies the required result rather than merely stating the action; the original issue was Routing tables remain logically separate despite each bridge domain having a valid gateway.
Incorrect Answers
That result would assess another condition: The intended controller service remains available during a tested underlying host failure. The correct criterion is directly linked to the finding: Routing tables remain logically separate despite each bridge domain having a valid gateway.
Another proposed result is: The critical fault is resolved or risk accepted and the affected service passes tests. It would not independently establish the required outcome: Each application routes in its VRF and unapproved cross-context traffic is blocked.
A different option checks: The server VLAN deploys correctly and node time remains synchronized. The case-specific acceptance condition is instead Each application routes in its VRF and unapproved cross-context traffic is blocked.
Question 124
A Cisco ACI change review investigates: A request assumes two different tenant VRFs will exchange packets solely because they share a subnet name. Observed evidence: Routing tables remain logically separate despite each bridge domain having a valid gateway. Which architectural or operational principle BEST applies?
Explanation
Correct Answer
The observed evidence is: Routing tables remain logically separate despite each bridge domain having a valid gateway. The governing principle is: Separate VRFs are distinct Layer 3 routing contexts, not automatically interconnected by matching subnet names. Consequently, the targeted action is: Preserve VRF segmentation and design only explicitly authorized supported external connectivity.
Incorrect Answers
This alternative invokes: Policy inspection finds orphaned logical objects without end-to-end workload classification. Appropriate ACI operational principle: Tenant, routing, bridge, application and classification objects require consistent relationships for actual connectivity. The governing distinction for the recorded case is Separate VRFs are distinct Layer 3 routing contexts, not automatically interconnected by matching subnet names.
The competing option invokes: The APIC audit log records an EPG contract removal at the beginning of the outage. Appropriate ACI operational principle: Fault, audit, event and health observations describe different dimensions of operational state and must be correlated. The present evidence is: Routing tables remain logically separate despite each bridge domain having a valid gateway. The case-relevant principle is: Separate VRFs are distinct Layer 3 routing contexts, not automatically interconnected by matching subnet names.
That principle concerns another fact pattern: One fabric node cannot reach the NTP source configured by its fabric policy. Appropriate ACI operational principle: Fabric-wide policy controls infrastructure services and should not be edited to fix an unrelated endpoint attachment. Here the key fact is: Routing tables remain logically separate despite each bridge domain having a valid gateway.
Question 125
In a deliberately RELATED second view of the same fictional ACI problem: A request assumes two different tenant VRFs will exchange packets solely because they share a subnet name. Which evidence-action-proof sequence is most defensible?
Explanation
Correct Answer
The starting point is Routing tables remain logically separate despite each bridge domain having a valid gateway. The proposed action and its separate check are Preserve VRF segmentation and design only explicitly authorized supported external connectivity and Each application routes in its VRF and unapproved cross-context traffic is blocked, respectively.
Incorrect Answers
Another action-and-check pairing is: Inspect the observed evidence: A single host outage would remove the entire virtual controller deployment. Apply the controlled action: Distribute supported virtual APIC instances across verified independent failure domains. Validate the separate result: The intended controller service remains available during a tested underlying host failure. The evidence here is Routing tables remain logically separate despite each bridge domain having a valid gateway. The required action and proof are Preserve VRF segmentation and design only explicitly authorized supported external connectivity and Each application routes in its VRF and unapproved cross-context traffic is blocked.
A different plan would inspect the observed evidence: The model is absent from the target software release's supported hardware matrix. Apply the controlled action: Validate exact hardware, line cards and code train and select supported replacements. Validate the separate result: Every purchased node and its interfaces are qualified for the chosen ACI release. It does not test the case-specific condition: Routing tables remain logically separate despite each bridge domain having a valid gateway.
Another combination would inspect the observed evidence: The endpoint inventory follows a shared security label across different bridge domains. Apply the controlled action: Apply a supported endpoint security group design with validated membership and precedence. Validate the separate result: Regulated endpoints retain the intended policies after supported movements. The current record instead supports Preserve VRF segmentation and design only explicitly authorized supported external connectivity, verified by Each application routes in its VRF and unapproved cross-context traffic is blocked.
Question 126
An ACI team must address: A request assumes two different tenant VRFs will exchange packets solely because they share a subnet name. Which corrective action AND independent verification make the BEST pair?
Explanation
Correct Answer
The starting point is Routing tables remain logically separate despite each bridge domain having a valid gateway. The proposed action and its separate check are Preserve VRF segmentation and design only explicitly authorized supported external connectivity and Each application routes in its VRF and unapproved cross-context traffic is blocked, respectively. For the current case, the offered answer is Preserve VRF segmentation and design only explicitly authorized supported external connectivity. Independently observable proof: Each application routes in its VRF and unapproved cross-context traffic is blocked.
Incorrect Answers
Another potential sequence is: Use a supported ACI leaf-spine topology with endpoints on leaf access interfaces. Independently observable proof: Approved fabric discovery and test traffic follow supported host-to-leaf-to-spine paths. It has no direct link to the distinguishing evidence: Routing tables remain logically separate despite each bridge domain having a valid gateway.
Another action-and-check pairing is: Complete the required logical construct relationships and their attachment policies. Independently observable proof: Workloads learn under intended EPGs and authorized flows route in the correct VRF. The evidence here is Routing tables remain logically separate despite each bridge domain having a valid gateway. The required action and proof are Preserve VRF segmentation and design only explicitly authorized supported external connectivity and Each application routes in its VRF and unapproved cross-context traffic is blocked.
Another possible combination is: Correct the reviewed contract role and filter scope rather than opening universal access. Independently observable proof: Only approved web-to-database sessions succeed and other traffic remains denied. The current record instead supports Preserve VRF segmentation and design only explicitly authorized supported external connectivity, verified by Each application routes in its VRF and unapproved cross-context traffic is blocked.
Question 127
While implementing this supported-intent ACI correction: Preserve VRF segmentation and design only explicitly authorized supported external connectivity. Which material security or operational caveat matters most?
Explanation
Correct Answer
The risk to retain is: Merging VRFs to resolve one service request may dissolve required segmentation. The original evidence is Routing tables remain logically separate despite each bridge domain having a valid gateway; widening the change beyond it is not justified.
Incorrect Answers
Another emphasis concerns: Broad physical fabric resets can conceal a narrow policy regression. The current change is Preserve VRF segmentation and design only explicitly authorized supported external connectivity; the material limitation is Merging VRFs to resolve one service request may dissolve required segmentation.
This limitation concerns another setting: Creating a tenant name alone does not establish connectivity or isolation. The observed facts here make a different caution decisive: Merging VRFs to resolve one service request may dissolve required segmentation.
Another caution is: Generic Ethernet interoperability is not evidence of supported ACI operation. The key risk in this case is: Merging VRFs to resolve one service request may dissolve required segmentation.
Question 128
In the related Cisco ACI scenario: A request assumes two different tenant VRFs will exchange packets solely because they share a subnet name. Which focused diagnostic AND post-change acceptance evidence BEST demonstrate resolution?
Explanation
Correct Answer
The pre-change check should compare case-specific ACI object and operational records with this deciding evidence: Routing tables remain logically separate despite each bridge domain having a valid gateway. Success criterion: Each application routes in its VRF and unapproved cross-context traffic is blocked. That check directly concerns Routing tables remain logically separate despite each bridge domain having a valid gateway.
Incorrect Answers
That check concerns a different signal: Compare case-specific ACI object and operational records with this deciding evidence: The AEP omits the physical domain and VLAN pool needed for the intended encapsulation. Success criterion: The EPG deploys on the port with correct VLAN and endpoint classification. The case-relevant check is: Compare case-specific ACI object and operational records with this deciding evidence: Routing tables remain logically separate despite each bridge domain having a valid gateway. Success criterion: Each application routes in its VRF and unapproved cross-context traffic is blocked.
Another check would compare case-specific ACI object and operational records with this deciding evidence: APIC rejects the distinguished name because the required parent relationship is missing. Success criterion: APIC accepts the object tree and deploys the EPG in its intended profile. The case observation to isolate is Routing tables remain logically separate despite each bridge domain having a valid gateway. The focused check here is: Compare case-specific ACI object and operational records with this deciding evidence: Routing tables remain logically separate despite each bridge domain having a valid gateway. Success criterion: Each application routes in its VRF and unapproved cross-context traffic is blocked.
Another investigation would compare case-specific ACI object and operational records with this deciding evidence: A single host outage would remove the entire virtual controller deployment. Success criterion: The intended controller service remains available during a tested underlying host failure. It does not directly establish the reported condition: Routing tables remain logically separate despite each bridge domain having a valid gateway.
Question 129
A fictional Cisco ACI engineering project has this problem: A client can switch locally but fails to reach another subnet inside the approved routing context. Diagnostic observation: The bridge domain lacks the intended SVI subnet and unicast routing configuration. Which scoped engineering response is BEST?
Explanation
Correct Answer
The issue turns on the bridge domain lacks the intended SVI subnet and unicast routing configuration. The relevant rule is that a bridge domain defines Layer 2 forwarding behavior and optional routed gateway subnet policy. The targeted correction is: Configure the approved bridge-domain subnet and unicast routing behavior with reviewed contracts.
Incorrect Answers
A different alternative is: Review consumers before changing shared policy, isolating tenant-specific intent where required. It does not establish the necessary outcome: Clients reach their intended gateway and authorized routed destinations.
Another proposed action is: Distribute supported virtual APIC instances across verified independent failure domains. That does not directly address the observed condition: The bridge domain lacks the intended SVI subnet and unicast routing configuration. The more targeted correction is: Configure the approved bridge-domain subnet and unicast routing behavior with reviewed contracts.
Another proposed action is: Repair the access-policy chain and preserve unrelated fabric-wide service settings. It targets a different dependency; the evidence here is the bridge domain lacks the intended SVI subnet and unicast routing configuration.
Question 130
An ACI implementation encounters: A client can switch locally but fails to reach another subnet inside the approved routing context. Which technical evidence BEST identifies the particular failure?
Explanation
Correct Answer
The deciding evidence is: The bridge domain lacks the intended SVI subnet and unicast routing configuration. This distinguishes the problem because a bridge domain defines Layer 2 forwarding behavior and optional routed gateway subnet policy. The response it supports is: Configure the approved bridge-domain subnet and unicast routing behavior with reviewed contracts.
Incorrect Answers
This other option describes: Decisive observed evidence: The access path lacks an appropriate domain binding while NTP remains healthy. The problem to explain is different: The bridge domain lacks the intended SVI subnet and unicast routing configuration.
Another proposed finding is: Decisive observed evidence: APIC rejects the distinguished name because the required parent relationship is missing. It is not the recorded discriminator, which is the bridge domain lacks the intended SVI subnet and unicast routing configuration.
That other evidence is: One fabric node cannot reach the NTP source configured by its fabric policy. The current incident instead shows: The bridge domain lacks the intended SVI subnet and unicast routing configuration. This distinction supports the action: Configure the approved bridge-domain subnet and unicast routing behavior with reviewed contracts.
Designing, Deploying, and Managing Network Automation Systems (350-901) Practice Tests
- Cisco 350-901 Practice Test 11 - 10 Questions (Last Reviewed 07-Nov-2026)
- Cisco 350-901 Practice Test 12 - 10 Questions (Last Reviewed 06-Nov-2026)
- Cisco 350-901 Practice Test 13 - 10 Questions (Last Reviewed 05-Nov-2026)
- Cisco 350-901 Practice Test 14 - 10 Questions (Last Reviewed 04-Nov-2026)
- Cisco 350-901 Practice Test 15 - 10 Questions (Last Reviewed 03-Nov-2026)
