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 23
Question 220
The security team at a medical-device field service team proposes this controlled action for field diagnostic VPN events and remote access logs: Configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. The original condition was: A security analyst builds an automated incident enrichment playbook but it never runs when new incidents are raised. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?
Explanation
Correct Answer
A controlled matching incident starts one audited job while an unrelated benign incident does not trigger it. Playbook triggers govern execution initiation independently of which tasks the playbook contains. In this case, the playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. The corresponding correction is to configure a supported incident trigger with safe filters and enable the playbook, retaining manual-run access only as needed. The question describes: The security team at a medical-device field service team proposes this controlled action for field diagnostic VPN events and remote access logs: Configure a supported incident trigger with safe filters and enable the.
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 playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. The required outcome is that a controlled matching incident starts one audited job while an unrelated benign incident does not trigger it.
Test failures followed by success raise one correlated event and reversed benign order does not. Stateful event correlation depends on temporal ordering and shared identifiers, not just the presence of the same log types. The diagnostic evidence here is the playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. The required outcome is that a controlled matching incident starts one audited job while an unrelated benign incident does not trigger it. The question describes: The security team at a medical-device field service team proposes this controlled action for field diagnostic VPN events and remote access logs: Configure a supported incident trigger with safe filters and enable the.
A controlled severity-specific alert reaches the intended on-call channel with an event ID and records successful delivery. Detecting an event and notifying a responder are separate control chains with distinct configuration and failure modes. The diagnostic evidence here is the playbook is configured for ON_DEMAND while the team assumes it has an INCIDENT_TRIGGER event source. The required outcome is that a controlled matching incident starts one audited job while an unrelated benign incident does not trigger it.
Question 221
A security analyst at an agricultural equipment manufacturer is investigating an anomaly in supplier EDI gateway logs and plant incident telemetry. The reported behavior is: An audit report for the previous quarter shows No Data although current daily reports work correctly. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?
Explanation
Correct Answer
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 practical next step is to verify retention period, accepted data recovery options and suitable future Analytics capacity rather than fabricating historical counts. Verify that a current control report succeeds, and the historical quarter is explicitly marked unavailable where source data cannot be recovered.
Incorrect Answers
Report type and output profile are configured as shared group output instead of authorized per-device segmentation and recipient routing. Report type and output profile jointly control distribution, which must respect privacy and ADOM boundaries. 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 correction is to verify retention period, accepted data recovery options and suitable future Analytics capacity rather than fabricating historical counts.
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 diagnostic evidence here is the reporting time range extends past retained Analytics rows while archived raw files are stored under a different lifecycle. The appropriate repair is to verify retention period, accepted data recovery options and suitable future Analytics capacity rather than fabricating historical counts.
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 the reporting time range extends past retained Analytics rows while archived raw files are stored under a different lifecycle. The needed change is to verify retention period, accepted data recovery options and suitable future Analytics capacity rather than fabricating historical counts.
Question 222
The security team at a public housing services agency proposes this controlled action for resident portal events and privileged-access logs: Document and tune supported high-accuracy caching/filter strategy, and use a directly validated complete query for exact audit counts when required. The original condition was: An analyst uses a high-volume chart's cached top-N values as an exact security incident count for financial certification. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?
Explanation
Correct Answer
Sample counts reconcile to full data with the intended accuracy setting and the report discloses any approximation. Aggregation caches trade resources and speed against result detail; not every cached chart is suitable as exact audit evidence. In this case, underlying full Analytics query returns different long-tail records than the preaggregated hcache result. The corresponding correction is to document and tune supported high-accuracy caching/filter strategy, and use a directly validated complete query for exact audit counts when required.
Incorrect Answers
The chart renders expected labeled groups and its totals match the dataset preview without relying on stale aliases. A report dataset's schema is a contract for dependent charts and macros. The diagnostic evidence here is underlying full Analytics query returns different long-tail records than the preaggregated hcache result. The required outcome is that sample counts reconcile to full data with the intended accuracy setting and the report discloses any approximation.
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 underlying full Analytics query returns different long-tail records than the preaggregated hcache result. The required outcome is that sample counts reconcile to full data with the intended accuracy setting and the report discloses any approximation.
A controlled IPS detection populates the dataset and downstream risk chart while ordinary traffic is not mislabeled attack data. SQL datasets can only filter and aggregate attributes that exist in their selected log schema. The diagnostic evidence here is underlying full Analytics query returns different long-tail records than the preaggregated hcache result. The required outcome is that sample counts reconcile to full data with the intended accuracy setting and the report discloses any approximation.
Question 223
A SOC response plan for greenhouse sensor firewall alerts and field WAN logs at a cooperative farm network must include both a justified correction and measurable proof. Incident: A custom report's chart displays an SQL error after the dataset was updated to rename its grouping column. Evidence: Chart expects src_host alias while the revised dataset returns source_name with no matching field. Which combined action-and-verification pair best fits this case?
Explanation
Correct Answer
To resolve the observed issue, align chart field mappings with the dataset's actual result columns and preview the query on representative logs. A suitable test should demonstrate that the chart renders expected labeled groups and its totals match the dataset preview without relying on stale aliases. Perform both using approved greenhouse sensor firewall alerts and field WAN logs test cases. In this case, chart expects src_host alias while the revised dataset returns source_name with no matching field. A report dataset's schema is a contract for dependent charts and macros.
Incorrect Answers
The preferred remedy is to verify retention period, accepted data recovery options and suitable future Analytics capacity rather than fabricating historical counts. Validation should establish that a current control report succeeds, and the historical quarter is explicitly marked unavailable where source data cannot be recovered. Perform both using approved greenhouse sensor firewall alerts and field WAN logs test cases. Report generation needs accessible source analytics for the entire selected interval; archived evidence does not guarantee ready report datasets. The diagnostic evidence here is chart expects src_host alias while the revised dataset returns source_name with no matching field. The appropriate repair is to align chart field mappings with the dataset's actual result columns and preview the query on representative logs. A controlled check should show that the chart renders expected labeled groups and its totals match the dataset preview without relying on stale aliases.
A focused response is to move resource-heavy report jobs to a safe window, optimize datasets and consider supported capacity tuning without disabling essential security logging. The acceptance test should confirm that peak ingestion remains within accepted latency and the multi-month report completes during the planned run window. Perform both using approved greenhouse sensor firewall alerts and field WAN logs test cases. Reporting workloads consume shared processing resources; analytics capacity planning must include peak query as well as log ingestion demand. The diagnostic evidence here is chart expects src_host alias while the revised dataset returns source_name with no matching field. The preferred remedy is to align chart field mappings with the dataset's actual result columns and preview the query on representative logs. Validation should establish that the chart renders expected labeled groups and its totals match the dataset preview without relying on stale aliases.
The correction is to align report macro dataset scope and chart dataset scope to the authorized tenant and time window. A controlled check should show that macros and charts reconcile under a controlled per-tenant sample without leaking another customer's aggregate values. Perform both using approved greenhouse sensor firewall alerts and field WAN logs test cases. Macros are dataset-backed computations and must receive the same scoping assumptions as other report elements. The diagnostic evidence here is chart expects src_host alias while the revised dataset returns source_name with no matching field. To resolve the observed issue, align chart field mappings with the dataset's actual result columns and preview the query on representative logs. A suitable test should demonstrate that the chart renders expected labeled groups and its totals match the dataset preview without relying on stale aliases.
Question 224
The security team at a regional courier franchise proposes this controlled action for parcel tracking gateway logs and scanner access alerts: Inventory active handlers, log-source health and observed validation signals separately from conceptual ATTACK mapping. The original condition was: An analyst marks all mapped techniques as fully monitored after viewing FortiAnalyzer's MITRE coverage screen, although necessary log types are absent. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?
Explanation
Correct Answer
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. In this case, the visual technique mapping lists available handlers but source coverage and analytics fields for several techniques are missing. The corresponding correction is to inventory active handlers, log-source health and observed validation signals separately from conceptual ATTACK mapping.
Incorrect Answers
A time-window retention test preserves required historical events and disk usage stays within policy under projected daily volume. Analyzable history is constrained by log aging policies and storage allocation, not just whether the current logging connection is healthy. The diagnostic evidence here is the visual technique mapping lists available handlers but source coverage and analytics fields for several techniques are missing. The required outcome is that a controlled approved detection scenario produces the mapped event and evidence; untested techniques are clearly labeled as coverage gaps.
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. The diagnostic evidence here is the visual technique mapping lists available handlers but source coverage and analytics fields for several techniques are missing. The required outcome is that a controlled approved detection scenario produces the mapped event and evidence; untested techniques are clearly labeled as coverage gaps.
An approved known benign test condition verifies content update health and the SOC documents any coverage gaps rather than claiming nonexistent feeds. Enrichment and outbreak intelligence require their own data and service dependencies; raw log retention cannot substitute for an unavailable feed. The diagnostic evidence here is the visual technique mapping lists available handlers but source coverage and analytics fields for several techniques are missing. The required outcome is that a controlled approved detection scenario produces the mapped event and evidence; untested techniques are clearly labeled as coverage gaps.
Question 225
A security analyst at a county public library network is investigating an anomaly in public Wi-Fi events and staff application log streams. The reported behavior is: A custom handler meant for malware severity critical fires on informational antivirus updates containing the word critical in a description. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?
Explanation
Correct Answer
Text filter matches the word anywhere while structured severity and subtype conditions are absent or scoped incorrectly. Unstructured text matching may not have the same semantics as typed security-log severity attributes. A focused response is to prefer supported structured log field conditions and a narrowly scoped text pattern, then test false-positive and true-positive samples. Verify that benign software updates do not trigger but an approved critical detection emits the handler event with the expected severity.
Incorrect Answers
Notification profile still references a retired email webhook or destination without delivery confirmation. Detecting an event and notifying a responder are separate control chains with distinct configuration and failure modes. The diagnostic evidence here is text filter matches the word anywhere while structured severity and subtype conditions are absent or scoped incorrectly. The preferred remedy is to prefer supported structured log field conditions and a narrowly scoped text pattern, then test false-positive and true-positive samples.
The incident trigger is enabled with no filter, so all newly created incidents satisfy its trigger condition. A default unfiltered incident trigger may apply broadly; safety depends on intentional trigger scoping before activation. The diagnostic evidence here is text filter matches the word anywhere while structured severity and subtype conditions are absent or scoped incorrectly. To resolve the observed issue, prefer supported structured log field conditions and a narrowly scoped text pattern, then test false-positive and true-positive samples.
The handler's data selector lists headquarters devices but the new branch is absent despite existing source logs. Event-handler data selectors define source scope separately from the underlying rule expression. The diagnostic evidence here is text filter matches the word anywhere while structured severity and subtype conditions are absent or scoped incorrectly. The correction is to prefer supported structured log field conditions and a narrowly scoped text pattern, then test false-positive and true-positive samples.
Question 226
During a FortiAnalyzer 7.6 design review covering point-of-sale cyber alerts and stock gateway logs at a neighborhood grocery cooperative, the incident is: A quarterly report file name says the day after its actual time period and auditors suspect data tampering. Key diagnostic evidence: Generated report metadata uses the appliance time zone while the automated export naming convention assumes UTC without documenting conversion. Which underlying security-analytics or reporting principle explains the behavior?
Explanation
Correct Answer
Report identity includes its time-zone semantics, not just the stored PDF bytes. In this case, generated report metadata uses the appliance time zone while the automated export naming convention assumes UTC without documenting conversion. The practical next step is to standardize generation/export time zone labels and preserve both UTC reference and report-period provenance. Verify that The PDF title, period, archive metadata and machine job timestamps reconcile under a test near midnight.
Incorrect Answers
Report customization needs versioned ownership to avoid collateral changes to shared approved reporting assets. The diagnostic evidence here is generated report metadata uses the appliance time zone while the automated export naming convention assumes UTC without documenting conversion. The controlling principle here is that report identity includes its time-zone semantics, not just the stored PDF bytes.
Report charts display the results of selected datasets; a valid chart definition cannot compensate for a query against the wrong log family. The diagnostic evidence here is generated report metadata uses the appliance time zone while the automated export naming convention assumes UTC without documenting conversion. The controlling principle here is that report identity includes its time-zone semantics, not just the stored PDF bytes.
Report aggregation keys define the claim's granularity; an IP address does not guarantee a stable user identity. The diagnostic evidence here is generated report metadata uses the appliance time zone while the automated export naming convention assumes UTC without documenting conversion. The controlling principle here is that report identity includes its time-zone semantics, not just the stored PDF bytes.
Question 227
A SOC response plan for care referral alerts and clinic firewall telemetry at a pediatric clinic consortium must include both a justified correction and measurable proof. Incident: A scheduled management report displays only the original four stores after a fifth FortiGate was registered correctly. Evidence: Report Settings uses an explicit device list that was never updated for the fifth device. Which combined action-and-verification pair best fits this case?
Explanation
Correct Answer
The needed change is to reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries. A suitable test should demonstrate that a control event from the fifth store appears in the next generated report and unrelated tenants remain excluded. Perform both using approved care referral alerts and clinic firewall telemetry test cases. In this case, report Settings uses an explicit device list that was never updated for the fifth device. Report source-device filters are independent from device registration and must track the intended scope.
Incorrect Answers
The practical next step is to 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. Perform both using approved care referral alerts and clinic firewall telemetry test cases. Dashboard historical analytics cannot be reconstructed merely by selecting a date if underlying analytics rows were aged out. The diagnostic evidence here is report Settings uses an explicit device list that was never updated for the fifth device. A focused response 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.
The appropriate repair is to repair documented parser normalization or adapt the dataset to supported field names and test the SQL against sample rows. Validation should establish that the dataset previews the expected source counts and the report generation completes without dropping valid third-party records. Perform both using approved care referral alerts and clinic firewall telemetry test cases. Report datasets depend on consistent field schema between ingestion normalization and the query definition. The diagnostic evidence here is report Settings uses an explicit device list that was never updated for the fifth device. The correction is to reconcile report device selection or maintain an approved dynamic group with correct ADOM boundaries. A controlled check should show that a control event from the fifth store appears in the next generated report and unrelated tenants remain excluded.
The preferred remedy is to distinguish internal service/application identifiers from user web sessions using documented datasets and scoped widget filters. The acceptance test should confirm that the revised view identifies user-facing risky domains separately and preserves an auditable total of excluded internal traffic. Perform both using approved care referral alerts and clinic firewall telemetry test cases. FortiView aggregation requires appropriate population definition; most frequent domain is not automatically the highest-risk user destination. The diagnostic evidence here is report Settings uses an explicit device list that was never updated for the fifth device. The appropriate repair 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.
Question 228
During an investigation of archive service audit logs and suspicious DNS events at a museum collections partnership, heritage data needs verifiable source evidence. The reported failure is: Analysts can read last month's raw archive files but FortiView's historical widget shows an empty graph for the same period. The analyst confirms: The specified historical range predates retained Analytics data although Archive log files still exist. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?
Explanation
Correct Answer
Verify analytics retention and supported data availability before asserting missing security activity or extending future storage policy. Scope the action to the affected archive service audit logs and suspicious DNS events environment. Dashboard historical analytics cannot be reconstructed merely by selecting a date if underlying analytics rows were aged out. The appropriate repair is to verify analytics retention and supported data availability before asserting missing security activity or extending future storage policy. Verify that the incident report documents which time windows support FortiView and demonstrates a current-day control record in both Log View and the visualization.
Incorrect Answers
Expand the time range based on incident chronology and join evidence by endpoint/user/device with clock-corrected timestamps. Scope the action to the affected archive service audit logs and suspicious DNS events environment. Incident causality requires a complete relevant time window rather than a convenient snapshot of later logs. The diagnostic evidence here is the specified historical range predates retained Analytics data although Archive log files still exist. The correction is to verify analytics retention and supported data availability before asserting missing security activity or extending future storage policy.
Separate event occurrences from distinct device/user/indicator counts and report both with appropriate grouping. Scope the action to the affected archive service audit logs and suspicious DNS events environment. The diagnostic evidence here is the specified historical range predates retained Analytics data although Archive log files still exist. The practical next step is to verify analytics retention and supported data availability before asserting missing security activity or extending future storage policy.
Validate containment across related events and affected assets, update the incident timeline, and reopen or create follow-up cases as appropriate. Scope the action to the affected archive service audit logs and suspicious DNS events environment. Administrative incident status is not technical evidence that the underlying threat has stopped across the environment. The diagnostic evidence here is the specified historical range predates retained Analytics data although Archive log files still exist. The needed change is to verify analytics retention and supported data availability before asserting missing security activity or extending future storage policy.
Question 229
The security team at a municipal transit operator proposes this controlled action for ticket validation events and remote-depot firewall logs: Configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport. The original condition was: A branch FortiGate sends no telemetry to its newly deployed FortiAnalyzer although local security events continue to occur. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?
Explanation
Correct Answer
A test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector. FortiAnalyzer cannot analyze evidence that a source FortiGate never forwards; destination and device authorization are foundational to central analytics. In this case, FortiGate logging configuration points to a former log collector and packet captures show no traffic toward the approved FortiAnalyzer address. The corresponding correction is to configure the correct FortiAnalyzer destination, authorized connectivity and required device registration, then verify the supported logging transport. The question describes: The security team at a municipal transit operator proposes this controlled action for ticket validation events and remote-depot firewall logs.
Incorrect Answers
Sample traffic is collected regionally, forwarded to the Analyzer and becomes searchable for event handling and scheduled reporting within the accepted delay. Collection, central processing and report generation are distinct roles in distributed FortiAnalyzer architectures. The diagnostic evidence here is FortiGate logging configuration points to a former log collector and packet captures show no traffic toward the approved FortiAnalyzer address. The required outcome is that a test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector.
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 FortiGate logging configuration points to a former log collector and packet captures show no traffic toward the approved FortiAnalyzer address. The required outcome is that a test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector.
Replayed representative peak log volume shows expected source and severity counts without persistent ingest drops and with measured latency inside the service objective. Centralized log collection requires realistic rate and storage capacity planning; adding senders cannot exceed finite ingestion resources without loss. The diagnostic evidence here is FortiGate logging configuration points to a former log collector and packet captures show no traffic toward the approved FortiAnalyzer address. The required outcome is that a test allowed and denied session produces expected timestamped records in the correct FortiAnalyzer device context without sending data to the retired collector.
Question 230
During an investigation of remote instrument security logs and environmental data alerts at a scientific field station, investigators must retain context through link outages. The reported failure is: Executives receive a zero-page incident PDF even though FortiAnalyzer's report history lists a completed run with populated charts. The analyst confirms: Report output profile or external storage handoff contains an incomplete artifact while internal report preview has correct data. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?
Explanation
Correct Answer
Compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. Scope the action to the affected remote instrument security logs and environmental data alerts environment. A successful data query and a correctly delivered report artifact are separate stages that require their own checks. To resolve the observed issue, compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. Verify that the delivered file checksum and page count match the approved generated report and automated delivery succeeds to the intended recipient.
Incorrect Answers
Inspect effective action values and build a comprehensive scoped source/destination/time filter before assuming no network evidence exists. Scope the action to the affected remote instrument security logs and environmental data alerts environment. Negative security decisions often appear in denied logs, so allow-only filtering can conceal the most relevant evidence. 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.
Check application-control logging prerequisites and include unclassified categories in a scoped dashboard query. Scope the action to the affected remote instrument security logs and environmental data alerts environment. Application dashboards depend on available classification logs and grouping rules, not complete omniscience about every flow. 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.
Separate event occurrences from distinct device/user/indicator counts and report both with appropriate grouping. Scope the action to the affected remote instrument security logs and environmental data alerts 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 preferred remedy is to compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access.
Fortinet NSE 5 - FortiAnalyzer 7.6 Analyst (FCP_FAZ_AN-7.6) Practice Tests
- Fortinet FCP_FAZ_AN-7.6 Practice Test 21 - 10 Questions (Last Reviewed 29-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 22 - 10 Questions (Last Reviewed 28-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 23 - 10 Questions (Last Reviewed 27-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 24 - 10 Questions (Last Reviewed 26-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 25 - 10 Questions (Last Reviewed 25-Oct-2026)