Practice Exams:

Fortinet FCP_FGT_AD-7.6 Dumps

EXAM: FCP - FortiGate 7.6 Administrator
Verified By Experts
Premium Bundle
$49.99

FCP_FGT_AD-7.6 Premium ETE File


  • Premium File 128 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Fortinet FCP_FGT_AD-7.6 Practice Test 49

Question 480

A supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the supplier wants deployment: Implement: Configure a properly scoped blackhole route where failing over to the default internet route for a protected private prefix would leak or misdirect traffic. Verify: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.
  2. For the supplier wants deployment: Implement: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Verify: Inspect the active routing table, resolve the next hop and send a test packet to the intended prefix while observing the egress interface.
  3. For the supplier wants deployment: Implement: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Verify: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.
  4. For the supplier wants deployment: Implement: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Verify: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

Answer & Explanations

Correct answer: D

A.

This action and check address the alternate operation “For the supplier wants deployment: Implement: Configure a properly scoped blackhole route where failing over to the default internet…” instead of the stated acceptance requirement. The matching action is to check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Its confirming test is to inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

B.

This action and check address the alternate operation “For the supplier wants deployment: Implement: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost…” instead of the stated acceptance requirement. The matching action is to check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Its confirming test is to inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

C.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. This action and check address the distinct objective “Measure SD-WAN member health with appropriate probes” instead of the stated acceptance requirement. The matching action is to check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Its confirming test is to inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions.

D.

The situation is that a supplier wants to distribute new outbound sessions across duplicate routed WAN paths without random failover behavior. Implement: Check matching route metrics, next-hop availability and session behavior before using multiple equal-cost routes for the same prefix. Verify: Inspect active equal-cost routes and observe controlled session flows using both eligible next hops under approved conditions. This pairing is justified because ECMP selection depends on route eligibility and FortiOS forwarding decisions; simply adding two static routes does not guarantee balanced distribution when metrics differ.

Question 481

An emergency dispatch center needs FortiGate to detect a path that stays electrically up but intermittently loses voice packets. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the emergency dispatch center deployment: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths.
  2. For the emergency dispatch center deployment: Define specific SD-WAN service rules for critical applications ahead of less-specific catchall steering rules.
  3. For the emergency dispatch center deployment: Define performance SLA thresholds appropriate to the critical application's sensitivity rather than relying on throughput alone.
  4. For the emergency dispatch center deployment: Check SD-WAN zone membership, routing toward the zone and firewall policies that permit traffic across the selected interfaces.

Answer & Explanations

Correct answer: A

A.

Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. This resolves the issue because performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health. To verify, degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

B.

This option addresses the distinct objective “Order SD-WAN service rules to meet application intent”, not the immediate requirement. SD-WAN service rule evaluation and member selection depend on configured matching criteria and strategy; broad early rules can shadow specific application steering. For the stated case, performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

C.

This option addresses the distinct objective “Use latency, jitter and loss thresholds for application steering”, not the immediate requirement. A fast link can still violate real-time application needs through jitter or loss; SD-WAN can use measured SLA quality to select a better eligible member. For the stated case, performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

D.

This option addresses the distinct objective “Include SD-WAN zones in matching routes and firewall policy”, not the immediate requirement. An SD-WAN member decision does not bypass the firewall policy engine; routes and policies must reference the intended zone or interfaces for the flow to pass. For the stated case, performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

Question 482

An emergency dispatch center needs FortiGate to detect a path that stays electrically up but intermittently loses voice packets. The engineer proposes this change: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the emergency dispatch center deployment: SD-WAN service rule evaluation and member selection depend on configured matching criteria and strategy; broad early rules can shadow specific application steering.
  2. For the emergency dispatch center deployment: Performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.
  3. For the emergency dispatch center deployment: A fast link can still violate real-time application needs through jitter or loss; SD-WAN can use measured SLA quality to select a better eligible member.
  4. For the emergency dispatch center deployment: An SD-WAN member decision does not bypass the firewall policy engine; routes and policies must reference the intended zone or interfaces for the flow to pass.

Answer & Explanations

Correct answer: B

A.

That statement explains the distinct objective “Order SD-WAN service rules to meet application intent” rather than the cause in this case. The deciding mechanism here is that performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

B.

Performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health. It supports this action: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. To confirm, degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

C.

That statement explains the distinct objective “Use latency, jitter and loss thresholds for application steering” rather than the cause in this case. The deciding mechanism here is that performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

D.

That statement explains the distinct objective “Include SD-WAN zones in matching routes and firewall policy” rather than the cause in this case. The deciding mechanism here is that performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

Question 483

An emergency dispatch center needs FortiGate to detect a path that stays electrically up but intermittently loses voice packets. After implementing this change—Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths—which test best establishes that the intended outcome is actually working?

  1. For the emergency dispatch center deployment: Generate critical and general test flows, then inspect matching SD-WAN service IDs and chosen members under each path's measured health.
  2. For the emergency dispatch center deployment: Inject controlled jitter or loss on one WAN and verify the member's SLA violation and a new session's steering decision.
  3. For the emergency dispatch center deployment: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.
  4. For the emergency dispatch center deployment: Inspect the selected SD-WAN member and route, then verify the matching permit policy and a successful return packet.

Answer & Explanations

Correct answer: C

A.

This check would help evaluate the distinct objective “Order SD-WAN service rules to meet application intent”, but not the required result. For this case, degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

B.

This check would help evaluate the distinct objective “Use latency, jitter and loss thresholds for application steering”, but not the required result. For this case, degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

C.

Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics. This is the relevant test because performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

D.

This check would help evaluate the distinct objective “Include SD-WAN zones in matching routes and firewall policy”, but not the required result. For this case, degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

Question 484

An emergency dispatch center needs FortiGate to detect a path that stays electrically up but intermittently loses voice packets. Which proposed shortcut would most directly cause continued forwarding over an impaired path because application health was never measured, and therefore must be avoided for this requirement?

  1. For the emergency dispatch center deployment: Choose an ISP solely by advertised bandwidth while ignoring packet loss for interactive traffic.
  2. For the emergency dispatch center deployment: Add a link as an SD-WAN member but leave the traffic policy pointed only at an unrelated legacy WAN interface.
  3. For the emergency dispatch center deployment: Place a catchall service rule before a critical-application rule and assume the later rule wins.
  4. For the emergency dispatch center deployment: Mark a WAN healthy based only on physical link-up while its end-to-end path drops application packets.

Answer & Explanations

Correct answer: D

A.

That shortcut would relate to the distinct objective “Use latency, jitter and loss thresholds for application steering”, rather than the specific configuration or use described. The unsafe step in this case is to mark a WAN healthy based only on physical link-up while its end-to-end path drops application packets.

B.

That shortcut would relate to the distinct objective “Include SD-WAN zones in matching routes and firewall policy”, rather than the specific configuration or use described. The unsafe step in this case is to mark a WAN healthy based only on physical link-up while its end-to-end path drops application packets.

C.

That shortcut would relate to the distinct objective “Order SD-WAN service rules to meet application intent”, rather than the specific configuration or use described. The unsafe step in this case is to mark a WAN healthy based only on physical link-up while its end-to-end path drops application packets.

D.

Mark a WAN healthy based only on physical link-up while its end-to-end path drops application packets. The proposed shortcut bypasses the needed control: Performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health. The appropriate response is to configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths.

Question 485

An emergency dispatch center needs FortiGate to detect a path that stays electrically up but intermittently loses voice packets. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the emergency dispatch center deployment: Implement: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Verify: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.
  2. For the emergency dispatch center deployment: Implement: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Verify: Inject controlled jitter or loss on one WAN and verify the member's SLA violation and a new session's steering decision.
  3. For the emergency dispatch center deployment: Implement: Check SD-WAN zone membership, routing toward the zone and firewall policies that permit traffic across the selected interfaces. Verify: Inspect the selected SD-WAN member and route, then verify the matching permit policy and a successful return packet.
  4. For the emergency dispatch center deployment: Implement: Define specific SD-WAN service rules for critical applications ahead of less-specific catchall steering rules. Verify: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

Answer & Explanations

Correct answer: A

A.

Implement: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Verify: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics. This pairing is justified because performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

B.

This action and check address the alternate operation “For the emergency dispatch center deployment: Implement: Configure SD-WAN performance SLA probes that use relevant reachable targets over the…” instead of the stated acceptance requirement. The matching action is to configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Its confirming test is to degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

C.

This action and check address the distinct objective “Include SD-WAN zones in matching routes and firewall policy” instead of the stated acceptance requirement. The matching action is to configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Its confirming test is to degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

D.

This action and check address the alternate operation “For the emergency dispatch center deployment: Implement: Define specific SD-WAN service rules for critical applications ahead of less-specific catchall…” instead of the stated acceptance requirement. The matching action is to configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Its confirming test is to degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

Question 486

A university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. Which FortiOS 7.6 administrative change best meets this requirement without weakening unrelated controls?

  1. For the university office deployment: Define performance SLA thresholds appropriate to the critical application's sensitivity rather than relying on throughput alone.
  2. For the university office deployment: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths.
  3. For the university office deployment: Check SD-WAN zone membership, routing toward the zone and firewall policies that permit traffic across the selected interfaces.
  4. For the university office deployment: Define specific SD-WAN service rules for critical applications ahead of less-specific catchall steering rules.

Answer & Explanations

Correct answer: B

A.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. This option addresses the distinct objective “Use latency, jitter and loss thresholds for application steering”, not the immediate requirement. A fast link can still violate real-time application needs through jitter or loss; SD-WAN can use measured SLA quality to select a better eligible member. For the stated case, performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

B.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. This resolves the issue because performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health. To verify, degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

C.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. This option addresses the distinct objective “Include SD-WAN zones in matching routes and firewall policy”, not the immediate requirement. An SD-WAN member decision does not bypass the firewall policy engine; routes and policies must reference the intended zone or interfaces for the flow to pass. For the stated case, performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

D.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. This option addresses the distinct objective “Order SD-WAN service rules to meet application intent”, not the immediate requirement. SD-WAN service rule evaluation and member selection depend on configured matching criteria and strategy; broad early rules can shadow specific application steering. For the stated case, performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

Question 487

A university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. The engineer proposes this change: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths Which explanation most accurately establishes why that change meets the operational requirement?

  1. For the university office deployment: A fast link can still violate real-time application needs through jitter or loss; SD-WAN can use measured SLA quality to select a better eligible member.
  2. For the university office deployment: An SD-WAN member decision does not bypass the firewall policy engine; routes and policies must reference the intended zone or interfaces for the flow to pass.
  3. For the university office deployment: Performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.
  4. For the university office deployment: SD-WAN service rule evaluation and member selection depend on configured matching criteria and strategy; broad early rules can shadow specific application steering.

Answer & Explanations

Correct answer: C

A.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. That statement explains the distinct objective “Use latency, jitter and loss thresholds for application steering” rather than the cause in this case. The deciding mechanism here is that performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

B.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. That statement explains the distinct objective “Include SD-WAN zones in matching routes and firewall policy” rather than the cause in this case. The deciding mechanism here is that performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

C.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. Performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health. It supports this action: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. To confirm, degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

D.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. That statement explains the distinct objective “Order SD-WAN service rules to meet application intent” rather than the cause in this case. The deciding mechanism here is that performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

Question 488

A university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. After implementing this change—Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths—which test best establishes that the intended outcome is actually working?

  1. For the university office deployment: Inspect the selected SD-WAN member and route, then verify the matching permit policy and a successful return packet.
  2. For the university office deployment: Generate critical and general test flows, then inspect matching SD-WAN service IDs and chosen members under each path's measured health.
  3. For the university office deployment: Inject controlled jitter or loss on one WAN and verify the member's SLA violation and a new session's steering decision.
  4. For the university office deployment: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

Answer & Explanations

Correct answer: D

A.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. This check would help evaluate the distinct objective “Include SD-WAN zones in matching routes and firewall policy”, but not the required result. For this case, degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

B.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. This check would help evaluate the distinct objective “Order SD-WAN service rules to meet application intent”, but not the required result. For this case, degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

C.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. This check would help evaluate the distinct objective “Use latency, jitter and loss thresholds for application steering”, but not the required result. For this case, degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

D.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics. This is the relevant test because performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

Question 489

A university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. Which proposed shortcut would most directly cause continued forwarding over an impaired path because application health was never measured, and therefore must be avoided for this requirement?

  1. For the university office deployment: Mark a WAN healthy based only on physical link-up while its end-to-end path drops application packets.
  2. For the university office deployment: Add a link as an SD-WAN member but leave the traffic policy pointed only at an unrelated legacy WAN interface.
  3. For the university office deployment: Place a catchall service rule before a critical-application rule and assume the later rule wins.
  4. For the university office deployment: Choose an ISP solely by advertised bandwidth while ignoring packet loss for interactive traffic.

Answer & Explanations

Correct answer: A

A.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. Mark a WAN healthy based only on physical link-up while its end-to-end path drops application packets. The proposed shortcut bypasses the needed control: Performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health. The appropriate response is to configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths.

B.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. That shortcut would relate to the distinct objective “Include SD-WAN zones in matching routes and firewall policy”, rather than the specific configuration or use described. The unsafe step in this case is to mark a WAN healthy based only on physical link-up while its end-to-end path drops application packets.

C.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. That shortcut would relate to the distinct objective “Order SD-WAN service rules to meet application intent”, rather than the specific configuration or use described. The unsafe step in this case is to mark a WAN healthy based only on physical link-up while its end-to-end path drops application packets.

D.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. That shortcut would relate to the distinct objective “Use latency, jitter and loss thresholds for application steering”, rather than the specific configuration or use described. The unsafe step in this case is to mark a WAN healthy based only on physical link-up while its end-to-end path drops application packets.

Question 490

A university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. Which combined implementation and verification plan most reliably resolves this specific FortiOS 7.6 issue?

  1. For the university office deployment: Implement: Check SD-WAN zone membership, routing toward the zone and firewall policies that permit traffic across the selected interfaces. Verify: Inspect the selected SD-WAN member and route, then verify the matching permit policy and a successful return packet.
  2. For the university office deployment: Implement: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Verify: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.
  3. For the university office deployment: Implement: Define specific SD-WAN service rules for critical applications ahead of less-specific catchall steering rules. Verify: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.
  4. For the university office deployment: Implement: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Verify: Inject controlled jitter or loss on one WAN and verify the member's SLA violation and a new session's steering decision.

Answer & Explanations

Correct answer: B

A.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. This action and check address the distinct objective “Include SD-WAN zones in matching routes and firewall policy” instead of the stated acceptance requirement. The matching action is to configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Its confirming test is to degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

B.

The situation is that a university office has two ISPs and must ensure SD-WAN checks actually traverse the route used by its learning platform. Implement: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Verify: Degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics. This pairing is justified because performance SLA checks supply latency, jitter, loss and reachability data used by qualifying SD-WAN decisions; irrelevant probe destinations can misrepresent application path health.

C.

This action and check address the alternate operation “For the university office deployment: Implement: Define specific SD-WAN service rules for critical applications ahead of less-specific catchall steering…” instead of the stated acceptance requirement. The matching action is to configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Its confirming test is to degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

D.

This action and check address the alternate operation “For the university office deployment: Implement: Configure SD-WAN performance SLA probes that use relevant reachable targets over the intended…” instead of the stated acceptance requirement. The matching action is to configure SD-WAN performance SLA probes that use relevant reachable targets over the intended member paths. Its confirming test is to degrade one test link and confirm SLA status, measured loss or latency, and selected member changes in diagnostics.

FCP - FortiGate 7.6 Administrator (FCP_FGT_AD-7.6) Practice Tests