Pass Fortinet FCP_FAZ_AN-7.6 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
Fortinet FCP_FAZ_AN-7.6 Practice Test 19
Question 180
A SOC response plan for benefit portal access alerts and privileged session logs at a pension administration office must include both a justified correction and measurable proof. Incident: Executives receive a zero-page incident PDF even though FortiAnalyzer's report history lists a completed run with populated charts. Evidence: Report output profile or external storage handoff contains an incomplete artifact while internal report preview has correct data. Which combined action-and-verification pair best fits this case?
Explanation
Correct Answer
The needed change is to compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. The acceptance test should confirm that the delivered file checksum and page count match the approved generated report and automated delivery succeeds to the intended recipient. Perform both using approved benefit portal access alerts and privileged session logs test cases. In this case, report output profile or external storage handoff contains an incomplete artifact while internal report preview has correct data. A successful data query and a correctly delivered report artifact are separate stages that require their own checks.
Incorrect Answers
The preferred remedy is to validate containment across related events and affected assets, update the incident timeline, and reopen or create follow-up cases as appropriate. A controlled check should show that a staged second-host test is identified and tracked instead of being hidden by an administrative closed status. Perform both using approved benefit portal access alerts and privileged session logs test cases. Administrative incident status is not technical evidence that the underlying threat has stopped across the environment. The diagnostic evidence here is report output profile or external storage handoff contains an incomplete artifact while internal report preview has correct data. The appropriate repair is to compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. A suitable test should demonstrate that the delivered file checksum and page count match the approved generated report and automated delivery succeeds to the intended recipient.
To resolve the observed issue, evaluate supported auto-cache/high-accuracy options and narrow expensive datasets or schedules while measuring resource impact. The outcome can be verified by confirming that the reworked report completes within its service budget and chart totals match validated sample queries. Perform both using approved benefit portal access alerts and privileged session logs test cases. Report caching can improve performance but has resource and accuracy tradeoffs; a slow report is not necessarily a malformed report. The diagnostic evidence here is report output profile or external storage handoff contains an incomplete artifact while internal report preview has correct data. The needed change is to compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. The acceptance test should confirm that the delivered file checksum and page count match the approved generated report and automated delivery succeeds to the intended recipient.
A focused response is to correlate traffic logs with relevant UTM/security subtype records on compatible session, device and timestamp fields. Validation should establish that a controlled prohibited request shows the intended security action and related traffic context without overcounting allowed sessions. Perform both using approved benefit portal access alerts and privileged session logs test cases. FortiGate forwarding/session status and layered security-profile detections describe different portions of the same event. The diagnostic evidence here is report output profile or external storage handoff contains an incomplete artifact while internal report preview has correct data. The preferred remedy is to compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. A controlled check should show that the delivered file checksum and page count match the approved generated report and automated delivery succeeds to the intended recipient.
Question 181
A SOC response plan for research network IPS detections and shared instrument access logs at a university research consortium must include both a justified correction and measurable proof. Incident: A Log View search reports no traffic between two hosts even though users reproduce an application access failure. Evidence: The search filter restricts action to accept and the actual firewall log entries use deny for the affected source and destination. Which combined action-and-verification pair best fits this case?
Explanation
Correct Answer
The preferred remedy is to inspect effective action values and build a comprehensive scoped source/destination/time filter before assuming no network evidence exists. A controlled check should show that a replayed denied flow appears with the policy/action and the count agrees with the FortiGate local observation. Perform both using approved research network IPS detections and shared instrument access logs test cases. In this case, the search filter restricts action to accept and the actual firewall log entries use deny for the affected source and destination. Negative security decisions often appear in denied logs, so allow-only filtering can conceal the most relevant evidence.
Incorrect Answers
To resolve the observed issue, update the widget's authorized device/log group selection and verify filter semantics against source logs. The outcome can be verified by confirming that the test device's events appear in both its Log View query and the aligned widget for the same time period. Perform both using approved research network IPS detections and shared instrument access logs test cases. Dashboard visualizations are derived from selected log sources and filters; an empty widget is not proof of no telemetry. The diagnostic evidence here is the search filter restricts action to accept and the actual firewall log entries use deny for the affected source and destination. The needed change is to inspect effective action values and build a comprehensive scoped source/destination/time filter before assuming no network evidence exists. The acceptance test should confirm that a replayed denied flow appears with the policy/action and the count agrees with the FortiGate local observation.
A focused response is to reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries. Validation should establish that a control event from the fifth store appears in the next generated report and unrelated tenants remain excluded. Perform both using approved research network IPS detections and shared instrument access logs test cases. Report source-device filters are independent from device registration and must track the intended scope. The diagnostic evidence here is the search filter restricts action to accept and the actual firewall log entries use deny for the affected source and destination. The preferred remedy is to inspect effective action values and build a comprehensive scoped source/destination/time filter before assuming no network evidence exists. A controlled check should show that a replayed denied flow appears with the policy/action and the count agrees with the FortiGate local observation.
The correction is to reproduce time, ADOM, device and filter context explicitly when pivoting between dashboard and Log View. A suitable test should demonstrate that pivoted raw events match the original widget's source set and timeframe, with any residual gaps documented. Perform both using approved research network IPS detections and shared instrument access logs test cases. A graphical summary and underlying records must share the same dimensions before differences can be interpreted. The diagnostic evidence here is the search filter restricts action to accept and the actual firewall log entries use deny for the affected source and destination. To resolve the observed issue, inspect effective action values and build a comprehensive scoped source/destination/time filter before assuming no network evidence exists. The outcome can be verified by confirming that a replayed denied flow appears with the policy/action and the count agrees with the FortiGate local observation.
Question 182
A security analyst at a public housing services agency is investigating an anomaly in resident portal events and privileged-access logs. The reported behavior is: An analyst uses a high-volume chart's cached top-N values as an exact security incident count for financial certification. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?
Explanation
Correct Answer
Underlying full Analytics query returns different long-tail records than the preaggregated hcache result. Aggregation caches trade resources and speed against result detail; not every cached chart is suitable as exact audit evidence. The needed change is to document and tune supported high-accuracy caching/filter strategy, and use a directly validated complete query for exact audit counts when required. Verify that sample counts reconcile to full data with the intended accuracy setting and the report discloses any approximation.
Incorrect Answers
Report history contains immutable older generated files with the previous layout while the definition has changed. Report definitions control future generation; they do not retroactively rewrite previously generated report artifacts. The diagnostic evidence here is underlying full Analytics query returns different long-tail records than the preaggregated hcache result. The preferred remedy is to document and tune supported high-accuracy caching/filter strategy, and use a directly validated complete query for exact audit counts when required.
Report definition history and owner settings show shared template edits rather than a cloned report under separate control. Report customization needs versioned ownership to avoid collateral changes to shared approved reporting assets. The diagnostic evidence here is underlying full Analytics query returns different long-tail records than the preaggregated hcache result. To resolve the observed issue, document and tune supported high-accuracy caching/filter strategy, and use a directly validated complete query for exact audit counts when required.
The reporting time range extends past retained Analytics rows while archived raw files are stored under a different lifecycle. Report generation needs accessible source analytics for the entire selected interval; archived evidence does not guarantee ready report datasets. The diagnostic evidence here is underlying full Analytics query returns different long-tail records than the preaggregated hcache result. A focused response is to document and tune supported high-accuracy caching/filter strategy, and use a directly validated complete query for exact audit counts when required.
Question 183
A SOC response plan for reservations security alerts and guest-network logs at a mid-size hotel group must include both a justified correction and measurable proof. Incident: Analysts can read last month's raw archive files but FortiView's historical widget shows an empty graph for the same period. Evidence: The specified historical range predates retained Analytics data although Archive log files still exist. Which combined action-and-verification pair best fits this case?
Explanation
Correct Answer
The appropriate repair is to verify analytics retention and supported data availability before asserting missing security activity or extending future storage policy. A controlled check should show that the incident report documents which time windows support FortiView and demonstrates a current-day control record in both Log View and the visualization. Perform both using approved reservations security alerts and guest-network logs test cases. In this case, the specified historical range predates retained Analytics data although Archive log files still exist. Dashboard historical analytics cannot be reconstructed merely by selecting a date if underlying analytics rows were aged out.
Incorrect Answers
A focused response is to distinguish internal service/application identifiers from user web sessions using documented datasets and scoped widget filters. Validation should establish that the revised view identifies user-facing risky domains separately and preserves an auditable total of excluded internal traffic. Perform both using approved reservations security alerts and guest-network logs test cases. FortiView aggregation requires appropriate population definition; most frequent domain is not automatically the highest-risk user destination. The diagnostic evidence here is the specified historical range predates retained Analytics data although Archive log files still exist. The preferred remedy is to verify analytics retention and supported data availability before asserting missing security activity or extending future storage policy. A controlled check should show that the incident report documents which time windows support FortiView and demonstrates a current-day control record in both Log View and the visualization.
The correction is to separate event occurrences from distinct device/user/indicator counts and report both with appropriate grouping. A suitable test should demonstrate that a replay of multiple alerts from one endpoint increments total events while unique affected-host count remains one. Perform both using approved reservations security alerts and guest-network logs test cases. The diagnostic evidence here is the specified historical range predates retained Analytics data although Archive log files still exist. To resolve the observed issue, verify analytics retention and supported data availability before asserting missing security activity or extending future storage policy. The outcome can be verified by confirming that the incident report documents which time windows support FortiView and demonstrates a current-day control record in both Log View and the visualization.
The practical next step is to reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries. The acceptance test should confirm that a control event from the fifth store appears in the next generated report and unrelated tenants remain excluded. Perform both using approved reservations security alerts and guest-network logs test cases. Report source-device filters are independent from device registration and must track the intended scope. The diagnostic evidence here is the specified historical range predates retained Analytics data although Archive log files still exist. A focused response is to verify analytics retention and supported data availability before asserting missing security activity or extending future storage policy. Validation should establish that the incident report documents which time windows support FortiView and demonstrates a current-day control record in both Log View and the visualization.
Question 184
A security analyst at a regional media broadcaster is investigating an anomaly in live contribution network events and newsdesk access logs. The reported behavior is: An outsourced SOC analyst assigned to customer A can open security views for customer B after a role migration. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?
Explanation
Correct Answer
The user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. SOC features inherit administrative and ADOM authorization boundaries; visibility settings alone are not isolation controls. To resolve the observed issue, restrict ADOM and role grants to authorized scopes and validate both GUI access and backend export permissions with negative tests. Verify that the user can analyze customer A events but cannot access customer B dashboards, incidents or report data through alternative views. The question describes: A security analyst at a regional media broadcaster is investigating an anomaly in live contribution network events and newsdesk access logs.
Incorrect Answers
FortiGate logging configuration points to a former log collector and packet captures show no traffic toward the approved FortiAnalyzer address. FortiAnalyzer cannot analyze evidence that a source FortiGate never forwards; destination and device authorization are foundational to central analytics. The diagnostic evidence here is the user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. A focused response is to restrict ADOM and role grants to authorized scopes and validate both GUI access and backend export permissions with negative tests.
Matching raw event identifiers and source/time fingerprints appear through two collection paths for the same FortiGate. Duplicate delivery paths can inflate analytics conclusions without any additional real network activity. The diagnostic evidence here is the user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. The correction is to restrict ADOM and role grants to authorized scopes and validate both GUI access and backend export permissions with negative tests.
Available raw log fields include device and VDOM values but the dashboard selector groups only by physical serial number. Correct source and virtual-domain attribution is necessary for trustworthy SOC conclusions in multi-tenant Fabric deployments. The diagnostic evidence here is the user's assigned administrator profile and allowed ADOM access include broader tenant permissions than the service contract specifies. The practical next step is to restrict ADOM and role grants to authorized scopes and validate both GUI access and backend export permissions with negative tests.
Question 185
The security team at a renewable-energy operator proposes this controlled action for remote plant intrusion signals and control-network access logs: Reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection. The original condition was: Security Fabric topology shows an obsolete edge device instead of the replacement FortiGate after a branch hardware swap. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?
Explanation
Correct Answer
The live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events. Security Fabric analytics depend on consistent device identities and membership, not simply identical display names. In this case, serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. The corresponding correction is to reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection.
Incorrect Answers
A controlled approved detection scenario produces the mapped event and evidence; untested techniques are clearly labeled as coverage gaps. A detection mapping describes capability or intent and cannot by itself prove that required telemetry and working rules exist. The diagnostic evidence here is serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. The required outcome is that the live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events.
Endpoint test alerts are labeled under the intended normalized event family with correct host and severity and are excluded from unrelated traffic totals. Log-source classification must match the producing application's schema before common SOC fields can be trusted. The diagnostic evidence here is serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. The required outcome is that the live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events.
Matching test policy events in two VDOMs appear with distinct source contexts and the analyst cannot confuse one tenant's evidence with the other. Correct source and virtual-domain attribution is necessary for trustworthy SOC conclusions in multi-tenant Fabric deployments. The diagnostic evidence here is serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. The required outcome is that the live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events.
Question 186
The security team at a city parks administration proposes this controlled action for public event portal traffic and staff system alerts: Verify retention period, accepted data recovery options and suitable future Analytics capacity rather than fabricating historical counts. The original condition was: An audit report for the previous quarter shows No Data although current daily reports work correctly. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?
Explanation
Correct Answer
A current control report succeeds, and the historical quarter is explicitly marked unavailable where source data cannot be recovered. Report generation needs accessible source analytics for the entire selected interval; archived evidence does not guarantee ready report datasets. In this case, the reporting time range extends past retained Analytics rows while archived raw files are stored under a different lifecycle. The corresponding correction is to verify retention period, accepted data recovery options and suitable future Analytics capacity rather than fabricating historical counts.
Incorrect Answers
Events at the start and end of the intended period appear exactly once and date-range labels match the actual query. Calendar-period and rolling-window selectors have different semantics even when both appear weekly. The diagnostic evidence here is the reporting time range extends past retained Analytics rows while archived raw files are stored under a different lifecycle. The required outcome is that a current control report succeeds, and the historical quarter is explicitly marked unavailable where source data cannot be recovered.
The new report includes the changed chart and older signed copies remain unchanged and distinguishable by generation time. Report definitions control future generation; they do not retroactively rewrite previously generated report artifacts. The diagnostic evidence here is the reporting time range extends past retained Analytics rows while archived raw files are stored under a different lifecycle. The required outcome is that a current control report succeeds, and the historical quarter is explicitly marked unavailable where source data cannot be recovered.
A low-volume but high-severity test source appears in the dedicated exception section even though it remains outside top-ten volume. Rankings are summaries, not exhaustive evidence; a low-frequency critical signal can sit below a volume cutoff. The diagnostic evidence here is the reporting time range extends past retained Analytics rows while archived raw files are stored under a different lifecycle. The required outcome is that a current control report succeeds, and the historical quarter is explicitly marked unavailable where source data cannot be recovered.
Question 187
The security team at a neighborhood grocery cooperative proposes this controlled action for point-of-sale cyber alerts and stock gateway logs: Provide explicit safe input values for manual runs or use a supported incident-context execution path with validated trigger variables. The original condition was: An analyst starts a playbook on demand and expects the incident's user and source-IP trigger variables to populate automatically. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?
Explanation
Correct Answer
An on-demand test refuses missing inputs, while the incident-started test uses the intended case fields. Trigger-derived variables exist only when the execution context supplies them; manual execution does not invent incident metadata. In this case, oN_DEMAND execution has no incident/event trigger payload and variables derived from trigger fields are empty. The corresponding correction is to provide explicit safe input values for manual runs or use a supported incident-context execution path with validated trigger variables.
Incorrect Answers
Sample incidents route to their responsible team with auditable ownership and none remain orphaned past the response time target. An incident's existence does not guarantee triage ownership; response workflow assignment is an additional operational decision. The diagnostic evidence here is oN_DEMAND execution has no incident/event trigger payload and variables derived from trigger fields are empty. The required outcome is that an on-demand test refuses missing inputs, while the incident-started test uses the intended case fields.
The second-host test is surfaced as actionable after closure, and the first case remains auditable. Administrative closure does not invalidate later observed evidence or prove all related assets are contained. The diagnostic evidence here is oN_DEMAND execution has no incident/event trigger payload and variables derived from trigger fields are empty. The required outcome is that an on-demand test refuses missing inputs, while the incident-started test uses the intended case fields.
Benign software updates do not trigger but an approved critical detection emits the handler event with the expected severity. Unstructured text matching may not have the same semantics as typed security-log severity attributes. The diagnostic evidence here is oN_DEMAND execution has no incident/event trigger payload and variables derived from trigger fields are empty. The required outcome is that an on-demand test refuses missing inputs, while the incident-started test uses the intended case fields.
Question 188
The security team at a university research consortium proposes this controlled action for research network IPS detections and shared instrument access logs: Order enrichment, evidence attachment and notification tasks with a safe failure fallback that labels incomplete evidence. The original condition was: A case automation sends an escalation note before its evidence-collection task completes, so the ticket references no supporting logs. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?
Explanation
Correct Answer
The escalation includes reproducible log details or explicitly flags evidence collection failure, never a silently empty attachment. Playbook task ordering matters to operational completeness, and downstream messages should reflect actual upstream completion. In this case, the notification branch runs in parallel and does not depend on successful evidence aggregation. The corresponding correction is to order enrichment, evidence attachment and notification tasks with a safe failure fallback that labels incomplete evidence.
Incorrect Answers
A legitimate test indicator is processed while reserved-management or malformed values are rejected without changing devices. Automation variables carry source data, not implicit trust; unsafe input handling can turn a detection into an unauthorized response. The diagnostic evidence here is the notification branch runs in parallel and does not depend on successful evidence aggregation. The required outcome is that the escalation includes reproducible log details or explicitly flags evidence collection failure, never a silently empty attachment.
A safe test invokes only the intended approved action, while unconfigured actions stay unavailable. FortiOS connector task actions depend on compatible device-side automation rules, not solely on a connected FortiAnalyzer playbook. The diagnostic evidence here is the notification branch runs in parallel and does not depend on successful evidence aggregation. The required outcome is that the escalation includes reproducible log details or explicitly flags evidence collection failure, never a silently empty attachment.
A second investigator can reproduce the source query and verify a sample log entry without relying on screenshots alone. Incident handling requires provenance and reproducible evidence, not just a narrative label attached to a case. The diagnostic evidence here is the notification branch runs in parallel and does not depend on successful evidence aggregation. The required outcome is that the escalation includes reproducible log details or explicitly flags evidence collection failure, never a silently empty attachment.
Question 189
During a FortiAnalyzer 7.6 design review covering supplier EDI gateway logs and plant incident telemetry at an agricultural equipment manufacturer, the incident is: An incident in one customer's ADOM triggers an automation that attempts to block an address on another customer's firewall. Key diagnostic evidence: The connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. Which underlying security-analytics or reporting principle explains the behavior?
Explanation
Correct Answer
Automated response must bind source incident scope to authorized target devices; a valid connector is not authorization to act across tenants. In this case, the connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. To resolve the observed issue, restrict connector targets, map source identity safely and add a negative cross-tenant scope check before remediation. Verify that a controlled tenant-A case changes only an approved tenant-A test policy and tenant-B devices remain untouched.
Incorrect Answers
Playbook triggers govern execution initiation independently of which tasks the playbook contains. The diagnostic evidence here is the connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. The controlling principle here is that automated response must bind source incident scope to authorized target devices; a valid connector is not authorization to act across tenants.
Threat indicators must preserve their type and canonical representation to support meaningful enrichment and correlation. The diagnostic evidence here is the connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. The controlling principle here is that automated response must bind source incident scope to authorized target devices; a valid connector is not authorization to act across tenants.
Event-handler data selectors define source scope separately from the underlying rule expression. The diagnostic evidence here is the connector target is hard-coded to a shared gateway instead of being derived from the authorized incident device context. The controlling principle here is that automated response must bind source incident scope to authorized target devices; a valid connector is not authorization to act across tenants.
Question 190
During a FortiAnalyzer 7.6 design review covering maintenance system incidents and service gateway logs at a metropolitan rail maintenance depot, the incident is: A custom security dashboard shows no source-IP activity even though raw logs from the affected sites are searchable. Key diagnostic evidence: Widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. Which underlying security-analytics or reporting principle explains the behavior?
Explanation
Correct Answer
Dashboard visualizations are derived from selected log sources and filters; an empty widget is not proof of no telemetry. In this case, widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. A controlled check should show that the test device's events appear in both its Log View query and the aligned widget for the same time period. The question describes: During a FortiAnalyzer 7.6 design review covering maintenance system incidents and service gateway logs at a metropolitan rail maintenance depot, the incident is: A custom security dashboard shows no source-IP activity even.
Incorrect Answers
Report caching can improve performance but has resource and accuracy tradeoffs; a slow report is not necessarily a malformed report. The diagnostic evidence here is widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. The targeted correction is to update the widget's authorized device/log group selection and verify filter semantics against source logs.
IP geolocation is an estimate of address location, not an identity or physical user-location attestation. The diagnostic evidence here is widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. The targeted correction is to update the widget's authorized device/log group selection and verify filter semantics against source logs.
FortiView aggregation requires appropriate population definition; most frequent domain is not automatically the highest-risk user destination. The diagnostic evidence here is widget or chart filters refer to a legacy log group whose members exclude the new registered FortiGate devices. The targeted correction is to update the widget's authorized device/log group selection and verify filter semantics against source logs.
Fortinet NSE 5 - FortiAnalyzer 7.6 Analyst (FCP_FAZ_AN-7.6) Practice Tests
- Fortinet FCP_FAZ_AN-7.6 Practice Test 17 - 10 Questions (Last Reviewed 02-Nov-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 18 - 10 Questions (Last Reviewed 01-Nov-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 19 - 10 Questions (Last Reviewed 31-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 20 - 10 Questions (Last Reviewed 30-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 21 - 10 Questions (Last Reviewed 29-Oct-2026)