Pass Juniper JN0-364 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
Juniper JN0-364 Practice Test 6
Question 50
A fictional Junos service-provider engineer encounters this scenario: Two equal-cost provider uplinks are available but a routing policy change was expected to send every flow evenly and an operator declares failure when the first few packets use the same member. Distinguishing evidence: Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: A
The bounded proposal is: Approve only the bounded change (Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.) after independently checking (A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: A broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold.
Another proposed approval would approve only the bounded change (Correct the static next-hop resolution against the verified active transit gateway and confirm the candidate configuration before committing the narrow change.) after independently checking (A controlled upstream failure and recovery shows the expected active route only while its resolved next hop is reachable and service probes succeed.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link.
A separate release decision would approve only the bounded change (Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order.) after independently checking (Packet samples and filter counters confirm only the approved customer flows use the alternate forwarding instance while management remains reachable.), without quietly widening the provider or customer network scope. It does not match the current change: Inspect the forwarding-table next hops and the Junos load-balancing policy, then measure multiple independent flows and validate the intended per-flow distribution.
An alternative approval would approve only the bounded change (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.) after independently checking (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Next-hop displays show multiple usable forwarding next hops, yet the test repeats one fixed five-tuple that consistently hashes to a single link and a broad representative multi-flow test uses both eligible paths while sessions preserve stable forwarding and loss stays within the agreed threshold, respectively.
Question 51
A fictional Junos service-provider engineer encounters this scenario: A metro access aggregation router stays stuck without an OSPF adjacency to its backbone uplink after a site template is copied from a nonbackbone area. Distinguishing evidence: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: C
Another proposed action is: Narrow the ingress match and forwarding-instance action to the documented customer flow, preserving explicit management and exception policy order. That does not directly address the observed condition: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. The more targeted correction is: Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.
Another proposed action is: Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions. It targets a different dependency; the evidence here is Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
Area mismatch prevents a core OSPF neighbor from forming. The decisive observation is Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. The proposed fix is: Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance. An observable result is: Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.
That alternative concerns: Check approved liveness requirements and align the interface hello and dead parameters on both adjacent devices before committing. The relevant evidence is Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. The corresponding fix is: Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.
Question 52
A fictional Junos service-provider engineer encounters this scenario: A metro access aggregation router stays stuck without an OSPF adjacency to its backbone uplink after a site template is copied from a nonbackbone area. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: C
Another piece of evidence concerns OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned. The current incident instead shows: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. This distinction supports the action: Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.
Another alternative would address BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails as decisive. The actual evidence in this case is Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. That fact identifies the relevant dependency, rather than a separate issue. Matching OSPF area membership is necessary for eligible routers to establish the intended adjacency.
Another proposed finding is: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. It is not the recorded discriminator, which is Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
Question 53
A fictional Junos service-provider engineer encounters this scenario: A metro access aggregation router stays stuck without an OSPF adjacency to its backbone uplink after a site template is copied from a nonbackbone area. Distinguishing evidence: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. Which Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: D
A different principle is: OSPF broadcast networks use DR and BDR election to reduce adjacency overhead. Evidence for this case: The interface is a broadcast multiaccess network with elected DR and BDR and the newcomer has low priority; neighbor output shows full adjacency to elected routers. The present evidence, however, is Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. The relevant rule is: Matching OSPF area membership is necessary for eligible routers to establish the intended adjacency.
This alternative invokes: Aggregate route advertisement must be evaluated with constituent route state and actual forwarding reachability. Evidence for this case: BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails. The governing distinction for the recorded case is Matching OSPF area membership is necessary for eligible routers to establish the intended adjacency.
The competing option invokes: OSPF neighbors require compatible interface-level parameters, including timing behavior. Evidence for this case: OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned. The present evidence is: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. The case-relevant principle is: Matching OSPF area membership is necessary for eligible routers to establish the intended adjacency.
Matching OSPF area membership is necessary for eligible routers to establish the intended adjacency. This distinction accounts for Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link; another unrelated mechanism would not address the same condition.
Question 54
A fictional Junos service-provider engineer encounters this scenario: A metro access aggregation router stays stuck without an OSPF adjacency to its backbone uplink after a site template is copied from a nonbackbone area. Intended bounded correction: Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: B
That result would assess another condition: The neighbor remains full through several monitored intervals, while routing reconverges predictably on a controlled link loss. The correct criterion is directly linked to the finding: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero. This verifies the required result rather than merely stating the action; the original issue was Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
A different option checks: The observed DR and BDR remain legitimate and all routers learn correct routes without forcing unnecessary full mesh adjacencies. The case-specific acceptance condition is instead Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.
Passing that test would not establish resolution of the stated issue. The relevant proof is: Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.
Question 55
A fictional Junos service-provider engineer encounters this scenario: A metro access aggregation router stays stuck without an OSPF adjacency to its backbone uplink after a site template is copied from a nonbackbone area. Distinguishing evidence: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. Which material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: A
The risk to retain is: Globally modifying OSPF area design to fix one mismatched interface can disrupt a wider provider routing domain. The original evidence is Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link; widening the change beyond it is not justified.
Another emphasis concerns: Changing every interface timer to match one link can create unnecessary churn and route instability elsewhere. The current change is Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance; the material limitation is Globally modifying OSPF area design to fix one mismatched interface can disrupt a wider provider routing domain.
This limitation concerns another setting: Debugging only the global table can prompt unintended configuration changes to an otherwise healthy customer VPN. The observed facts here make a different caution decisive: Globally modifying OSPF area design to fix one mismatched interface can disrupt a wider provider routing domain.
Another caution is: A syntactically valid summary can conceal an unreachable constituent when operators rely only on control-plane advertisement. The key risk in this case is: Globally modifying OSPF area design to fix one mismatched interface can disrupt a wider provider routing domain.
Question 56
A fictional Junos service-provider engineer encounters this scenario: A metro access aggregation router stays stuck without an OSPF adjacency to its backbone uplink after a site template is copied from a nonbackbone area. Distinguishing evidence: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. Which focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: C
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The firewall filter counter rises on a broad term that matches management subnet packets along with the intended customer source prefix. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Routing instance views show the source prefix active, while OSPF export policy counters show its attributes failing the allowed route term. The case observation to isolate is Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
The focused investigation should compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. It is tied to the observed evidence: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. It tests the conditions for this response: Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.
That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
Question 57
A fictional Junos service-provider engineer encounters this scenario: A metro access aggregation router stays stuck without an OSPF adjacency to its backbone uplink after a site template is copied from a nonbackbone area. Distinguishing evidence: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. Which controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: B
Another action-and-check pairing is: First verify the observed failure (Peer history contains hold timer expirations and packet captures show sporadic missing keepalives during a saturated control-plane event.); review and authorize the bounded correction (Investigate transport reliability, control-plane load and negotiated timer behavior before adjusting route filters or hold time.); then independently verify the intended outcome (The session remains established over representative monitored intervals and loss testing confirms appropriate recovery behavior.) before production rollout. The evidence here is Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. The required action and proof are Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance and Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.
The correction is Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance. The matching proof is Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero. Both address the finding that Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
Another possible combination is: First verify the observed failure (OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination.); review and authorize the bounded correction (Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.); then independently verify the intended outcome (Database entries and active route selection are explainable, and probes follow the intended next hop without falsely requiring every LSA to be an active route.) before production rollout. The current record instead supports Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance, verified by Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.
Another potential sequence is: First verify the observed failure (The script performs route and ping checks in the default table while the customer interface and its OSPF learned routes live in an isolated routing instance.); review and authorize the bounded correction (Repeat routing and operational tests explicitly in the correct customer instance and investigate any actual gap without changing global routing.); then independently verify the intended outcome (Route displays and sourced tests from the correct instance explain end-to-end reachability and isolate the false default-table alarm.) before production rollout. It has no direct link to the distinguishing evidence: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
Question 58
A fictional Junos service-provider engineer encounters this scenario: A metro access aggregation router stays stuck without an OSPF adjacency to its backbone uplink after a site template is copied from a nonbackbone area. Distinguishing evidence: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. Which set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: C
Another approval package concerns: Observed evidence (OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned.), limited correction (Check approved liveness requirements and align the interface hello and dead parameters on both adjacent devices before committing.), independently measurable result (The neighbor remains full through several monitored intervals, while routing reconverges predictably on a controlled link loss.). The present scope must instead be justified by Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
An alternative release decision is: Observed evidence (OSPF database output includes relevant link-state information, whereas the active route table prefers a more specific or otherwise preferred competing route for the destination.), limited correction (Compare link-state database reachability with route calculation, preference and active forwarding selection before modifying advertisement filters.), independently measurable result (Database entries and active route selection are explainable, and probes follow the intended next hop without falsely requiring every LSA to be an active route.). It does not match the current change: Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.
The approval decision should consider Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. The specific proposal is: Observed evidence (Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.), limited correction (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.), independently measurable result (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.). Its measurable outcome is: Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.
Another approval package concerns: Observed evidence (BGP announcements still include the aggregate prefix but the route table no longer contains the former constituent access path and a probe to that branch fails.), limited correction (Inspect active contributing routes and the aggregation policy, then choose a scoped summary advertisement and appropriate blackhole safeguards that reflect verified forwarding behavior.), independently measurable result (Neighbor route reception and end-to-end reachability tests demonstrate the intended covering advertisement without incorrectly promising restored access to the failed branch.). The present scope must instead be justified by Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
Question 59
A fictional Junos service-provider engineer encounters this scenario: A metro access aggregation router stays stuck without an OSPF adjacency to its backbone uplink after a site template is copied from a nonbackbone area. Distinguishing evidence: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: A
A contingency plan would pause changes, preserve the differentiating evidence (Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.), restore the last approved safe network state and reassess area mismatch prevents a core ospf neighbor from forming. This preserves control of the change linked to Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
Another recovery route would pause changes, preserve the differentiating evidence (Route inspection shows several tenant networks imported into a shared routing table through a broad RIB group rather than the single approved resolver route.), restore the last approved safe network state and reassess route leaking across routing instances is broader than intended. It does not preserve the condition of this case: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. The bounded fallback is: Pause changes, preserve the differentiating evidence (Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.), restore the last approved safe network state and reassess area mismatch prevents a core ospf neighbor from forming.
Another option proposes: Pause changes, preserve the differentiating evidence (OSPF neighbor and interface details reveal different hello and dead intervals on the directly connected segment even though addresses and area are aligned.), restore the last approved safe network state and reassess hello and dead interval mismatch causes ospf neighbor instability. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.), restore the last approved safe network state and reassess area mismatch prevents a core ospf neighbor from forming.
Another fallback concerns pausing changes, preserve the differentiating evidence (The interface is a broadcast multiaccess network with elected DR and BDR and the newcomer has low priority; neighbor output shows full adjacency to elected routers.), restore the last approved safe network state and reassess dr and bdr expectations are confused on shared ethernet. The current change concerns Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
Question 60
A fictional Junos service-provider engineer encounters this scenario: A metro access aggregation router stays stuck without an OSPF adjacency to its backbone uplink after a site template is copied from a nonbackbone area. Distinguishing evidence: Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: D
A separate release decision would approve only the bounded change (Inspect IS-IS LSP flooding, level scope and database synchronization before deciding on targeted refresh or isolation steps.) after independently checking (Peer databases converge on the expected LSP set and the authorized loopback routes become usable without forcing widespread protocol resets.), without quietly widening the provider or customer network scope. It does not match the current change: Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.
An alternative approval would approve only the bounded change (Review the OSPF export policy and prefix scope, then explicitly permit only the approved external destination while preserving other route exclusions.) after independently checking (Neighbor route views receive the approved external prefix and unrelated tenant networks remain unadvertised.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link and Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero, respectively.
Another proposed approval would approve only the bounded change (Check approved liveness requirements and align the interface hello and dead parameters on both adjacent devices before committing.) after independently checking (The neighbor remains full through several monitored intervals, while routing reconverges predictably on a controlled link loss.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link.
The approval decision should consider Interface-level OSPF inspection shows the local circuit attached to area 0.0.0.1 while the peer expects area 0.0.0.0 on the same numbered link. The specific proposal is: Approve only the bounded change (Validate the inter-router interface, area design and active configuration, then align the intended area membership under the appropriate OSPF instance.) after independently checking (Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.), without quietly widening the provider or customer network scope. Its measurable outcome is: Both routers progress to the expected full adjacency and the correct link-state routes appear without shifting unrelated interfaces into area zero.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 4 - 10 Questions (Last Reviewed 15-Nov-2026)
- Juniper JN0-364 Practice Test 5 - 10 Questions (Last Reviewed 14-Nov-2026)
- Juniper JN0-364 Practice Test 6 - 10 Questions (Last Reviewed 13-Nov-2026)
- Juniper JN0-364 Practice Test 7 - 10 Questions (Last Reviewed 12-Nov-2026)
- Juniper JN0-364 Practice Test 8 - 10 Questions (Last Reviewed 11-Nov-2026)