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 36
Question 350
The security team at a cloud software support provider proposes this controlled action for customer ticket service events and engineer VPN logs: Treat FortiView geographic aggregation as network-IP intelligence and corroborate identity/location with authentication and proxy evidence. The original condition was: An analyst treats a geolocation ranking as proof that a named user connected physically from a specific country. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?
Explanation
Correct Answer
The report distinguishes network egress geolocation from verified user presence and does not assert a physical origin without corroboration. IP geolocation is an estimate of address location, not an identity or physical user-location attestation. In this case, the record contains a NAT/proxy egress address whose geolocation differs from the user's documented private endpoint. The corresponding correction is to treat FortiView geographic aggregation as network-IP intelligence and corroborate identity/location with authentication and proxy evidence.
Incorrect Answers
Pivoted raw events match the original widget's source set and timeframe, with any residual gaps documented. A graphical summary and underlying records must share the same dimensions before differences can be interpreted. The diagnostic evidence here is the record contains a NAT/proxy egress address whose geolocation differs from the user's documented private endpoint. The required outcome is that the report distinguishes network egress geolocation from verified user presence and does not assert a physical origin without corroboration.
Controlled failed and successful attempts for both identity formats return the expected ordered evidence without unrelated log flood. Evidence-driven log searching must account for producer-specific field names and structured filters rather than assuming one universal field. The diagnostic evidence here is the record contains a NAT/proxy egress address whose geolocation differs from the user's documented private endpoint. The required outcome is that the report distinguishes network egress geolocation from verified user presence and does not assert a physical origin without corroboration.
A replay of multiple alerts from one endpoint increments total events while unique affected-host count remains one. The diagnostic evidence here is the record contains a NAT/proxy egress address whose geolocation differs from the user's documented private endpoint. The required outcome is that the report distinguishes network egress geolocation from verified user presence and does not assert a physical origin without corroboration.
Question 351
During an investigation of public Wi-Fi events and staff application log streams at a county public library network, guest logs must remain separate from protected staff records. The reported failure is: A custom weekly report claims one account accessed all suspicious destinations, but the workstation address was reassigned between users. The analyst confirms: Dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?
Explanation
Correct Answer
Add documented identity and time context to the dataset or label IP-only aggregation without individual attribution. Scope the action to the affected public Wi-Fi events and staff application log streams environment. Report aggregation keys define the claim's granularity; an IP address does not guarantee a stable user identity. A focused response is to add documented identity and time context to the dataset or label IP-only aggregation without individual attribution. Verify that synthetic lease reassignment yields correct separate sessions or an explicit unattributed result, not one false user claim.
Incorrect Answers
Verify report filter caching and explicit source/subnet/ADOM constraints for each generated run before distribution. Scope the action to the affected public Wi-Fi events and staff application log streams environment. Report filter caching and query scope require tenant-aware validation, especially when a definition is reused. The diagnostic evidence here is dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. The preferred remedy is to add documented identity and time context to the dataset or label IP-only aggregation without individual attribution.
Bind the chart to a compatible supported dataset and validate log type, field mappings and sample aggregates. Scope the action to the affected public Wi-Fi events and staff application log streams environment. 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 dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. To resolve the observed issue, add documented identity and time context to the dataset or label IP-only aggregation without individual attribution.
Clone the report for the authorized variation and apply access/approval controls to preserve the standard template. Scope the action to the affected public Wi-Fi events and staff application log streams environment. Report customization needs versioned ownership to avoid collateral changes to shared approved reporting assets. The diagnostic evidence here is dataset groups on srcip without corresponding time-bounded identity/DHCP evidence and merges separate user sessions. The correction is to add documented identity and time context to the dataset or label IP-only aggregation without individual attribution.
Question 352
The security team at a public housing services agency proposes this controlled action for resident portal events and privileged-access logs: Configure and verify the required analytics processing/retention path alongside archival retention and test availability in the appropriate ADOM. The original condition was: A security analyst can confirm raw archived logs exist but an event handler and scheduled report show no matching events for that time window. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?
Explanation
Correct Answer
The targeted test event appears in both required searchable analytics views and retained raw evidence while archival integrity remains preserved. Archival retention and analytics database availability have different uses; event handlers and reports require appropriate processed analytics data. In this case, archive retention contains the records, yet the required Analytics log population was not maintained for the corresponding query interval. The corresponding correction is to configure and verify the required analytics processing/retention path alongside archival retention and test availability in the appropriate ADOM. The question describes: The security team at a public housing services agency proposes this controlled action for resident portal events and privileged-access logs.
Incorrect Answers
New controlled sessions create the expected number of log entries and the original source identity remains traceable across collectors. Duplicate delivery paths can inflate analytics conclusions without any additional real network activity. The diagnostic evidence here is archive retention contains the records, yet the required Analytics log population was not maintained for the corresponding query interval. The required outcome is that the targeted test event appears in both required searchable analytics views and retained raw evidence while archival integrity remains preserved.
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 archive retention contains the records, yet the required Analytics log population was not maintained for the corresponding query interval. The required outcome is that the targeted test event appears in both required searchable analytics views and retained raw evidence while archival integrity remains preserved.
The approved gateway is visible under the designated ADOM and a controlled event is searchable; an unapproved test source remains unauthorized. Receiving a connection and trusting a log-producing device are separate operations; registration and domain placement determine analyst access. The diagnostic evidence here is archive retention contains the records, yet the required Analytics log population was not maintained for the corresponding query interval. The required outcome is that the targeted test event appears in both required searchable analytics views and retained raw evidence while archival integrity remains preserved.
Question 353
During an investigation of nonemergency dispatch audit events and perimeter alerts at a regional emergency response center, staff require precise escalation without false urgency. The reported failure is: A weekly operations report misses the current Monday's urgent incidents because its date range means the previous calendar week. The analyst confirms: Settings specify Previous Week rather than rolling Previous 7 Days and previewed boundary timestamps exclude current period. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?
Explanation
Correct Answer
Select the report period that matches the written compliance requirement, preserving consistent day-boundary behavior. Scope the action to the affected nonemergency dispatch audit events and perimeter alerts environment. Calendar-period and rolling-window selectors have different semantics even when both appear weekly. The practical next step is to select the report period that matches the written compliance requirement, preserving consistent day-boundary behavior. Verify that events at the start and end of the intended period appear exactly once and date-range labels match the actual query.
Incorrect Answers
Add documented identity and time context to the dataset or label IP-only aggregation without individual attribution. Scope the action to the affected nonemergency dispatch audit events and perimeter alerts environment. Report aggregation keys define the claim's granularity; an IP address does not guarantee a stable user identity. The diagnostic evidence here is settings specify Previous Week rather than rolling Previous 7 Days and previewed boundary timestamps exclude current period. A focused response is to select the report period that matches the written compliance requirement, preserving consistent day-boundary behavior.
Clone the report for the authorized variation and apply access/approval controls to preserve the standard template. Scope the action to the affected nonemergency dispatch audit events and perimeter alerts environment. Report customization needs versioned ownership to avoid collateral changes to shared approved reporting assets. The diagnostic evidence here is settings specify Previous Week rather than rolling Previous 7 Days and previewed boundary timestamps exclude current period. The correction is to select the report period that matches the written compliance requirement, preserving consistent day-boundary behavior.
Label top-N limitations and include an explicit rare/high-severity indicator query where completeness is required. Scope the action to the affected nonemergency dispatch audit events and perimeter alerts environment. Rankings are summaries, not exhaustive evidence; a low-frequency critical signal can sit below a volume cutoff. The diagnostic evidence here is settings specify Previous Week rather than rolling Previous 7 Days and previewed boundary timestamps exclude current period. The appropriate repair is to select the report period that matches the written compliance requirement, preserving consistent day-boundary behavior.
Question 354
A security analyst at a hydrology research nonprofit is investigating an anomaly in river sensor gateway logs and remote site alerts. The reported behavior is: A blocked outbound HTTPS attempt is counted as an allowed user session because the analyst examines only the traffic disposition. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?
Explanation
Correct Answer
Related antivirus or web-filter event records carry the actual security-profile verdict and matching session context. FortiGate forwarding/session status and layered security-profile detections describe different portions of the same event. The correction is to correlate traffic logs with relevant UTM/security subtype records on compatible session, device and timestamp fields. Verify that a controlled prohibited request shows the intended security action and related traffic context without overcounting allowed sessions.
Incorrect Answers
The event window excludes the earlier login and only includes later DNS or data-transfer entries. Incident causality requires a complete relevant time window rather than a convenient snapshot of later logs. The diagnostic evidence here is related antivirus or web-filter event records carry the actual security-profile verdict and matching session context. The practical next step is to correlate traffic logs with relevant UTM/security subtype records on compatible session, device and timestamp fields.
Report time zone and previous-day window definitions use a different offset from the incident site's local time. Report scheduling window boundaries and display-time conversion influence which events enter a report. The diagnostic evidence here is related antivirus or web-filter event records carry the actual security-profile verdict and matching session context. The appropriate repair is to correlate traffic logs with relevant UTM/security subtype records on compatible session, device and timestamp fields.
The view displays a 24-hour aggregate but the drill-down uses a shorter window or different device selector. A graphical summary and underlying records must share the same dimensions before differences can be interpreted. The diagnostic evidence here is related antivirus or web-filter event records carry the actual security-profile verdict and matching session context. The needed change is to correlate traffic logs with relevant UTM/security subtype records on compatible session, device and timestamp fields.
Question 355
A security analyst at a pension administration office is investigating an anomaly in benefit portal access alerts and privileged session logs. The reported behavior is: Executives receive a zero-page incident PDF even though FortiAnalyzer's report history lists a completed run with populated charts. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?
Explanation
Correct Answer
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. The needed change is to 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. The question describes: A security analyst at a pension administration office is investigating an anomaly in benefit portal access alerts and privileged session logs.
Incorrect Answers
Report history and resource statistics show dataset assembly dominates processing and auto-cache policy is not appropriate to the new workload. 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 practical next step is to compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access.
Dataset filters reference normalized srcip while the updated parser writes the relevant address into an unsupported custom field. Report datasets depend on consistent field schema between ingestion normalization and the query definition. 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.
Raw event logs contain the privileged account under a different field than the analyst's fixed Log View filter. Evidence-driven log searching must account for producer-specific field names and structured filters rather than assuming one universal field. 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.
Question 356
The security team at a pension administration office proposes this controlled action for benefit portal access alerts and privileged session logs: Compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access. The original condition was: Executives receive a zero-page incident PDF even though FortiAnalyzer's report history lists a completed run with populated charts. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?
Explanation
Correct Answer
The delivered file checksum and page count match the approved generated report and automated delivery succeeds to the intended recipient. A successful data query and a correctly delivered report artifact are separate stages that require their own checks. In this case, report output profile or external storage handoff contains an incomplete artifact while internal report preview has correct data. The corresponding correction is to compare internal generated report with delivered file, fix the output profile/transport/storage path and verify recipient access.
Incorrect Answers
A staged second-host test is identified and tracked instead of being hidden by an administrative closed status. 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 required outcome is that the delivered file checksum and page count match the approved generated report and automated delivery succeeds to the intended recipient.
A replayed denied flow appears with the policy/action and the count agrees with the FortiGate local observation. 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 required outcome is that the delivered file checksum and page count match the approved generated report and automated delivery succeeds to the intended recipient.
A controlled address reassignment is resolved into separate correctly attributed sessions, with uncertainty documented when evidence is incomplete. Source IP is a temporary network identifier; defensible historical attribution needs time-specific supporting 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 required outcome is that the delivered file checksum and page count match the approved generated report and automated delivery succeeds to the intended recipient.
Question 357
During an investigation of checkout firewall alerts and replenishment system logs at a high-street retail chain, store-security events need reliable cross-site correlation. The reported failure is: Endpoint antivirus events are incorrectly treated as firewall traffic, making malware severity and host fields unusable for searches. The analyst confirms: Assigned parser or device source type labels do not match the real endpoint log schema and normalized fields contain nonsensical values. Which bounded FortiAnalyzer 7.6 analysis or configuration response best addresses the evidence?
Explanation
Correct Answer
Select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples. Scope the action to the affected checkout firewall alerts and replenishment system logs environment. Log-source classification must match the producing application's schema before common SOC fields can be trusted. A focused response is to select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples. Verify that endpoint test alerts are labeled under the intended normalized event family with correct host and severity and are excluded from unrelated traffic totals.
Incorrect Answers
Inventory active handlers, log-source health and observed validation signals separately from conceptual ATTACK mapping. Scope the action to the affected checkout firewall alerts and replenishment system logs environment. A detection mapping describes capability or intent and cannot by itself prove that required telemetry and working rules exist. The diagnostic evidence here is assigned parser or device source type labels do not match the real endpoint log schema and normalized fields contain nonsensical values. The needed change is to select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples.
Reassign the authorized device into its proper administrative domain with preserved evidence handling and tenant-aware permissions. Scope the action to the affected checkout firewall alerts and replenishment system logs environment. FortiAnalyzer ADOM scoping controls device and log context; working collection does not guarantee correct tenancy or isolation. The diagnostic evidence here is assigned parser or device source type labels do not match the real endpoint log schema and normalized fields contain nonsensical values. The preferred remedy is to select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples.
Establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned. Scope the action to the affected checkout firewall alerts and replenishment system logs environment. Collection, central processing and report generation are distinct roles in distributed FortiAnalyzer architectures. The diagnostic evidence here is assigned parser or device source type labels do not match the real endpoint log schema and normalized fields contain nonsensical values. To resolve the observed issue, select the correct supported parser/source type for the incoming product and verify its field mapping against canonical raw samples.
Question 358
A security analyst at an online education platform is investigating an anomaly in assessment portal access records and web security alerts. The reported behavior is: Security Fabric topology shows an obsolete edge device instead of the replacement FortiGate after a branch hardware swap. Before implementing a fix, which finding would distinguish the suspected cause from other FortiAnalyzer problems?
Explanation
Correct Answer
Serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. Security Fabric analytics depend on consistent device identities and membership, not simply identical display names. The correction is to reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection. Verify that the live replacement is represented once in Fabric context with matching new log source identifiers and no phantom old edge events.
Incorrect Answers
FortiAnalyzer device management shows the gateway awaiting approval while network tests confirm log packets reach the appliance. Receiving a connection and trusting a log-producing device are separate operations; registration and domain placement determine analyst access. 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 preferred remedy is to reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection.
Archive retention contains the records, yet the required Analytics log population was not maintained for the corresponding query interval. Archival retention and analytics database availability have different uses; event handlers and reports require appropriate processed analytics data. 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. To resolve the observed issue, reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection.
Device/ADOM analytics retention and rolling policies have removed the older logs before the investigation's mandated retention period. 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 serial-number inventory, device-manager records and recent telemetry identify the replacement, but the obsolete Fabric relationship remains in the analytics scope. A focused response is to reconcile the Fabric group and authorized device identities, remove the retired member through supported procedures and validate fresh collection.
Question 359
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 case automation sends an escalation note before its evidence-collection task completes, so the ticket references no supporting logs. Evidence: The notification branch runs in parallel and does not depend on successful evidence aggregation. Which combined action-and-verification pair best fits this case?
Explanation
Correct Answer
The correction is to order enrichment, evidence attachment and notification tasks with a safe failure fallback that labels incomplete evidence. A suitable test should demonstrate that the escalation includes reproducible log details or explicitly flags evidence collection failure, never a silently empty attachment. Perform both using approved research network IPS detections and shared instrument access logs test cases. In this case, the notification branch runs in parallel and does not depend on successful evidence aggregation. Playbook task ordering matters to operational completeness, and downstream messages should reflect actual upstream completion.
Incorrect Answers
The practical next step is to provide explicit safe input values for manual runs or use a supported incident-context execution path with validated trigger variables. The acceptance test should confirm that an on-demand test refuses missing inputs, while the incident-started test uses the intended case fields. Perform both using approved research network IPS detections and shared instrument access logs test cases. Trigger-derived variables exist only when the execution context supplies them; manual execution does not invent incident metadata. The diagnostic evidence here is the notification branch runs in parallel and does not depend on successful evidence aggregation. A focused response is to order enrichment, evidence attachment and notification tasks with a safe failure fallback that labels incomplete evidence. Validation should establish that the escalation includes reproducible log details or explicitly flags evidence collection failure, never a silently empty attachment.
The appropriate repair is to narrow the individual rule filters or use appropriate correlation logic when multiple conditions must be met together. A controlled check should show that only approved suspicious test patterns create the expected event while routine authorized flows do not trigger alerts. Perform both using approved research network IPS detections and shared instrument access logs test cases. Basic event handler rule matching differs from correlation sequence logic; rule composition controls alert specificity. The diagnostic evidence here is the notification branch runs in parallel and does not depend on successful evidence aggregation. The correction is to order enrichment, evidence attachment and notification tasks with a safe failure fallback that labels incomplete evidence. A suitable test should demonstrate that the escalation includes reproducible log details or explicitly flags evidence collection failure, never a silently empty attachment.
The needed change is to define the intended FOLLOWED_BY sequence, thresholds and grouping window with the genuine source log fields. The outcome can be verified by confirming that test failures followed by success raise one correlated event and reversed benign order does not. Perform both using approved research network IPS detections and shared instrument access logs test cases. 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 notification branch runs in parallel and does not depend on successful evidence aggregation. The practical next step is to order enrichment, evidence attachment and notification tasks with a safe failure fallback that labels incomplete evidence. The acceptance test should confirm that the escalation includes reproducible log details or explicitly flags evidence collection failure, never a silently empty attachment.
Question 360
The security team at an industrial parts distributor proposes this controlled action for barcode scanner connectivity alerts and egress gateway events: Establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned. The original condition was: A regional FortiAnalyzer Collector receives logs but the design expects it alone to run analytics reports and SOC event correlation in the same manner as a full Analyzer. What post-change test most directly proves the intended outcome without disrupting unrelated monitoring?
Explanation
Correct Answer
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. In this case, deployment topology documents Collector role and no configured Analyzer-side processing for the forwarded datasets. The corresponding correction is to establish a supported Analyzer–Collector design with reachable forwarding and the Analyzer-side analytics and report responsibilities clearly assigned.
Incorrect Answers
Each customer's analysts see only their authorized devices and log searches after the migration, with documented provenance for earlier retained records. FortiAnalyzer ADOM scoping controls device and log context; working collection does not guarantee correct tenancy or isolation. The diagnostic evidence here is deployment topology documents Collector role and no configured Analyzer-side processing for the forwarded datasets. The required outcome is that sample traffic is collected regionally, forwarded to the Analyzer and becomes searchable for event handling and scheduled reporting within the accepted delay.
A controlled web-filter policy violation appears with its Fortinet-specific subtype and the prior ordinary traffic count remains consistent. The source's selected logging categories determine which evidence is available to downstream analysis and security reporting. The diagnostic evidence here is deployment topology documents Collector role and no configured Analyzer-side processing for the forwarded datasets. The required outcome is that sample traffic is collected regionally, forwarded to the Analyzer and becomes searchable for event handling and scheduled reporting within the accepted delay.
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. The diagnostic evidence here is deployment topology documents Collector role and no configured Analyzer-side processing for the forwarded datasets. The required outcome is that sample traffic is collected regionally, forwarded to the Analyzer and becomes searchable for event handling and scheduled reporting within the accepted delay.
Fortinet NSE 5 - FortiAnalyzer 7.6 Analyst (FCP_FAZ_AN-7.6) Practice Tests
- Fortinet FCP_FAZ_AN-7.6 Practice Test 34 - 10 Questions (Last Reviewed 16-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 35 - 10 Questions (Last Reviewed 15-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 36 - 10 Questions (Last Reviewed 14-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 37 - 10 Questions (Last Reviewed 13-Oct-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 38 - 10 Questions (Last Reviewed 12-Oct-2026)