Fortinet NSE6_OTS_AR-7.6 (Fortinet NSE 6 - OT Security 7.6 Architect) Practice Test 83

Question 820

During an OT readiness check at the hydroelectric generation site, correlation incident reports incorrectly join independent hosts because the selected incident grouping key is too broad. What is the most targeted response?

  1. Select the relevant device or user key attributes when defining incident grouping
  2. Create a scoped FortiSIEM dashboard using normalized incidents and relevant time filters
  3. Use the display severity as the only incident grouping attribute
  4. Test the rule against real normalized events and adjust field mappings or predicates

Explanation

Correct Answer

A:

In this hydroelectric generation site scenario, incident identity keys determine whether new matching events increment an existing incident or raise a separate one; that directly resolves the requirement that correlation incident reports incorrectly join independent hosts because the selected incident grouping key is too broad.

Incorrect Answers

B:

At the hydroelectric generation site, this mechanism serves the separate situation where SOC analysts need a consolidated trend of control-network alerts across multiple sites, whereas the present finding is that correlation incident reports incorrectly join independent hosts because the selected incident grouping key is too broad; although role-focused dashboards summarize correlated events while retaining drill-down into source evidence, the required capability remains missing.

C:

At the hydroelectric generation site, this substitutes a measure addressing a different concern: a shared severity label does not distinguish independent source-device incident sequences; it leaves unresolved the finding that correlation incident reports incorrectly join independent hosts because the selected incident grouping key is too broad.

D:

At the hydroelectric generation site, this mechanism serves the separate situation where a SIEM correlation rule has been created but produces no incidents because its conditions never match the actual parsed fields, whereas the present finding is that correlation incident reports incorrectly join independent hosts because the selected incident grouping key is too broad; although correlation depends on the event attributes and window really produced by the data sources, the required capability remains missing.

Question 821

The controls engineer and SOC analyst for the industrial refrigeration installation must jointly address the following: (1) controls engineers cannot patch an essential controller until the next shutdown and the risk must be accepted or mitigated formally; and (2) operations wants a site-specific FortiSIEM dashboard rather than a corporate-wide incident summary. Which paired action most directly satisfies both findings without introducing an unrelated control change?

  1. Delete the vulnerability ticket once maintenance is postponed; then filter the dashboard on the OT site, incident dimensions and period of interest
  2. Document compensating controls, owner approval and a time-bound residual-risk plan; then filter the dashboard on the OT site, incident dimensions and period of interest
  3. Document compensating controls, owner approval and a time-bound residual-risk plan; then reuse an unfiltered global dashboard as proof of site-only risk
  4. Delete the vulnerability ticket once maintenance is postponed; then reuse an unfiltered global dashboard as proof of site-only risk

Explanation

Correct Answer

B:

The first control fits because deferred firmware fixes require explicit accountability and interim network controls; the second fits because site and time scoping align the visualization with local risk owners. Together they resolve the separate findings at the industrial refrigeration installation: controls engineers cannot patch an essential controller until the next shutdown and the risk must be accepted or mitigated formally, and operations wants a site-specific FortiSIEM dashboard rather than a corporate-wide incident summary. This addresses controls engineers cannot patch an essential controller until the next shutdown and the risk must be accepted or mitigated formally without bypassing the separate requirement that operations wants a site-specific FortiSIEM dashboard rather than a corporate-wide incident summary.

Incorrect Answers

A:

The second part is useful because site and time scoping align the visualization with local risk owners; however, the first part fails because closing the record without a treatment plan loses ownership of the remaining hazard. The first gap remains unresolved at the industrial refrigeration installation: controls engineers cannot patch an essential controller until the next shutdown and the risk must be accepted or mitigated formally; the second measure helps with operations wants a site-specific FortiSIEM dashboard rather than a corporate-wide incident summary but cannot repair it.

C:

The first action is suitable because deferred firmware fixes require explicit accountability and interim network controls; the second is misdirected because enterprise aggregates cannot isolate the plant's contribution without appropriate scoping. At the industrial refrigeration installation, the remaining second gap is that operations wants a site-specific FortiSIEM dashboard rather than a corporate-wide incident summary, even though controls engineers cannot patch an essential controller until the next shutdown and the risk must be accepted or mitigated formally is covered.

D:

The first substitution fails because closing the record without a treatment plan loses ownership of the remaining hazard; the second fails because enterprise aggregates cannot isolate the plant's contribution without appropriate scoping. For this industrial refrigeration installation, the first finding is that controls engineers cannot patch an essential controller until the next shutdown and the risk must be accepted or mitigated formally, while the other is that operations wants a site-specific FortiSIEM dashboard rather than a corporate-wide incident summary; neither is corrected by the chosen substitutions.

Question 822

A technician reviewing security evidence from the bulk-material handling facility finds that sensors at a process-control layer must be visible to the SOC without exposing those sensors directly to the enterprise LAN. The proposed shortcut is to permit unrestricted enterprise access directly to the controller subnet. Which alternative should the architect approve instead?

  1. Integrate Fortinet Security Fabric telemetry and inventory across the OT boundary
  2. Permit unrestricted enterprise access directly to the controller subnet
  3. Collect telemetry through approved segmented collectors and controlled boundary paths
  4. Place FortiGate policy boundaries at identified inter-zone conduits

Explanation

Correct Answer

C:

At the bulk-material handling facility, controlled information flows preserve OT segmentation while supplying analysis outside sensitive control segments; that directly resolves the requirement that sensors at a process-control layer must be visible to the SOC without exposing those sensors directly to the enterprise LAN.

Incorrect Answers

A:

At the bulk-material handling facility, this mechanism serves the separate situation where multiple Fortinet components provide partial OT visibility but incidents cannot be related across firewall, asset and analytics data, whereas the present finding is that sensors at a process-control layer must be visible to the SOC without exposing those sensors directly to the enterprise LAN; although correlation of FortiGate enforcement, device identity and analytics observations supports a coordinated OT security view, the required capability remains missing.

B:

At the bulk-material handling facility, the expected mechanism is absent because broad inbound reachability enlarges the exposure of assets intended to remain isolated; it leaves unresolved the finding that sensors at a process-control layer must be visible to the SOC without exposing those sensors directly to the enterprise LAN.

D:

At the bulk-material handling facility, this mechanism serves the separate situation where a Purdue model diagram does not show which cross-level flows the firewall actually governs, whereas the present finding is that sensors at a process-control layer must be visible to the SOC without exposing those sensors directly to the enterprise LAN; although a firewall at the conduit can enforce narrowly permitted communication between distinct Purdue-related zones, the required capability remains missing.

Question 823

At a pharmaceutical production floor, engineers must address both of these documented gaps: (1) security must recognize industrial application traffic even when it uses nonstandard transport ports; and (2) the team sees Modbus/TCP communications and needs to constrain dangerous controller write activity while retaining read operations. Which TWO independently necessary controls directly fulfill the two requirements? Choose TWO.

  1. Treat every Modbus packet as equally safe after allowing port 502
  2. Design Modbus-aware operation filtering where supported at the control conduit
  3. Configure a suitable FortiGate application control sensor on the observed policy
  4. Treat the source TCP port as definitive application identity
  5. Remove that unnecessary service from the segment's firewall allowlist

Explanation

Correct Answers

B:

For the stated gap at the pharmaceutical production floor, Modbus function-level distinctions matter because read and write requests can share one TCP service; that directly resolves the requirement that the team sees Modbus/TCP communications and needs to constrain dangerous controller write activity while retaining read operations; it is evaluated alongside the separate requirement that security must recognize industrial application traffic even when it uses nonstandard transport ports.

C:

In this pharmaceutical production floor scenario, application identification uses protocol decoders and signatures rather than trusting port numbers alone; that directly resolves the requirement that security must recognize industrial application traffic even when it uses nonstandard transport ports; it is evaluated alongside the separate requirement that the team sees Modbus/TCP communications and needs to constrain dangerous controller write activity while retaining read operations.

Incorrect Answers

A:

At the pharmaceutical production floor, that alternative is insufficient because a common transport service does not restrict the embedded function being requested; it leaves unresolved the finding that the team sees Modbus/TCP communications and needs to constrain dangerous controller write activity while retaining read operations; the parallel design also has to address security must recognize industrial application traffic even when it uses nonstandard transport ports.

D:

At the pharmaceutical production floor, this substitutes a measure addressing a different concern: source ports do not reliably identify the application protocol or its behavior; it leaves unresolved the finding that security must recognize industrial application traffic even when it uses nonstandard transport ports; the parallel design also has to address the team sees Modbus/TCP communications and needs to constrain dangerous controller write activity while retaining read operations.

E:

At the pharmaceutical production floor, this mechanism serves the separate situation where the OT architect needs to reduce the attack surface of a specific protocol service that is not required by the process, whereas the present finding is that security must recognize industrial application traffic even when it uses nonstandard transport ports; although eliminating unneeded permitted services shrinks reachable attack paths independently of signature coverage, the required capability remains missing.

Question 824

An OT architect reviewing the solar power operations center observes two independent gaps: (1) a new inventory fails to distinguish field sensing equipment from devices executing logic and supervisory visualization; and (2) the asset dashboard omits the OT vulnerability context needed for identifying devices with known exploited flaws. What two-part implementation is the most precise response to the stated requirements?

  1. Record sensors, actuators, PLCs and supervisory components by operational role; then disable all UTM processing while expecting the same enrichment
  2. Classify all equipment as interchangeable Ethernet endpoints; then confirm device identification and necessary security-profile processing for IoT/OT visibility
  3. Record sensors, actuators, PLCs and supervisory components by operational role; then confirm device identification and necessary security-profile processing for IoT/OT visibility
  4. Classify all equipment as interchangeable Ethernet endpoints; then disable all UTM processing while expecting the same enrichment

Explanation

Correct Answer

C:

The first control fits because recognizing field measurement, physical actuation, controller logic and supervisory functions is essential to impact analysis; the second fits because device identity processing and relevant inspected traffic supply asset attributes that enable enriched vulnerability views. Together they resolve the separate findings at the solar power operations center: a new inventory fails to distinguish field sensing equipment from devices executing logic and supervisory visualization, and the asset dashboard omits the OT vulnerability context needed for identifying devices with known exploited flaws. This addresses a new inventory fails to distinguish field sensing equipment from devices executing logic and supervisory visualization without bypassing the separate requirement that the asset dashboard omits the OT vulnerability context needed for identifying devices with known exploited flaws.

Incorrect Answers

A:

The first action is suitable because recognizing field measurement, physical actuation, controller logic and supervisory functions is essential to impact analysis; the second is misdirected because disabling inspection can remove observations needed to associate assets with vulnerability information. At the solar power operations center, the remaining second gap is that the asset dashboard omits the OT vulnerability context needed for identifying devices with known exploited flaws, even though a new inventory fails to distinguish field sensing equipment from devices executing logic and supervisory visualization is covered.

B:

The second part is useful because device identity processing and relevant inspected traffic supply asset attributes that enable enriched vulnerability views; however, the first part fails because a generic network label obscures who senses, controls or merely displays industrial processes. The first gap remains unresolved at the solar power operations center: a new inventory fails to distinguish field sensing equipment from devices executing logic and supervisory visualization; the second measure helps with the asset dashboard omits the OT vulnerability context needed for identifying devices with known exploited flaws but cannot repair it.

D:

The first substitution fails because a generic network label obscures who senses, controls or merely displays industrial processes; the second fails because disabling inspection can remove observations needed to associate assets with vulnerability information. For this solar power operations center, the first finding is that a new inventory fails to distinguish field sensing equipment from devices executing logic and supervisory visualization, while the other is that the asset dashboard omits the OT vulnerability context needed for identifying devices with known exploited flaws; neither is corrected by the chosen substitutions.

Question 825

The pharmaceutical production floor is preparing a controlled rollout. One outstanding requirement is that a FortiGate LAN interface sees OT hosts but device identity collection is disabled on that interface. The proposed shortcut is to enable only historical traffic-log report scheduling. Which alternative should the architect approve instead?

  1. Enable device identification on the relevant FortiGate LAN interface
  2. Review the KEV indicators associated with the discovered asset vulnerability
  3. Enable only historical traffic-log report scheduling
  4. Review the interface signature-exclusion settings for OT and IoT discovery

Explanation

Correct Answer

A:

The relevant technical distinction for the pharmaceutical production floor is that interface-level device-identification allows passive gathering of identity information from observed devices; that directly resolves the requirement that a FortiGate LAN interface sees OT hosts but device identity collection is disabled on that interface.

Incorrect Answers

B:

At the pharmaceutical production floor, this mechanism serves the separate situation where a vulnerability widget shows an OT weakness but the analyst needs to prioritize those known to be exploited in the wild, whereas the present finding is that a FortiGate LAN interface sees OT hosts but device identity collection is disabled on that interface; although known-exploited-vulnerability context differentiates observed exploitation relevance from an undifferentiated list of weaknesses, the required capability remains missing.

C:

The mismatch at the pharmaceutical production floor is specific to the observed control requirement: reports summarize recorded traffic but do not activate interface-based device identification; it leaves unresolved the finding that a FortiGate LAN interface sees OT hosts but device identity collection is disabled on that interface.

D:

At the pharmaceutical production floor, this mechanism serves the separate situation where OT and IoT signatures are inadvertently excluded from the detection configuration on a FortiGate interface, whereas the present finding is that a FortiGate LAN interface sees OT hosts but device identity collection is disabled on that interface; although excluded signature categories suppress matching for those device types and reduce available asset details, the required capability remains missing.

Question 826

An OT architect reviewing the rail signaling depot observes two independent gaps: (1) a plant wants to contain an exploit on a legacy PLC without installing an agent on the controller; and (2) the FortiGate knows an asset's vulnerability but its flow bypasses the firewall policy bearing the virtual patching profile. Which combination addresses the required mechanisms at their proper enforcement or observation points?

  1. Deploy network-based IPS or virtual patch protection at the applicable segment boundary; then put the profile on the real traffic path through a matching firewall policy
  2. Deploy network-based IPS or virtual patch protection at the applicable segment boundary; then expand the dashboard widget while leaving the routing bypass
  3. Install an endpoint detection agent on the unsupported controller firmware; then expand the dashboard widget while leaving the routing bypass
  4. Install an endpoint detection agent on the unsupported controller firmware; then put the profile on the real traffic path through a matching firewall policy

Explanation

Correct Answer

A:

The first control fits because inline network inspection can mitigate selected exploit traffic while leaving the unmodifiable endpoint software untouched; the second fits because a policy-attached virtual patch is not effective for traffic that does not cross that policy. Together they resolve the separate findings at the rail signaling depot: a plant wants to contain an exploit on a legacy PLC without installing an agent on the controller, and the FortiGate knows an asset's vulnerability but its flow bypasses the firewall policy bearing the virtual patching profile. This addresses a plant wants to contain an exploit on a legacy PLC without installing an agent on the controller without bypassing the separate requirement that the FortiGate knows an asset's vulnerability but its flow bypasses the firewall policy bearing the virtual patching profile.

Incorrect Answers

B:

The first action is suitable because inline network inspection can mitigate selected exploit traffic while leaving the unmodifiable endpoint software untouched; the second is misdirected because dashboard presentation cannot force bypassing sessions through a mitigation point. At the rail signaling depot, the remaining second gap is that the FortiGate knows an asset's vulnerability but its flow bypasses the firewall policy bearing the virtual patching profile, even though a plant wants to contain an exploit on a legacy PLC without installing an agent on the controller is covered.

C:

The first substitution fails because a legacy PLC may not run a general-purpose endpoint agent and this is not a practical network control; the second fails because dashboard presentation cannot force bypassing sessions through a mitigation point. For this rail signaling depot, the first finding is that a plant wants to contain an exploit on a legacy PLC without installing an agent on the controller, while the other is that the FortiGate knows an asset's vulnerability but its flow bypasses the firewall policy bearing the virtual patching profile; neither is corrected by the chosen substitutions.

D:

The second part is useful because a policy-attached virtual patch is not effective for traffic that does not cross that policy; however, the first part fails because a legacy PLC may not run a general-purpose endpoint agent and this is not a practical network control. The first gap remains unresolved at the rail signaling depot: a plant wants to contain an exploit on a legacy PLC without installing an agent on the controller; the second measure helps with the FortiGate knows an asset's vulnerability but its flow bypasses the firewall policy bearing the virtual patching profile but cannot repair it.

Question 827

A targeted security validation of the food-processing factory specifies the following: (1) the security engineer must decide which severity levels are actively blocked and which are only logged; and (2) an event-monitoring design confuses DNP3 event communication with ordinary operator web sessions. Which combination addresses the required mechanisms at their proper enforcement or observation points?

  1. Define and test the severity and action choices within a virtual patching profile; then identify DNP3 traffic using its industrial protocol context and configured communications pattern
  2. Increase traffic logging while leaving virtual-patching severity actions unchanged; then identify DNP3 traffic using its industrial protocol context and configured communications pattern
  3. Define and test the severity and action choices within a virtual patching profile; then apply a generic HTTP-only parsing assumption to DNP3 events
  4. Check valid update connectivity or the approved offline package update path; then identify DNP3 traffic using its industrial protocol context and configured communications pattern
  5. Increase traffic logging while leaving virtual-patching severity actions unchanged; then apply a generic HTTP-only parsing assumption to DNP3 events

Explanation

Correct Answer

A:

The first control fits because profile-level action and severity selections set which matched mitigations are enforced versus observed; the second fits because DNP3 supports telemetry and control exchanges that require different baselines from web browsing. Together they resolve the separate findings at the food-processing factory: the security engineer must decide which severity levels are actively blocked and which are only logged, and an event-monitoring design confuses DNP3 event communication with ordinary operator web sessions. This addresses the security engineer must decide which severity levels are actively blocked and which are only logged without bypassing the separate requirement that an event-monitoring design confuses DNP3 event communication with ordinary operator web sessions.

Incorrect Answers

B:

The second part is useful because DNP3 supports telemetry and control exchanges that require different baselines from web browsing; however, the first part fails because extra visibility does not configure which virtual-patching severities should block a session. The first gap remains unresolved at the food-processing factory: the security engineer must decide which severity levels are actively blocked and which are only logged; the second measure helps with an event-monitoring design confuses DNP3 event communication with ordinary operator web sessions but cannot repair it.

C:

The first action is suitable because profile-level action and severity selections set which matched mitigations are enforced versus observed; the second is misdirected because a web request parser does not describe DNP3 operational functions or expected field-device messages. At the food-processing factory, the remaining second gap is that an event-monitoring design confuses DNP3 event communication with ordinary operator web sessions, even though the security engineer must decide which severity levels are actively blocked and which are only logged is covered.

D:

The second action addresses an event-monitoring design confuses DNP3 event communication with ordinary operator web sessions because DNP3 supports telemetry and control exchanges that require different baselines from web browsing, but the separate first finding still concerns the security engineer must decide which severity levels are actively blocked and which are only logged. The proposed first mechanism belongs to a different requirement: the team expects current device vulnerability mappings after new FortiGuard definitions are issued; local signature and vulnerability intelligence must be refreshed through an authorized update workflow, but despite the valid second control for an event-monitoring design confuses DNP3 event communication with ordinary operator web sessions, it does not resolve the first finding at the food-processing factory: the security engineer must decide which severity levels are actively blocked and which are only logged.

E:

The first substitution fails because extra visibility does not configure which virtual-patching severities should block a session; the second fails because a web request parser does not describe DNP3 operational functions or expected field-device messages. For this food-processing factory, the first finding is that the security engineer must decide which severity levels are actively blocked and which are only logged, while the other is that an event-monitoring design confuses DNP3 event communication with ordinary operator web sessions; neither is corrected by the chosen substitutions.

Question 828

At the automotive assembly line, the next change must address the fact that the security review demands auditable separation between identity verification and permission to operate a controller. What is the most targeted response?

  1. Inspect the authenticated user's group and matching firewall policy scope
  2. Align firewall authorizations with up-to-date user group membership and session handling
  3. Treat a successful password check as permission for all industrial commands
  4. Record the authentication source and narrowly scoped authorization policy separately

Explanation

Correct Answer

D:

The relevant technical distinction for the automotive assembly line is that proving who a person is and determining what that person may access are distinct security decisions; that directly resolves the requirement that the security review demands auditable separation between identity verification and permission to operate a controller.

Incorrect Answers

A:

At the automotive assembly line, this mechanism serves the separate situation where a technician can log in to a portal but cannot reach a required PLC because the effective network policy lacks that destination, whereas the present finding is that the security review demands auditable separation between identity verification and permission to operate a controller; although successful authentication does not itself grant every destination and service; authorization is evaluated separately, the required capability remains missing.

B:

At the automotive assembly line, this mechanism serves the separate situation where a contractor account has been removed from the identity provider but an old local allow rule still provides broad access, whereas the present finding is that the security review demands auditable separation between identity verification and permission to operate a controller; although revocation must be reflected in both identity state and effective policy for the access path, the required capability remains missing.

C:

The mismatch at the automotive assembly line is specific to the observed control requirement: credential verification alone does not define allowed destinations or permitted actions; it leaves unresolved the finding that the security review demands auditable separation between identity verification and permission to operate a controller.

Question 829

At an OT architecture workshop covering the paper mill control network, the priority items are: (1) industrial trunk links have inconsistent VLAN tagging and an isolated OT segment leaks into an unintended access network; and (2) FortiNAC has identified a rogue device but the managed switch is not configured for the relevant isolation VLAN. Which paired action most directly satisfies both findings without introducing an unrelated control change?

  1. Add a routed inter-VLAN policy without correcting allowed trunk VLANs; then configure and map the restriction VLAN on the controlled switch before enforcing port changes
  2. Audit allowed tagged VLANs and native-VLAN behavior on both trunk ends; then configure and map the restriction VLAN on the controlled switch before enforcing port changes
  3. Audit allowed tagged VLANs and native-VLAN behavior on both trunk ends; then apply FortiNAC forced remediation and the remediation isolation state
  4. Audit allowed tagged VLANs and native-VLAN behavior on both trunk ends; then enable an unrelated email alert while leaving the switch VLAN missing
  5. Add a routed inter-VLAN policy without correcting allowed trunk VLANs; then enable an unrelated email alert while leaving the switch VLAN missing

Explanation

Correct Answer

B:

The first control fits because consistent trunk membership prevents a control VLAN from being carried where it is not approved; the second fits because access enforcement depends on the switching infrastructure actually supporting the intended restricted VLAN. Together they resolve the separate findings at the paper mill control network: industrial trunk links have inconsistent VLAN tagging and an isolated OT segment leaks into an unintended access network, and FortiNAC has identified a rogue device but the managed switch is not configured for the relevant isolation VLAN. This addresses industrial trunk links have inconsistent VLAN tagging and an isolated OT segment leaks into an unintended access network without bypassing the separate requirement that FortiNAC has identified a rogue device but the managed switch is not configured for the relevant isolation VLAN.

Incorrect Answers

A:

The second part is useful because access enforcement depends on the switching infrastructure actually supporting the intended restricted VLAN; however, the first part fails because layer-three policy cannot repair frames leaked by an unintended layer-two trunk membership. The first gap remains unresolved at the paper mill control network: industrial trunk links have inconsistent VLAN tagging and an isolated OT segment leaks into an unintended access network; the second measure helps with FortiNAC has identified a rogue device but the managed switch is not configured for the relevant isolation VLAN but cannot repair it.

C:

The first control responds to industrial trunk links have inconsistent VLAN tagging and an isolated OT segment leaks into an unintended access network because consistent trunk membership prevents a control VLAN from being carried where it is not approved, but the separate second finding still concerns FortiNAC has identified a rogue device but the managed switch is not configured for the relevant isolation VLAN. The second measure targets a different requirement: a registered workstation failed its compliance policy scan but must receive only remediation access; untrusted registered hosts can be restricted until their compliance posture is corrected, whereas the current second finding is that FortiNAC has identified a rogue device but the managed switch is not configured for the relevant isolation VLAN, with the different first requirement being industrial trunk links have inconsistent VLAN tagging and an isolated OT segment leaks into an unintended access network.

D:

The first action is suitable because consistent trunk membership prevents a control VLAN from being carried where it is not approved; the second is misdirected because notification does not supply a usable layer-two quarantine destination. At the paper mill control network, the remaining second gap is that FortiNAC has identified a rogue device but the managed switch is not configured for the relevant isolation VLAN, even though industrial trunk links have inconsistent VLAN tagging and an isolated OT segment leaks into an unintended access network is covered.

E:

The first substitution fails because layer-three policy cannot repair frames leaked by an unintended layer-two trunk membership; the second fails because notification does not supply a usable layer-two quarantine destination. For this paper mill control network, the first finding is that industrial trunk links have inconsistent VLAN tagging and an isolated OT segment leaks into an unintended access network, while the other is that FortiNAC has identified a rogue device but the managed switch is not configured for the relevant isolation VLAN; neither is corrected by the chosen substitutions.

Question 830

The asset owner of the large-scale irrigation installation wants to correct both of these deficiencies: (1) a maintenance laptop needs a narrow temporary path to one PLC rather than access to the entire control subnet; and (2) firewall policy should authorize a named maintenance group rather than every endpoint on the engineering subnet. What is the technically justified combination for the two separate observations?

  1. Keep cell-specific forwarding contexts logically isolated and define explicit interconnections; then apply identity-aware firewall rules using the authenticated user group
  2. Allow the whole technician VLAN to connect to all controllers permanently; then apply identity-aware firewall rules using the authenticated user group
  3. Authorize a source-, destination- and service-specific time-bounded firewall policy; then authorize every source address in the engineering LAN without authentication
  4. Authorize a source-, destination- and service-specific time-bounded firewall policy; then apply identity-aware firewall rules using the authenticated user group
  5. Allow the whole technician VLAN to connect to all controllers permanently; then authorize every source address in the engineering LAN without authentication

Explanation

Correct Answer

D:

The first control fits because narrowing identity, endpoints and protocols constrains maintenance reachability to the documented task; the second fits because group-scoped authorization links a verified human identity to the permitted network session. Together they resolve the separate findings at the large-scale irrigation installation: a maintenance laptop needs a narrow temporary path to one PLC rather than access to the entire control subnet, and firewall policy should authorize a named maintenance group rather than every endpoint on the engineering subnet. This addresses a maintenance laptop needs a narrow temporary path to one PLC rather than access to the entire control subnet without bypassing the separate requirement that firewall policy should authorize a named maintenance group rather than every endpoint on the engineering subnet.

Incorrect Answers

A:

The second action addresses firewall policy should authorize a named maintenance group rather than every endpoint on the engineering subnet because group-scoped authorization links a verified human identity to the permitted network session, but the separate first finding still concerns a maintenance laptop needs a narrow temporary path to one PLC rather than access to the entire control subnet. The proposed first mechanism belongs to a different requirement: multiple industrial cells use identical private addressing and must share one physical firewall without merging their networks; separate routing contexts prevent accidental overlap while making required shared services deliberate, but despite the valid second control for firewall policy should authorize a named maintenance group rather than every endpoint on the engineering subnet, it does not resolve the first finding at the large-scale irrigation installation: a maintenance laptop needs a narrow temporary path to one PLC rather than access to the entire control subnet.

B:

The second part is useful because group-scoped authorization links a verified human identity to the permitted network session; however, the first part fails because indefinite subnet-wide access exceeds the stated one-device maintenance requirement. The first gap remains unresolved at the large-scale irrigation installation: a maintenance laptop needs a narrow temporary path to one PLC rather than access to the entire control subnet; the second measure helps with firewall policy should authorize a named maintenance group rather than every endpoint on the engineering subnet but cannot repair it.

C:

The first action is suitable because narrowing identity, endpoints and protocols constrains maintenance reachability to the documented task; the second is misdirected because host subnet membership does not prove the user's membership in the maintenance role. At the large-scale irrigation installation, the remaining second gap is that firewall policy should authorize a named maintenance group rather than every endpoint on the engineering subnet, even though a maintenance laptop needs a narrow temporary path to one PLC rather than access to the entire control subnet is covered.

E:

The first substitution fails because indefinite subnet-wide access exceeds the stated one-device maintenance requirement; the second fails because host subnet membership does not prove the user's membership in the maintenance role. For this large-scale irrigation installation, the first finding is that a maintenance laptop needs a narrow temporary path to one PLC rather than access to the entire control subnet, while the other is that firewall policy should authorize a named maintenance group rather than every endpoint on the engineering subnet; neither is corrected by the chosen substitutions.

Fortinet NSE 6 - OT Security 7.6 Architect (NSE6_OTS_AR-7.6) Practice Tests