Question 370An insurer enables 802.1X on all ports but does not plan authentication for legacy life-safety controllers. What is the most direct design risk if this remains unresolved? One facilities incident could disable enforcement and the application path simultaneously. A compromised display could become a bridge into payment card infrastructure. A blanket fallback could let rogue equipment onto sensitive operational networks. An abuse investigation could blame the wrong application or miss illicit data transfer. ExplanationCorrect Answer C:A blanket fallback could let rogue equipment onto sensitive operational networks. Leaving the defect uncorrected makes this outcome credible. Network admission controls should account for constrained devices without creating broad unauthenticated trust. Remedy: Use tightly scoped certificate or device-identity exceptions with restricted segmentation and monitoring. Incorrect Answers A:Security service availability depends on power and site topology as well as policy logic. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A blanket fallback could let rogue equipment onto sensitive operational networks. B:Payment-processing security boundaries should follow regulated data flows instead of branch location. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A blanket fallback could let rogue equipment onto sensitive operational networks. D:Source attribution and policy verification deteriorate when unrelated trust zones share untraceable egress. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A blanket fallback could let rogue equipment onto sensitive operational networks.
Question 371A pharmaceutical company asks to stretch a sensitive research VLAN to its disaster recovery site solely to avoid renumbering a legacy app. Which network architecture decision best meets these requirements? Prefer an application-specific recovery bridge or controlled translation with tight fault-domain limits. Forecast throughput and delay at peak write volume and test the chosen replication placement. Provide dynamic service discovery and health-aware load distribution for scaled inference endpoints. Design translator redundancy and state continuity for the required IPv6-to-IPv4 flows. ExplanationCorrect Answer A:Prefer an application-specific recovery bridge or controlled translation with tight fault-domain limits. The stated step is necessary because avoiding address changes must be balanced against exposing a large sensitive broadcast domain. Success means: A disaster recovery drill preserves approved research access without unrestricted layer-2 extension. Incorrect Answers B:Data consistency architecture imposes network bandwidth and latency constraints under worst-case load. That is relevant to a different intervention. For the stated situation, the required action is: Prefer an application-specific recovery bridge or controlled translation with tight fault-domain limits. The governing reason is: Avoiding address changes must be balanced against exposing a large sensitive broadcast domain. C:AI inference scaling requires corresponding network endpoint lifecycle and reachability automation. That is relevant to a different intervention. For the stated situation, the required action is: Prefer an application-specific recovery bridge or controlled translation with tight fault-domain limits. The governing reason is: Avoiding address changes must be balanced against exposing a large sensitive broadcast domain. D:Address translation infrastructure becomes a service dependency needing its own resilience budget. That is relevant to a different intervention. For the stated situation, the required action is: Prefer an application-specific recovery bridge or controlled translation with tight fault-domain limits. The governing reason is: Avoiding address changes must be balanced against exposing a large sensitive broadcast domain.
Question 372A logistics provider uses path-specific routing policy but fails to document how a new address block enters every regional access list. The design team recommends: Create policy-as-code templates with approved subnet enrollment and regression checks. Which architectural principle best supports that recommendation? Inbound interdomain routing cannot be determined solely by locally preferred attributes. Model input secrecy must persist through network observability and support systems. Address growth needs consistent routing and enforcement lifecycle to avoid fragmented reachability. External reachability depends on route authorization and transit import policy as well as BGP configuration. ExplanationCorrect Answer C:Address growth needs consistent routing and enforcement lifecycle to avoid fragmented reachability. That mechanism makes the proposed response appropriate. Create policy-as-code templates with approved subnet enrollment and regression checks. Evidence: A test prefix becomes reachable only through approved routes and remains denied to unrelated tenants. Incorrect Answers A:Inbound interdomain routing cannot be determined solely by locally preferred attributes. This does not establish the proposed intervention. The governing principle here is: Address growth needs consistent routing and enforcement lifecycle to avoid fragmented reachability. Apply it by: Create policy-as-code templates with approved subnet enrollment and regression checks. B:Model input secrecy must persist through network observability and support systems. This does not establish the proposed intervention. The governing principle here is: Address growth needs consistent routing and enforcement lifecycle to avoid fragmented reachability. Apply it by: Create policy-as-code templates with approved subnet enrollment and regression checks. D:External reachability depends on route authorization and transit import policy as well as BGP configuration. This does not establish the proposed intervention. The governing principle here is: Address growth needs consistent routing and enforcement lifecycle to avoid fragmented reachability. Apply it by: Create policy-as-code templates with approved subnet enrollment and regression checks.
Question 373A smart-city transport network attaches low-bandwidth sensors and high-bitrate surveillance to one undifferentiated queue. The design team recommends: Create distinct traffic classes tied to functional criticality and realistic burst characteristics. Which architectural principle best supports that recommendation? Address-family migration must preserve required application reachability until every dependency is ready. AI data locality influences both latency and recurring transfer economics. Congestion policy should reflect control urgency rather than uniform treatment of heterogeneous flows. Dual-stack availability must be engineered, not presumed from IPv4-only success. ExplanationCorrect Answer C:Congestion policy should reflect control urgency rather than uniform treatment of heterogeneous flows. The correction follows from this operating constraint. Create distinct traffic classes tied to functional criticality and realistic burst characteristics. Confirm with: During a camera burst, sensor alarms remain below the required delivery delay. Incorrect Answers A:Address-family migration must preserve required application reachability until every dependency is ready. This does not establish the proposed intervention. The governing principle here is: Congestion policy should reflect control urgency rather than uniform treatment of heterogeneous flows. Apply it by: Create distinct traffic classes tied to functional criticality and realistic burst characteristics. B:AI data locality influences both latency and recurring transfer economics. This does not establish the proposed intervention. The governing principle here is: Congestion policy should reflect control urgency rather than uniform treatment of heterogeneous flows. Apply it by: Create distinct traffic classes tied to functional criticality and realistic burst characteristics. D:Dual-stack availability must be engineered, not presumed from IPv4-only success. This does not establish the proposed intervention. The governing principle here is: Congestion policy should reflect control urgency rather than uniform treatment of heterogeneous flows. Apply it by: Create distinct traffic classes tied to functional criticality and realistic burst characteristics.
Question 374A bank uses IP address alone for access to an administrative application even though users move between branches and VPN pools. Which network architecture decision best meets these requirements? Classify device telemetry, redact secrets and apply provider access and retention governance. Adopt policy tied to workload identities and continuous approved discovery rather than stale addresses. Define payment-card trust zones with only necessary monitored exchanges to nonpayment systems. Enforce authenticated user identity and managed endpoint context independently of transient addresses. ExplanationCorrect Answer D:Enforce authenticated user identity and managed endpoint context independently of transient addresses. An IP address is not a durable representation of a person's authorization. Check the outcome directly: A traveling administrator is authorized by approved identity and an unauthenticated device at the old IP is denied. The unresolved risk would be: Address reassignment could wrongly grant privileged access. Incorrect Answers A:Observability systems can become sensitive information repositories and need confidentiality controls. That is relevant to a different intervention. For the stated situation, the required action is: Enforce authenticated user identity and managed endpoint context independently of transient addresses. The governing reason is: An IP address is not a durable representation of a person's authorization. B:Dynamic service populations require security controls that follow service identity instead of transient endpoints. That is relevant to a different intervention. For the stated situation, the required action is: Enforce authenticated user identity and managed endpoint context independently of transient addresses. The governing reason is: An IP address is not a durable representation of a person's authorization. C:Payment-processing security boundaries should follow regulated data flows instead of branch location. That is relevant to a different intervention. For the stated situation, the required action is: Enforce authenticated user identity and managed endpoint context independently of transient addresses. The governing reason is: An IP address is not a durable representation of a person's authorization.
Question 375An enterprise deploys anycast DNS at two sites but leaves the resolver database synchronized only once per day. Which network architecture decision best meets these requirements? Define authoritative configuration consistency and withdrawal behavior for degraded anycast nodes. Design diversion and reentry paths with consistent route origin and capacity for sanitized traffic. Create a protected model-distribution class and tune transfer concurrency around application service objectives. Use application-aware route advertisement or controlled endpoint redirection with verified health criteria. ExplanationCorrect Answer A:Define authoritative configuration consistency and withdrawal behavior for degraded anycast nodes. The change addresses the dependency rather than an adjacent symptom. Anycast reachability is safe only when serving sites have sufficiently consistent data and health checks. Verification: A stale resolver is withdrawn and clients receive consistent authorized records from healthy sites. Incorrect Answers B:Security mitigation services become part of the active forwarding topology during attacks. That is relevant to a different intervention. For the stated situation, the required action is: Define authoritative configuration consistency and withdrawal behavior for degraded anycast nodes. The governing reason is: Anycast reachability is safe only when serving sites have sufficiently consistent data and health checks. C:Model checkpoint distribution can generate bandwidth bursts far larger than inference requests. That is relevant to a different intervention. For the stated situation, the required action is: Define authoritative configuration consistency and withdrawal behavior for degraded anycast nodes. The governing reason is: Anycast reachability is safe only when serving sites have sufficiently consistent data and health checks. D:Network reachability does not prove that the destination application can serve real transactions. That is relevant to a different intervention. For the stated situation, the required action is: Define authoritative configuration consistency and withdrawal behavior for degraded anycast nodes. The governing reason is: Anycast reachability is safe only when serving sites have sufficiently consistent data and health checks.
Question 376A retail payment platform requires continuous authorization but its application gateways depend on one regional DNS resolver. The design team recommends: Design redundant service discovery and independent failover for critical name resolution. Which architectural principle best supports that recommendation? User responsiveness depends on complete service placement and transport delay. Cloud application continuity depends on identity and network services as well as vendor uptime. Application availability includes hidden name-service dependencies beyond gateway hardware. Application success requires transport MTU compatibility through all service overlays. ExplanationCorrect Answer C:Application availability includes hidden name-service dependencies beyond gateway hardware. Design redundant service discovery and independent failover for critical name resolution. That is the direct response to this rule. Verify using: An isolated resolver failure still returns valid gateway records from another authorized service. Incorrect Answers A:User responsiveness depends on complete service placement and transport delay. This does not establish the proposed intervention. The governing principle here is: Application availability includes hidden name-service dependencies beyond gateway hardware. Apply it by: Design redundant service discovery and independent failover for critical name resolution. B:Cloud application continuity depends on identity and network services as well as vendor uptime. This does not establish the proposed intervention. The governing principle here is: Application availability includes hidden name-service dependencies beyond gateway hardware. Apply it by: Design redundant service discovery and independent failover for critical name resolution. D:Application success requires transport MTU compatibility through all service overlays. This does not establish the proposed intervention. The governing principle here is: Application availability includes hidden name-service dependencies beyond gateway hardware. Apply it by: Design redundant service discovery and independent failover for critical name resolution.
Question 377A bank selects one underlay MTU for its native network while tunneling several protocols through a VPN service chain. What is the most direct design risk if this remains unresolved? Real customer requests could stall despite successful small ping tests. Unbounded backup replication could saturate store links and interrupt sales. Confidential design information could enter uncontrolled provider systems. Unbuffered measurements could vanish and invalidate refrigerated shipment compliance. ExplanationCorrect Answer A:Real customer requests could stall despite successful small ping tests. Calculate effective application payload sizes with worst-case nested encapsulation and test PMTUD. This limits the consequence because application success requires transport MTU compatibility through all service overlays. Incorrect Answers B:Backup traffic architecture must respect both recovery objectives and ongoing store availability. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Real customer requests could stall despite successful small ping tests. C:External AI services extend the data-governance boundary to prompts and retrieved context. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Real customer requests could stall despite successful small ping tests. D:IoT data collection needs explicit loss and timeliness semantics when connectivity is intermittent. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Real customer requests could stall despite successful small ping tests.
Question 378A logistics gateway routes application traffic through a service chain, but an intermediate policy device drops fragmented packets. What is the most direct design risk if this remains unresolved? Production payloads larger than the tested minimum could fail unpredictably. Ambiguous addresses could route sensitive claims data to the wrong system. A single controller service fault could disrupt global route changes. Transport upgrades could leave the true login bottleneck untouched. ExplanationCorrect Answer A:Production payloads larger than the tested minimum could fail unpredictably. The stated weakness directly creates that exposure. End-to-end data-plane design must preserve packet characteristics through every imposed encapsulation. Reduce it by: Account for actual MTU, encapsulation overhead and fragmentation behavior across the service chain. Incorrect Answers B:Overlapping namespaces require explicit disambiguation before policy or routing can be trusted. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Production payloads larger than the tested minimum could fail unpredictably. C:SD-WAN designs must distinguish overlay forwarding continuity from central management availability. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Production payloads larger than the tested minimum could fail unpredictably. D:User-experience design follows transaction dependencies, not only core transport metrics. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Production payloads larger than the tested minimum could fail unpredictably.
Question 379A manufacturer configures firewall logs locally on each gateway with no tamper-resistant aggregation across its plants. What is the most direct design risk if this remains unresolved? Outdated rules could block legitimate deployments or open access to reassigned addresses. Compromised or failed gateways could erase the incident trail. NAC connectivity loss could either halt legitimate operations or admit untrusted endpoints. A route leak could become an actual data-plane access breach. ExplanationCorrect Answer B:Compromised or failed gateways could erase the incident trail. This consequence follows from the failed control. Design secure centralized or resilient distributed audit collection with authenticated event transport. Verify improvement when: A controlled gateway outage leaves prior audit records intact in the approved evidence store. Incorrect Answers A:Dynamic service populations require security controls that follow service identity instead of transient endpoints. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Compromised or failed gateways could erase the incident trail. C:Identity-policy resilience requires explicit cached authorization and denial semantics during partitions. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Compromised or failed gateways could erase the incident trail. D:Control-plane route separation and packet-level authorization are complementary controls. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Compromised or failed gateways could erase the incident trail.
Question 380A hospital network project follows a waterfall approval model but clinical departments cannot articulate application latency needs until pilots run. After the proposed design change — Introduce an early representative clinical pilot and capture measurable latency requirements before final topology approval. — which outcome would provide the strongest validation? The team signs stable underlay interfaces and reviews each new store requirement against an agreed change budget. Clinical owners confirm traffic profiles and approve measured latency thresholds from pilot recordings. An audited inventory reconciles energy and equipment counts across branches and managed services. A load test shows new inference replicas receive balanced traffic without exhausting transport links. ExplanationCorrect Answer B:Clinical owners confirm traffic profiles and approve measured latency thresholds from pilot recordings. The result demonstrates the repair under real operating conditions. Introduce an early representative clinical pilot and capture measurable latency requirements before final topology approval. It limits the chance that late discovery of real-time needs could force expensive redesign after the hardware order. Incorrect Answers A:A hybrid governance cadence can preserve safety-critical interfaces while admitting bounded requirement changes. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Clinical owners confirm traffic profiles and approve measured latency thresholds from pilot recordings. C:Environmental reports require consistent scope and verifiable measurement assumptions. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Clinical owners confirm traffic profiles and approve measured latency thresholds from pilot recordings. D:Auto-scaling a workload does not improve throughput when the network bottleneck is fixed. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Clinical owners confirm traffic profiles and approve measured latency thresholds from pilot recordings.