Fortinet FCP_FAZ_AN-7.6 Dumps
Fortinet FCP_FAZ_AN-7.6 Practice Test 19
Question 180
A hospital SOC detects a sudden DNS burst and needs a traceable log-to-incident hunting process before taking containment action. Which combined analytic action and validation test best solve this case?
Answer & Explanations
Correct answer: C
Choose this FortiAnalyzer analyst action: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Validate using: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance. This action-and-test pairing concerns another situation: A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. The current case needs this action: Use a bounded threat-hunting workflow that starts from observable hypothesis and pivots through logs, dashboards, and correlated incident evidence. Test with: Record a test hypothesis, pivot to original underlying logs, and document the evidence supporting or rejecting it. The fictional case is: A hospital SOC detects a sudden DNS burst and needs a traceable log-to-incident hunting process before taking containment action.
Choose this FortiAnalyzer analyst action: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Validate using: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary. This action-and-test pairing concerns another situation: A financial SOC uses FortiAI to summarize several linked events and must verify that the listed source hosts are actually present in its logs. The current case needs this action: Use a bounded threat-hunting workflow that starts from observable hypothesis and pivots through logs, dashboards, and correlated incident evidence. Test with: Record a test hypothesis, pivot to original underlying logs, and document the evidence supporting or rejecting it. The fictional case is: A hospital SOC detects a sudden DNS burst and needs a traceable log-to-incident hunting process before taking containment action.
Use a bounded threat-hunting workflow that starts from observable hypothesis and pivots through logs, dashboards, and correlated incident evidence. Check the result: Record a test hypothesis, pivot to original underlying logs, and document the evidence supporting or rejecting it. The technical reason is: A hypothesis-driven investigation uses corroborated time-bound source and destination observations rather than declaring compromise from one aggregate chart. The fictional case is: A hospital SOC detects a sudden DNS burst and needs a traceable log-to-incident hunting process before taking containment action.
Choose this FortiAnalyzer analyst action: Identify whether the record is in real-time Archive, compressed Archive, or the Analytics SQL database before selecting the investigative view. Validate using: Send a test record and compare its raw arrival, indexing state, and later Log View search availability across the expected delay. This action-and-test pairing concerns another situation: A university SOC sees a FortiGate security event at the collector but cannot find it immediately in a historical analytics query. The current case needs this action: Use a bounded threat-hunting workflow that starts from observable hypothesis and pivots through logs, dashboards, and correlated incident evidence. Test with: Record a test hypothesis, pivot to original underlying logs, and document the evidence supporting or rejecting it.
Question 181
A financial SOC uses FortiAI to summarize several linked events and must verify that the listed source hosts are actually present in its logs. Which FortiAnalyzer analyst action best addresses the stated operational requirement?
Answer & Explanations
Correct answer: C
Validate the parser against representative raw log samples and inspect assignment, priority, and extracted normalized output before deployment. That action is relevant to a different problem: A university SOC imports a custom web server parser but extracted client addresses appear blank in FortiAnalyzer analytics. Its technical basis is: Parser matching and field extraction govern whether a source is represented correctly in the SIEM database and available for normalized analytics. The present case instead requires: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields.
Define an event-to-incident operating process that distinguishes raw evidence, generated events, analyst assessment, and confirmed incidents. That action is relevant to a different problem: A hospital SOC receives thousands of routine web-filter denies and needs a defensible pathway to escalate an actual attack pattern. Its technical basis is: SOC investigation must weigh event context and corroborating evidence before treating a log occurrence as an actionable incident. The present case instead requires: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields.
Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. The technical reason is: Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. Confirm by: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
Measure per-ADOM log rates and volumes and inspect collection, queue, database, and forwarding capacity before altering retention. That action is relevant to a different problem: A retail chain experiences payment-hour firewall bursts and its FortiAnalyzer analytics lag increases although archive storage is not full. Its technical basis is: Ingestion throughput and downstream indexing capacity can be bottlenecks even when enough disk space remains for compressed storage. The present case instead requires: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields.
Question 182
A financial SOC uses FortiAI to summarize several linked events and must verify that the listed source hosts are actually present in its logs. The reviewed recommendation is: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Which technical principle explains why the proposed FortiAnalyzer action works?
Answer & Explanations
Correct answer: D
FortiAnalyzer may keep searchable Analytics data and compressed Archive records for different periods and storage-policy changes can purge data. That principle explains a different situation: A medical provider needs twelve months of raw firewall logs but only two months of fast interactive queries in its FortiAnalyzer. Here the relevant cause is: Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. Apply it by: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields.
FortiAnalyzer SOC analysis can combine eligible Fabric product observations within a shared analysis scope for more complete attack context. That principle explains a different situation: A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. Here the relevant cause is: Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. Apply it by: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields.
Ingestion throughput and downstream indexing capacity can be bottlenecks even when enough disk space remains for compressed storage. That principle explains a different situation: A retail chain experiences payment-hour firewall bursts and its FortiAnalyzer analytics lag increases although archive storage is not full. Here the relevant cause is: Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. Apply it by: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields.
Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. It explains why the intervention—treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields—addresses the stated problem. Test the mechanism by: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
Question 183
A financial SOC uses FortiAI to summarize several linked events and must verify that the listed source hosts are actually present in its logs. The reviewed recommendation is: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Which observation best demonstrates that this corrective step worked?
Answer & Explanations
Correct answer: D
Run the built-in parser validation on both matching and nonmatching sample records and check resulting mapped values in Log View. That test is for another requirement: A university SOC imports a custom web server parser but extracted client addresses appear blank in FortiAnalyzer analytics. It does not verify the stated outcome; the relevant check is: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot. That test is for another requirement: A regional insurer plans to enable additional FortiGuard playbooks on FortiAnalyzer but its subscription status has not been verified. It does not verify the stated outcome; the relevant check is: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance. That test is for another requirement: A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. It does not verify the stated outcome; the relevant check is: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary. This directly tests whether the chosen intervention works: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. The causal mechanism is: Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement.
Question 184
A financial SOC uses FortiAI to summarize several linked events and must verify that the listed source hosts are actually present in its logs. Which unsafe investigation or automation shortcut must be rejected?
Answer & Explanations
Correct answer: A
Automatically execute a destructive block whenever a model-generated summary labels a host malicious with no log verification. The risk is: Unsupported automated conclusions can disrupt legitimate devices or misstate incident evidence. The safer action is: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Confirm by: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody. That is an appropriate action for the separate case: A multinational retailer puts regional FortiAnalyzers under a central Fabric supervisor and needs accurate log custody boundaries. It is not the unsafe shortcut asked about here. Reject: Automatically execute a destructive block whenever a model-generated summary labels a host malicious with no log verification. Its risk is: Unsupported automated conclusions can disrupt legitimate devices or misstate incident evidence.
Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. That is an appropriate action for the separate case: A bank analyst assigns a high-severity incident and reports host isolation before checking any FortiAnalyzer automation job. It is not the unsafe shortcut asked about here. Reject: Automatically execute a destructive block whenever a model-generated summary labels a host malicious with no log verification. Its risk is: Unsupported automated conclusions can disrupt legitimate devices or misstate incident evidence.
Validate the parser against representative raw log samples and inspect assignment, priority, and extracted normalized output before deployment. That is an appropriate action for the separate case: A university SOC imports a custom web server parser but extracted client addresses appear blank in FortiAnalyzer analytics. It is not the unsafe shortcut asked about here. Reject: Automatically execute a destructive block whenever a model-generated summary labels a host malicious with no log verification. Its risk is: Unsupported automated conclusions can disrupt legitimate devices or misstate incident evidence.
Question 185
A financial SOC uses FortiAI to summarize several linked events and must verify that the listed source hosts are actually present in its logs. Which FortiAnalyzer action and acceptance test are correctly paired?
Answer & Explanations
Correct answer: C
Choose this FortiAnalyzer analyst action: Define an event-to-incident operating process that distinguishes raw evidence, generated events, analyst assessment, and confirmed incidents. Validate using: Inject a harmless denied-connection record and verify the process preserves evidence without automatically creating a critical incident. This action-and-test pairing concerns another situation: A hospital SOC receives thousands of routine web-filter denies and needs a defensible pathway to escalate an actual attack pattern. The current case needs this action: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Test with: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
Choose this FortiAnalyzer analyst action: Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. Validate using: Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot. This action-and-test pairing concerns another situation: A regional insurer plans to enable additional FortiGuard playbooks on FortiAnalyzer but its subscription status has not been verified. The current case needs this action: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Test with: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Check the result: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary. The technical reason is: Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement.
Choose this FortiAnalyzer analyst action: Use a bounded threat-hunting workflow that starts from observable hypothesis and pivots through logs, dashboards, and correlated incident evidence. Validate using: Record a test hypothesis, pivot to original underlying logs, and document the evidence supporting or rejecting it. This action-and-test pairing concerns another situation: A regional university sees one campus IP dominate bandwidth after hours and wants to verify whether it reflects approved backups or exfiltration. The current case needs this action: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Test with: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
Question 186
A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case. What is the most defensible FortiAnalyzer action in this situation?
Answer & Explanations
Correct answer: C
Use a bounded threat-hunting workflow that starts from observable hypothesis and pivots through logs, dashboards, and correlated incident evidence. That action is relevant to a different problem: A regional university sees one campus IP dominate bandwidth after hours and wants to verify whether it reflects approved backups or exfiltration. Its technical basis is: A hypothesis-driven investigation uses corroborated time-bound source and destination observations rather than declaring compromise from one aggregate chart. The present case instead requires: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields.
Measure per-ADOM log rates and volumes and inspect collection, queue, database, and forwarding capacity before altering retention. That action is relevant to a different problem: A retail chain experiences payment-hour firewall bursts and its FortiAnalyzer analytics lag increases although archive storage is not full. Its technical basis is: Ingestion throughput and downstream indexing capacity can be bottlenecks even when enough disk space remains for compressed storage. The present case instead requires: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. The fictional case is: A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case.
Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. The technical reason is: Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. Confirm by: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary. The fictional case is: A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case.
Distinguish detection and incident state from enforcement action by verifying explicit playbook or Fabric automation execution outcomes. That action is relevant to a different problem: A bank analyst assigns a high-severity incident and reports host isolation before checking any FortiAnalyzer automation job. Its technical basis is: An observed event or incident provides analytical evidence but does not itself guarantee a security device performed a containment action. The present case instead requires: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields.
Question 187
A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case. The reviewed recommendation is: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. What FortiAnalyzer mechanism supports the recommended analysis?
Answer & Explanations
Correct answer: B
Ingestion throughput and downstream indexing capacity can be bottlenecks even when enough disk space remains for compressed storage. That principle explains a different situation: A retail chain experiences payment-hour firewall bursts and its FortiAnalyzer analytics lag increases although archive storage is not full. Here the relevant cause is: Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. Apply it by: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. The fictional case is: A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case.
Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. It explains why the intervention—treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields—addresses the stated problem. Test the mechanism by: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary. The fictional case is: A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case.
Without a matching parser, supported raw device logs may still be present but cannot populate the intended normalized SIEM fields. That principle explains a different situation: A hospital uses Linux security event logs for threat detection and the normalized Fabric view remains empty although a device receives data. Here the relevant cause is: Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. Apply it by: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields.
SOC investigation must weigh event context and corroborating evidence before treating a log occurrence as an actionable incident. That principle explains a different situation: A hospital SOC receives thousands of routine web-filter denies and needs a defensible pathway to escalate an actual attack pattern. Here the relevant cause is: Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. Apply it by: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields.
Question 188
A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case. The reviewed recommendation is: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. What pilot verification directly establishes the intended result?
Answer & Explanations
Correct answer: C
Validate a known test host log and firewall event and compare normalized source identity and time fields in the correct Fabric log view. That test is for another requirement: A bank wants to correlate a Windows security login with FortiGate source-IP activity but the raw records have incompatible formats. It does not verify the stated outcome; the relevant check is: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
Check source log presence and parser match results separately, then verify the newly parsed test event becomes available for normalized searches. That test is for another requirement: A hospital uses Linux security event logs for threat detection and the normalized Fabric view remains empty although a device receives data. It does not verify the stated outcome; the relevant check is: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary. This directly tests whether the chosen intervention works: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. The causal mechanism is: Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. The fictional case is: A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case.
Inspect the entitled content list and demonstrate one eligible predefined handler or parser can be imported and used in a pilot. That test is for another requirement: A regional insurer plans to enable additional FortiGuard playbooks on FortiAnalyzer but its subscription status has not been verified. It does not verify the stated outcome; the relevant check is: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary. The fictional case is: A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case.
Question 189
A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case. Which tempting SOC change would undermine the stated requirement?
Answer & Explanations
Correct answer: C
Measure per-ADOM log rates and volumes and inspect collection, queue, database, and forwarding capacity before altering retention. That is an appropriate action for the separate case: A retail chain experiences payment-hour firewall bursts and its FortiAnalyzer analytics lag increases although archive storage is not full. It is not the unsafe shortcut asked about here. Reject: Automatically execute a destructive block whenever a model-generated summary labels a host malicious with no log verification. Its risk is: Unsupported automated conclusions can disrupt legitimate devices or misstate incident evidence.
Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. That is an appropriate action for the separate case: A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. It is not the unsafe shortcut asked about here. Reject: Automatically execute a destructive block whenever a model-generated summary labels a host malicious with no log verification. Its risk is: Unsupported automated conclusions can disrupt legitimate devices or misstate incident evidence.
Automatically execute a destructive block whenever a model-generated summary labels a host malicious with no log verification. The risk is: Unsupported automated conclusions can disrupt legitimate devices or misstate incident evidence. The safer action is: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Confirm by: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary. The fictional case is: A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case.
Verify the installed subscriptions and eligible FortiGuard SOC automation content packs before selecting enhanced parser, event, and playbook resources. That is an appropriate action for the separate case: A regional insurer plans to enable additional FortiGuard playbooks on FortiAnalyzer but its subscription status has not been verified. It is not the unsafe shortcut asked about here. Reject: Automatically execute a destructive block whenever a model-generated summary labels a host malicious with no log verification. Its risk is: Unsupported automated conclusions can disrupt legitimate devices or misstate incident evidence.
Question 190
A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case. Which combined analytic action and validation test best solve this case?
Answer & Explanations
Correct answer: A
Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Check the result: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary. The technical reason is: Generative analysis can help explain patterns but summaries require source-grounded verification and human response approval before enforcement. The fictional case is: A medical analyst receives an AI-generated intrusion narrative and needs to confirm each decisive timeline claim before opening a case.
Choose this FortiAnalyzer analyst action: Create a supported cross-Fabric investigation view that links normalized security evidence to events and incident context. Validate using: Correlate a synthetic email threat with authorized web and firewall test events and verify the incident preserves each source's provenance. This action-and-test pairing concerns another situation: A hospital receives a phishing alert from FortiMail followed by FortiGate outbound traffic and needs unified incident evidence. The current case needs this action: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Test with: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
Choose this FortiAnalyzer analyst action: Review ADOM log storage policies and set intentional Analytics and Archive retention periods with disk allocation and deletion impact assessed. Validate using: Simulate the proposed retention change and verify oldest required Archive files and intended Analytics date ranges remain under policy. This action-and-test pairing concerns another situation: A medical provider needs twelve months of raw firewall logs but only two months of fast interactive queries in its FortiAnalyzer. The current case needs this action: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Test with: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
Choose this FortiAnalyzer analyst action: Define a supported FortiAnalyzer Fabric supervisor-member topology and distinguish centralized incident summaries from local member log custody. Validate using: Compare an incident at the supervisor and member and check that required full log evidence remains accessible at the appropriate member. This action-and-test pairing concerns another situation: A multinational retailer puts regional FortiAnalyzers under a central Fabric supervisor and needs accurate log custody boundaries. The current case needs this action: Treat FortiAI assistance as analyst support and cross-check its key incident claims against source logs and relevant contextual fields. Test with: Select a harmless incident and verify its timestamps, hosts, and cited events against the source record before approving the summary.
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 04-Nov-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 18 - 10 Questions (Last Reviewed 03-Nov-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 19 - 10 Questions (Last Reviewed 02-Nov-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 20 - 10 Questions (Last Reviewed 01-Nov-2026)
- Fortinet FCP_FAZ_AN-7.6 Practice Test 21 - 10 Questions (Last Reviewed 31-Oct-2026)