Cisco 300-610 Practice Test 24
Question 230
At a 60-rack compute cluster, a post-incident design review focuses on preventing: Two workloads use different ACI EPGs but an architect assumes that automatically permits any traffic between them. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?
- Validate IP address overlap before approving bridge-domain changes.
- Monitor attribute drift and unintended EPG reassignment.
- Review contracts when application tiers or ports change.
- Document which queues truly require no-drop behavior.
Explanation
Correct Answer
C:The most relevant ongoing safeguard is: Review contracts when application tiers or ports change. The risk it addresses is: Two workloads use different ACI EPGs but an architect assumes that automatically permits any traffic between them. This check is tied to the technical principle: EPG membership and contract policy determine how ACI handles allowed communication; different EPGs can require explicit contracts. The immediate correction remains: Define least-privilege EPG contracts with necessary subjects and filters for intended application flows. Periodically validate the safeguard through two different observations. Inspect EPG bindings and effective contract relationships Test one allowed application connection and one forbidden port. The continuing acceptance target is: Only approved inter-EPG traffic flows and unauthorized services remain denied.
Incorrect Answers
A:This is a continuing control for aci vrf and bridge domain scope; its underlying principle is: Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT. The recurring risk here is different: Two workloads use different ACI EPGs but an architect assumes that automatically permits any traffic between them. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The intended long-term acceptance condition remains: Only approved inter-EPG traffic flows and unauthorized services remain denied.
B:This is a continuing control for aci microsegmentation attribute selection; its underlying principle is: Attribute-based EPG selection can support workload-aware segmentation where identity and orchestration metadata are reliably maintained. The recurring risk here is different: Two workloads use different ACI EPGs but an architect assumes that automatically permits any traffic between them. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A security policy groups every virtual machine by static VLAN when workloads are frequently created and moved by orchestration. The intended long-term acceptance condition remains: Only approved inter-EPG traffic flows and unauthorized services remain denied.
D:This is a continuing control for avoiding global pause for ai traffic; its underlying principle is: Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback. The recurring risk here is different: Two workloads use different ACI EPGs but an architect assumes that automatically permits any traffic between them. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The intended long-term acceptance condition remains: Only approved inter-EPG traffic flows and unauthorized services remain denied.
Question 231
At a virtualized application data center, during a controlled design review, the team discovers: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?
- Use supported dynamic endpoint selectors with tested precedence rather than relying solely on manually assigned VLANs.
- Assign overlapping tenants to independent VRFs or introduce deliberate translation and routed policy.
- Align Layer 2 VNIs, VRFs and routed security controls to the approved segmentation model.
- Enable documented PFC watchdog handling with a planned drop and recovery policy for the affected class.
Explanation
Correct Answer
B:The relevant failure is: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The technical distinction is: Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT. The targeted correction is: Assign overlapping tenants to independent VRFs or introduce deliberate translation and routed policy. Before changing the design, check two independent observations. Compare VRF and bridge-domain associations Test identical-prefix reachability from each tenant context. Accept the change only if: Overlapping workloads do not collide or leak through one routing table.
Incorrect Answers
A:This action targets aci microsegmentation attribute selection, where the mechanism is: Attribute-based EPG selection can support workload-aware segmentation where identity and orchestration metadata are reliably maintained. That is a separate condition from the problem in this question: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. Even a successful repair of the alternative would not establish the required result: Overlapping workloads do not collide or leak through one routing table. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
C:This action targets vxlan segmentation without policy, where the mechanism is: Overlay segment identifiers alone do not enforce full tenant isolation if routing and firewall policies permit cross-context reachability. That is a separate condition from the problem in this question: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. Even a successful repair of the alternative would not establish the required result: Overlapping workloads do not collide or leak through one routing table. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
D:This action targets pfc watchdog failure handling, where the mechanism is: Prolonged priority pause can cause PFC deadlock; a supported watchdog can detect and break pathological pauses. That is a separate condition from the problem in this question: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. Even a successful repair of the alternative would not establish the required result: Overlapping workloads do not collide or leak through one routing table. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
Question 232
At an AI-training data-center pod, before changing the fabric, the team observes: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. Acceptance requires evidence from the running system, not just the saved design. Which pair of observations most directly tests the proposed diagnosis before a change?
- Inspect VNI-to-VRF mappings and inter-VRF route leaking; probe permitted and denied synthetic flows at the gateway.
- Inspect actual workload attributes and resulting EPG membership; move a test workload and verify contract enforcement follows its intended role.
- Map request and response paths against the permitted regions; inspect storage, logging and telemetry endpoints for unintended cross-region transfer.
- Compare VRF and bridge-domain associations; test identical-prefix reachability from each tenant context.
Explanation
Correct Answer
D:The first observation is: Compare VRF and bridge-domain associations The independent second observation is: Test identical-prefix reachability from each tenant context. Together they test the proposed diagnosis of this incident: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The underlying technical principle is: Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT. If those checks confirm it, the appropriate next action is: Assign overlapping tenants to independent VRFs or introduce deliberate translation and routed policy. The expected measurable result is: Overlapping workloads do not collide or leak through one routing table.
Incorrect Answers
A:These observations investigate vxlan segmentation without policy; they would be useful if the symptoms were: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. That alternative rests on the principle: Overlay segment identifiers alone do not enforce full tenant isolation if routing and firewall policies permit cross-context reachability. The question instead asks for evidence about: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The discriminating observations here are: Compare VRF and bridge-domain associations Test identical-prefix reachability from each tenant context.
B:These observations investigate aci microsegmentation attribute selection; they would be useful if the symptoms were: A security policy groups every virtual machine by static VLAN when workloads are frequently created and moved by orchestration. That alternative rests on the principle: Attribute-based EPG selection can support workload-aware segmentation where identity and orchestration metadata are reliably maintained. The question instead asks for evidence about: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The discriminating observations here are: Compare VRF and bridge-domain associations Test identical-prefix reachability from each tenant context.
C:These observations investigate inference model placement for privacy; they would be useful if the symptoms were: Sensitive inference inputs must remain inside a regulated region but a proposed design sends requests to a remote shared accelerator site. That alternative rests on the principle: Data placement and accelerator resource pooling are separate design choices; inference service location must respect residency and access controls. The question instead asks for evidence about: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The discriminating observations here are: Compare VRF and bridge-domain associations Test identical-prefix reachability from each tenant context.
Question 233
At a regulated private-cloud campus, the data-center team needs to explain this behavior: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?
- Attribute-based EPG selection can support workload-aware segmentation where identity and orchestration metadata are reliably maintained.
- Overlay segment identifiers alone do not enforce full tenant isolation if routing and firewall policies permit cross-context reachability.
- Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT.
- Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix.
Explanation
Correct Answer
C:The controlling technical principle is: Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT. This matters because the reported design failure is: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The first diagnostic check is: Compare VRF and bridge-domain associations The independent check is: Test identical-prefix reachability from each tenant context. These facts support the targeted intervention: Assign overlapping tenants to independent VRFs or introduce deliberate translation and routed policy. Confirm that the resulting design meets this condition: Overlapping workloads do not collide or leak through one routing table.
Incorrect Answers
A:The offered principle describes aci microsegmentation attribute selection: Attribute-based EPG selection can support workload-aware segmentation where identity and orchestration metadata are reliably maintained. That is useful for a distinct incident, such as: A security policy groups every virtual machine by static VLAN when workloads are frequently created and moved by orchestration. It does not account for the reported failure: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The governing principle in this situation is: Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT.
B:The offered principle describes vxlan segmentation without policy: Overlay segment identifiers alone do not enforce full tenant isolation if routing and firewall policies permit cross-context reachability. That is useful for a distinct incident, such as: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. It does not account for the reported failure: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The governing principle in this situation is: Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT.
D:The offered principle describes ip mobility with stretched routed boundaries: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix. That is useful for a distinct incident, such as: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. It does not account for the reported failure: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The governing principle in this situation is: Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT.
Question 234
At a dual-spine infrastructure project, the team completed an authorized repair for: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?
- Tenant segmentation holds across bridged and routed paths.
- Only approved inter-EPG traffic flows and unauthorized services remain denied.
- Overlapping workloads do not collide or leak through one routing table.
- End-to-end inference traffic and retained records stay within the allowed locality without violating latency SLOs.
Explanation
Correct Answer
C:The relevant measurable success criterion is: Overlapping workloads do not collide or leak through one routing table. It addresses the original reported defect: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Compare VRF and bridge-domain associations Test identical-prefix reachability from each tenant context. The correction being evaluated is: Assign overlapping tenants to independent VRFs or introduce deliberate translation and routed policy. The underlying reason that correction matters is: Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT.
Incorrect Answers
A:This metric would help validate a correction to vxlan segmentation without policy, rather than the original reported issue. The other issue is: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. Here the defect to be resolved is: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The expected measurable outcome for the actual incident is: Overlapping workloads do not collide or leak through one routing table. A positive result for the other service would not prove this requirement is met.
B:This metric would help validate a correction to aci epg policy segmentation, rather than the original reported issue. The other issue is: Two workloads use different ACI EPGs but an architect assumes that automatically permits any traffic between them. Here the defect to be resolved is: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The expected measurable outcome for the actual incident is: Overlapping workloads do not collide or leak through one routing table. A positive result for the other service would not prove this requirement is met.
D:This metric would help validate a correction to inference model placement for privacy, rather than the original reported issue. The other issue is: Sensitive inference inputs must remain inside a regulated region but a proposed design sends requests to a remote shared accelerator site. Here the defect to be resolved is: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The expected measurable outcome for the actual incident is: Overlapping workloads do not collide or leak through one routing table. A positive result for the other service would not prove this requirement is met.
Question 235
At a low-latency GPU workload fabric, the architecture standards group considers the recurring risk: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?
- Validate IP address overlap before approving bridge-domain changes.
- Audit inter-VRF connectivity after gateway or security policy changes.
- Monitor attribute drift and unintended EPG reassignment.
- Validate member-level hot spots when workload flow count changes.
Explanation
Correct Answer
A:The most relevant ongoing safeguard is: Validate IP address overlap before approving bridge-domain changes. The risk it addresses is: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. This check is tied to the technical principle: Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT. The immediate correction remains: Assign overlapping tenants to independent VRFs or introduce deliberate translation and routed policy. Periodically validate the safeguard through two different observations. Compare VRF and bridge-domain associations Test identical-prefix reachability from each tenant context. The continuing acceptance target is: Overlapping workloads do not collide or leak through one routing table.
Incorrect Answers
B:This is a continuing control for vxlan segmentation without policy; its underlying principle is: Overlay segment identifiers alone do not enforce full tenant isolation if routing and firewall policies permit cross-context reachability. The recurring risk here is different: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The intended long-term acceptance condition remains: Overlapping workloads do not collide or leak through one routing table.
C:This is a continuing control for aci microsegmentation attribute selection; its underlying principle is: Attribute-based EPG selection can support workload-aware segmentation where identity and orchestration metadata are reliably maintained. The recurring risk here is different: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A security policy groups every virtual machine by static VLAN when workloads are frequently created and moved by orchestration. The intended long-term acceptance condition remains: Overlapping workloads do not collide or leak through one routing table.
D:This is a continuing control for lacp hashing and a single large flow; its underlying principle is: LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links. The recurring risk here is different: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member links. The intended long-term acceptance condition remains: Overlapping workloads do not collide or leak through one routing table.
Question 236
At a two-region enterprise VXLAN fabric, a proposed deployment has this failure mode: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?
- Define least-privilege EPG contracts with necessary subjects and filters for intended application flows.
- Align Layer 2 VNIs, VRFs and routed security controls to the approved segmentation model.
- Assign overlapping tenants to independent VRFs or introduce deliberate translation and routed policy.
- Include checkpoint bandwidth, storage ingestion and job restart targets in the fabric and storage service design.
Explanation
Correct Answer
B:The relevant failure is: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The technical distinction is: Overlay segment identifiers alone do not enforce full tenant isolation if routing and firewall policies permit cross-context reachability. The targeted correction is: Align Layer 2 VNIs, VRFs and routed security controls to the approved segmentation model. Before changing the design, check two independent observations. Inspect VNI-to-VRF mappings and inter-VRF route leaking Probe permitted and denied synthetic flows at the gateway. Accept the change only if: Tenant segmentation holds across bridged and routed paths.
Incorrect Answers
A:This action targets aci epg policy segmentation, where the mechanism is: EPG membership and contract policy determine how ACI handles allowed communication; different EPGs can require explicit contracts. That is a separate condition from the problem in this question: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. Even a successful repair of the alternative would not establish the required result: Tenant segmentation holds across bridged and routed paths. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
C:This action targets aci vrf and bridge domain scope, where the mechanism is: Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT. That is a separate condition from the problem in this question: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. Even a successful repair of the alternative would not establish the required result: Tenant segmentation holds across bridged and routed paths. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
D:This action targets ai training checkpoint traffic, where the mechanism is: Periodic model checkpoints create bursty storage traffic requiring predictable paths to persistent storage beyond the GPU interconnect. That is a separate condition from the problem in this question: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. Even a successful repair of the alternative would not establish the required result: Tenant segmentation holds across bridged and routed paths. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
Question 237
At a 60-rack compute cluster, the cause remains unconfirmed for this reported issue: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. Acceptance requires evidence from the running system, not just the saved design. Which pair of observations most directly tests the proposed diagnosis before a change?
- Inspect actual workload attributes and resulting EPG membership; move a test workload and verify contract enforcement follows its intended role.
- Compare VRF and bridge-domain associations; test identical-prefix reachability from each tenant context.
- Inspect DSCP-to-queue mapping from endpoints to leaf; compare pause and drop counters by priority during backup bursts.
- Inspect VNI-to-VRF mappings and inter-VRF route leaking; probe permitted and denied synthetic flows at the gateway.
Explanation
Correct Answer
D:The first observation is: Inspect VNI-to-VRF mappings and inter-VRF route leaking The independent second observation is: Probe permitted and denied synthetic flows at the gateway. Together they test the proposed diagnosis of this incident: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The underlying technical principle is: Overlay segment identifiers alone do not enforce full tenant isolation if routing and firewall policies permit cross-context reachability. If those checks confirm it, the appropriate next action is: Align Layer 2 VNIs, VRFs and routed security controls to the approved segmentation model. The expected measurable result is: Tenant segmentation holds across bridged and routed paths.
Incorrect Answers
A:These observations investigate aci microsegmentation attribute selection; they would be useful if the symptoms were: A security policy groups every virtual machine by static VLAN when workloads are frequently created and moved by orchestration. That alternative rests on the principle: Attribute-based EPG selection can support workload-aware segmentation where identity and orchestration metadata are reliably maintained. The question instead asks for evidence about: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The discriminating observations here are: Inspect VNI-to-VRF mappings and inter-VRF route leaking Probe permitted and denied synthetic flows at the gateway.
B:These observations investigate aci vrf and bridge domain scope; they would be useful if the symptoms were: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. That alternative rests on the principle: Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT. The question instead asks for evidence about: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The discriminating observations here are: Inspect VNI-to-VRF mappings and inter-VRF route leaking Probe permitted and denied synthetic flows at the gateway.
C:These observations investigate rdma traffic isolation; they would be useful if the symptoms were: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. That alternative rests on the principle: RDMA no-drop behavior is commonly applied only to selected traffic classes; bulk flows should not automatically share the PFC priority. The question instead asks for evidence about: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The discriminating observations here are: Inspect VNI-to-VRF mappings and inter-VRF route leaking Probe permitted and denied synthetic flows at the gateway.
Question 238
At a virtualized application data center, a failure review must identify the central technical cause of: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?
- Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT.
- Attribute-based EPG selection can support workload-aware segmentation where identity and orchestration metadata are reliably maintained.
- Controller availability and telemetry collection are independent; missing device streams can hide fabric degradation.
- Overlay segment identifiers alone do not enforce full tenant isolation if routing and firewall policies permit cross-context reachability.
Explanation
Correct Answer
D:The controlling technical principle is: Overlay segment identifiers alone do not enforce full tenant isolation if routing and firewall policies permit cross-context reachability. This matters because the reported design failure is: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The first diagnostic check is: Inspect VNI-to-VRF mappings and inter-VRF route leaking The independent check is: Probe permitted and denied synthetic flows at the gateway. These facts support the targeted intervention: Align Layer 2 VNIs, VRFs and routed security controls to the approved segmentation model. Confirm that the resulting design meets this condition: Tenant segmentation holds across bridged and routed paths.
Incorrect Answers
A:The offered principle describes aci vrf and bridge domain scope: Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT. That is useful for a distinct incident, such as: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. It does not account for the reported failure: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The governing principle in this situation is: Overlay segment identifiers alone do not enforce full tenant isolation if routing and firewall policies permit cross-context reachability.
B:The offered principle describes aci microsegmentation attribute selection: Attribute-based EPG selection can support workload-aware segmentation where identity and orchestration metadata are reliably maintained. That is useful for a distinct incident, such as: A security policy groups every virtual machine by static VLAN when workloads are frequently created and moved by orchestration. It does not account for the reported failure: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The governing principle in this situation is: Overlay segment identifiers alone do not enforce full tenant isolation if routing and firewall policies permit cross-context reachability.
C:The offered principle describes monitoring telemetry collection loss: Controller availability and telemetry collection are independent; missing device streams can hide fabric degradation. That is useful for a distinct incident, such as: Nexus Dashboard remains available but an operator assumes that means every spine and leaf is delivering complete telemetry. It does not account for the reported failure: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The governing principle in this situation is: Overlay segment identifiers alone do not enforce full tenant isolation if routing and firewall policies permit cross-context reachability.
Question 239
At an AI-training data-center pod, the service owner needs evidence of resolution for: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?
- Only approved inter-EPG traffic flows and unauthorized services remain denied.
- Overlapping workloads do not collide or leak through one routing table.
- Both uplinks carry the intended VLANs with deterministic redundancy.
- Tenant segmentation holds across bridged and routed paths.
Explanation
Correct Answer
D:The relevant measurable success criterion is: Tenant segmentation holds across bridged and routed paths. It addresses the original reported defect: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Inspect VNI-to-VRF mappings and inter-VRF route leaking Probe permitted and denied synthetic flows at the gateway. The correction being evaluated is: Align Layer 2 VNIs, VRFs and routed security controls to the approved segmentation model. The underlying reason that correction matters is: Overlay segment identifiers alone do not enforce full tenant isolation if routing and firewall policies permit cross-context reachability.
Incorrect Answers
A:This metric would help validate a correction to aci epg policy segmentation, rather than the original reported issue. The other issue is: Two workloads use different ACI EPGs but an architect assumes that automatically permits any traffic between them. Here the defect to be resolved is: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The expected measurable outcome for the actual incident is: Tenant segmentation holds across bridged and routed paths. A positive result for the other service would not prove this requirement is met.
B:This metric would help validate a correction to aci vrf and bridge domain scope, rather than the original reported issue. The other issue is: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. Here the defect to be resolved is: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The expected measurable outcome for the actual incident is: Tenant segmentation holds across bridged and routed paths. A positive result for the other service would not prove this requirement is met.
C:This metric would help validate a correction to dual-homed server vpc consistency, rather than the original reported issue. The other issue is: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. Here the defect to be resolved is: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The expected measurable outcome for the actual incident is: Tenant segmentation holds across bridged and routed paths. A positive result for the other service would not prove this requirement is met.
Question 240
At a regulated private-cloud campus, after correction, the team wants to prevent recurrence of: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?
- Validate IP address overlap before approving bridge-domain changes.
- Audit inter-VRF connectivity after gateway or security policy changes.
- Monitor attribute drift and unintended EPG reassignment.
- Preserve adapter-to-fabric compatibility matrices for future accelerator purchases.
Explanation
Correct Answer
B:The most relevant ongoing safeguard is: Audit inter-VRF connectivity after gateway or security policy changes. The risk it addresses is: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. This check is tied to the technical principle: Overlay segment identifiers alone do not enforce full tenant isolation if routing and firewall policies permit cross-context reachability. The immediate correction remains: Align Layer 2 VNIs, VRFs and routed security controls to the approved segmentation model. Periodically validate the safeguard through two different observations. Inspect VNI-to-VRF mappings and inter-VRF route leaking Probe permitted and denied synthetic flows at the gateway. The continuing acceptance target is: Tenant segmentation holds across bridged and routed paths.
Incorrect Answers
A:This is a continuing control for aci vrf and bridge domain scope; its underlying principle is: Bridge-domain segmentation and VRF routing scope are different; overlapping routing prefixes generally need separate routing contexts or compatible NAT. The recurring risk here is different: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: An ACI tenant design creates several bridge domains in one VRF and expects overlapping IP subnets to remain isolated without further design. The intended long-term acceptance condition remains: Tenant segmentation holds across bridged and routed paths.
C:This is a continuing control for aci microsegmentation attribute selection; its underlying principle is: Attribute-based EPG selection can support workload-aware segmentation where identity and orchestration metadata are reliably maintained. The recurring risk here is different: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A security policy groups every virtual machine by static VLAN when workloads are frequently created and moved by orchestration. The intended long-term acceptance condition remains: Tenant segmentation holds across bridged and routed paths.
D:This is a continuing control for infiniband versus ethernet compatibility; its underlying principle is: InfiniBand and Ethernet have different link-layer protocols and must use the matching network fabric or supported interworking design. The recurring risk here is different: A VXLAN VNI separates workloads at Layer 2 but traffic still crosses routed tenant boundaries through a shared gateway. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A cluster order assumes InfiniBand host adapters can be connected directly to ordinary Ethernet switch ports without a suitable gateway. The intended long-term acceptance condition remains: Tenant segmentation holds across bridged and routed paths.