Question 170
In a deployment where a low-cost circuit has packet loss over the allowed SLA threshold, the team plans to: Exclude the failing member despite its attractive price. Which condition must be established for the chosen implementation to work as described?
- Verify the health check actually measures and enforces packet loss
- Ensure the specific rule's source and destination criteria actually match
- Confirm that static preference is intentional and both paths have reachability
- Configure the quality profile on a supported FortiOS version
Explanation
Correct Answer
A:Verify the health check actually measures and enforces packet loss. This is the enabling condition for exclude the failing member despite its attractive price. Without that prerequisite, the expected operational evidence may not appear: check which members pass the service's SLA before cost comparison. the documented recovery path is to repair the health-check threshold or carrier fault instead of selecting the failing cheap circuit.
Incorrect Answers
B:Ensure the specific rule's source and destination criteria actually match is relevant when the organization must correct the specificity and order of user-defined SD-WAN rules. Here the prerequisite instead concerns exclude the failing member despite its attractive price, so that different condition would not establish the necessary setup for the stated deployment.
C:Confirm that static preference is intentional and both paths have reachability is relevant when the organization must set manual member priorities if that fixed preference is the explicit goal. Here the prerequisite instead concerns exclude the failing member despite its attractive price, so that different condition would not establish the necessary setup for the stated deployment.
D:Configure the quality profile on a supported FortiOS version is relevant when the organization must use the supported custom-profile link-cost-factor in hybrid evaluation where available. Here the prerequisite instead concerns exclude the failing member despite its attractive price, so that different condition would not establish the necessary setup for the stated deployment.
Question 171
A team implemented this choice for a customer: Exclude the failing member despite its attractive price. The requirement was: a low-cost circuit has packet loss over the allowed SLA threshold. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Inspect each candidate's SLA value before examining cost
- Verify the payment flow selects the specific service rule before generic rules
- Inspect service-rule lookup for the flow and its winning rule ID
- Check which members pass the service's SLA before cost comparison
Explanation
Correct Answer
D:Check which members pass the service's SLA before cost comparison. It is the specific operational evidence for the requirement that a low-cost circuit has packet loss over the allowed SLA threshold. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
A:Inspect each candidate's SLA value before examining cost would be meaningful evidence when attempting to select the highest SLA-value member as the first hybrid comparison. It does not directly demonstrate whether check which members pass the service's SLA before cost comparison, which is the stated acceptance result for this Fortinet deployment.
B:Verify the payment flow selects the specific service rule before generic rules would be meaningful evidence when attempting to create a specific SD-WAN service rule matching the payment application's traffic. It does not directly demonstrate whether check which members pass the service's SLA before cost comparison, which is the stated acceptance result for this Fortinet deployment.
C:Inspect service-rule lookup for the flow and its winning rule ID would be meaningful evidence when attempting to correct the specificity and order of user-defined SD-WAN rules. It does not directly demonstrate whether check which members pass the service's SLA before cost comparison, which is the stated acceptance result for this Fortinet deployment.
Question 172
A Fortinet team is working on this situation: a low-cost circuit has packet loss over the allowed SLA threshold. It attempted: Exclude the failing member despite its attractive price. Expected evidence (Check which members pass the service's SLA before cost comparison) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Repair member priority entries rather than pretending manual mode performs best-latency comparisons
- Repair the health-check threshold or carrier fault instead of selecting the failing cheap circuit
- Repair the profile definition if ranking ignores the intended metric
- Add an explicit higher-priority rule only if the default implicit behavior fails the business requirement
Explanation
Correct Answer
B:Repair the health-check threshold or carrier fault instead of selecting the failing cheap circuit. The missing evidence (check which members pass the service's SLA before cost comparison) points to a problem with the implementation of exclude the failing member despite its attractive price. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A:Repair member priority entries rather than pretending manual mode performs best-latency comparisons addresses a different operational issue: a customer values a primary link even when its latency is a little worse than a backup. This situation calls for repair the health-check threshold or carrier fault instead of selecting the failing cheap circuit because the missing result relates to check which members pass the service's SLA before cost comparison.
C:Repair the profile definition if ranking ignores the intended metric addresses a different operational issue: an engineer wants custom quality ranking after hybrid SLA and cost ties. This situation calls for repair the health-check threshold or carrier fault instead of selecting the failing cheap circuit because the missing result relates to check which members pass the service's SLA before cost comparison.
D:Add an explicit higher-priority rule only if the default implicit behavior fails the business requirement addresses a different operational issue: an engineer needs predictable forwarding for traffic that matches no user-defined SD-WAN rule. This situation calls for repair the health-check threshold or carrier fault instead of selecting the failing cheap circuit because the missing result relates to check which members pass the service's SLA before cost comparison.
Question 173
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. A voice path must remain healthy under jitter and latency limits even if its monetary cost is higher. Which design or implementation decision best meets the stated requirement?
- Correct the specificity and order of user-defined SD-WAN rules
- Use the supported custom-profile link-cost-factor in hybrid evaluation where available
- Use SLA eligibility first and compare cost only between passing members
- Configure Maximize Bandwidth for eligible members
Explanation
Correct Answer
C:Use SLA eligibility first and compare cost only between passing members. This addresses the stated requirement: a voice path must remain healthy under jitter and latency limits even if its monetary cost is higher. The deployment must satisfy the accompanying requirement (Confirm latency and jitter targets for the voice class); the engineer can then validate the result by performing this check: inspect both pass/fail SLA indicators and the subsequent cost election.
Incorrect Answers
A:Correct the specificity and order of user-defined SD-WAN rules is a legitimate choice for another type of situation: a team is troubleshooting why a general cloud rule defeats a specific critical-service rule. The alternative design first requires the team to ensure the specific rule's source and destination criteria actually match, but it does not directly implement the specified requirement to use SLA eligibility first and compare cost only between passing members.
B:Use the supported custom-profile link-cost-factor in hybrid evaluation where available is a legitimate choice for another type of situation: an engineer wants custom quality ranking after hybrid SLA and cost ties. The alternative design first requires the team to configure the quality profile on a supported FortiOS version, but it does not directly implement the specified requirement to use SLA eligibility first and compare cost only between passing members.
D:Configure Maximize Bandwidth for eligible members is a legitimate choice for another type of situation: an internet service wants to exploit several quality-compliant links at once. The alternative design first requires the team to ensure both bandwidth paths are active and meet SLA targets, but it does not directly implement the specified requirement to use SLA eligibility first and compare cost only between passing members.
Question 174
In a deployment where a voice path must remain healthy under jitter and latency limits even if its monetary cost is higher, the team plans to: Use SLA eligibility first and compare cost only between passing members. Which condition must be established for the chosen implementation to work as described?
- Confirm no higher-priority rule matches the test session
- Define relevant health probes and a suitable link-cost factor
- Ensure both bandwidth paths are active and meet SLA targets
- Confirm latency and jitter targets for the voice class
Explanation
Correct Answer
D:Confirm latency and jitter targets for the voice class. This is the enabling condition for use SLA eligibility first and compare cost only between passing members. Without that prerequisite, the expected operational evidence may not appear: inspect both pass/fail SLA indicators and the subsequent cost election. the documented recovery path is to adjust inappropriate SLA thresholds before assuming the routing cost is wrong.
Incorrect Answers
A:Confirm no higher-priority rule matches the test session is relevant when the organization must examine the implicit SD-WAN rule behavior rather than inventing a hidden explicit match. Here the prerequisite instead concerns use SLA eligibility first and compare cost only between passing members, so that different condition would not establish the necessary setup for the stated deployment.
B:Define relevant health probes and a suitable link-cost factor is relevant when the organization must configure Best Quality strategy using the applicable latency measurement. Here the prerequisite instead concerns use SLA eligibility first and compare cost only between passing members, so that different condition would not establish the necessary setup for the stated deployment.
C:Ensure both bandwidth paths are active and meet SLA targets is relevant when the organization must configure Maximize Bandwidth for eligible members. Here the prerequisite instead concerns use SLA eligibility first and compare cost only between passing members, so that different condition would not establish the necessary setup for the stated deployment.
Question 175
A team implemented this choice for a customer: Use SLA eligibility first and compare cost only between passing members. The requirement was: a voice path must remain healthy under jitter and latency limits even if its monetary cost is higher. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Inspect application recognition and rule selection after identification completes
- Inspect both pass/fail SLA indicators and the subsequent cost election
- Review the passing SLA and selected member cost
- Check the selected Internet Service and rule match during a test connection
Explanation
Correct Answer
B:Inspect both pass/fail SLA indicators and the subsequent cost election. It is the specific operational evidence for the requirement that a voice path must remain healthy under jitter and latency limits even if its monetary cost is higher. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
A:Inspect application recognition and rule selection after identification completes would be meaningful evidence when attempting to use an application-based SD-WAN rule and account for its learning phase. It does not directly demonstrate whether inspect both pass/fail SLA indicators and the subsequent cost election, which is the stated acceptance result for this Fortinet deployment.
C:Review the passing SLA and selected member cost would be meaningful evidence when attempting to use Lowest Cost (SLA) with member cost and performance thresholds. It does not directly demonstrate whether inspect both pass/fail SLA indicators and the subsequent cost election, which is the stated acceptance result for this Fortinet deployment.
D:Check the selected Internet Service and rule match during a test connection would be meaningful evidence when attempting to match the destination using a FortiGuard Internet Service definition when appropriate. It does not directly demonstrate whether inspect both pass/fail SLA indicators and the subsequent cost election, which is the stated acceptance result for this Fortinet deployment.
Question 176
A Fortinet team is working on this situation: a voice path must remain healthy under jitter and latency limits even if its monetary cost is higher. It attempted: Use SLA eligibility first and compare cost only between passing members. Expected evidence (Inspect both pass/fail SLA indicators and the subsequent cost election) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Adjust inappropriate SLA thresholds before assuming the routing cost is wrong
- Upgrade to a supported maintenance build or use a supported existing strategy rather than inventing CLI flags
- Move or refine the application rule above the broad default rule if payment sessions use the wrong member
- Correct the ISDB match instead of hardcoding one stale destination IP
Explanation
Correct Answer
A:Adjust inappropriate SLA thresholds before assuming the routing cost is wrong. The missing evidence (inspect both pass/fail SLA indicators and the subsequent cost election) points to a problem with the implementation of use SLA eligibility first and compare cost only between passing members. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
B:Upgrade to a supported maintenance build or use a supported existing strategy rather than inventing CLI flags addresses a different operational issue: a service team expects hybrid priority logic on an older FortiOS 7.6 patch. This situation calls for adjust inappropriate SLA thresholds before assuming the routing cost is wrong because the missing result relates to inspect both pass/fail SLA indicators and the subsequent cost election.
C:Move or refine the application rule above the broad default rule if payment sessions use the wrong member addresses a different operational issue: a payment application's traffic must use a low-loss ISP before ordinary browsing rules are evaluated. This situation calls for adjust inappropriate SLA thresholds before assuming the routing cost is wrong because the missing result relates to inspect both pass/fail SLA indicators and the subsequent cost election.
D:Correct the ISDB match instead of hardcoding one stale destination IP addresses a different operational issue: a public SaaS provider changes IP addresses while the branch still needs service-aware steering. This situation calls for adjust inappropriate SLA thresholds before assuming the routing cost is wrong because the missing result relates to inspect both pass/fail SLA indicators and the subsequent cost election.
Question 177
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. An operator sees higher link cost selected and suspects Lowest Cost logic is broken. Which design or implementation decision best meets the stated requirement?
- First verify whether the lower-cost member actually passes the SLA
- Distinguish the automatic strategy from Best Quality and SLA-based modes
- Configure Best Quality strategy using the applicable latency measurement
- Select the highest SLA-value member as the first hybrid comparison
Explanation
Correct Answer
A:First verify whether the lower-cost member actually passes the SLA. This addresses the stated requirement: an operator sees higher link cost selected and suspects Lowest Cost logic is broken. The deployment must satisfy the accompanying requirement (Ensure the health checks and performance measurement inputs are current); the engineer can then validate the result by performing this check: compare health state of both links with their assigned costs.
Incorrect Answers
B:Distinguish the automatic strategy from Best Quality and SLA-based modes is a legitimate choice for another type of situation: an analyst sees the automatic strategy but expects SLA-based quality ranking. The alternative design first requires the team to verify the chosen rule mode before interpreting its path-election result, but it does not directly implement the specified requirement to first verify whether the lower-cost member actually passes the SLA.
C:Configure Best Quality strategy using the applicable latency measurement is a legitimate choice for another type of situation: an application requires selecting the fastest healthy path at each decision. The alternative design first requires the team to define relevant health probes and a suitable link-cost factor, but it does not directly implement the specified requirement to first verify whether the lower-cost member actually passes the SLA.
D:Select the highest SLA-value member as the first hybrid comparison is a legitimate choice for another type of situation: a service uses hybrid SLA and priority evaluation and several members have different SLA values. The alternative design first requires the team to ensure the service is configured for hybrid SLA behavior in the supported FortiOS release, but it does not directly implement the specified requirement to first verify whether the lower-cost member actually passes the SLA.
Question 178
In a deployment where an operator sees higher link cost selected and suspects Lowest Cost logic is broken, the team plans to: First verify whether the lower-cost member actually passes the SLA. Which condition must be established for the chosen implementation to work as described?
- Confirm the configured factor measures the quality attribute the service values
- Ensure the health checks and performance measurement inputs are current
- Check patch support before deploying a hybrid-only service rule
- Confirm no higher-priority rule matches the test session
Explanation
Correct Answer
B:Ensure the health checks and performance measurement inputs are current. This is the enabling condition for first verify whether the lower-cost member actually passes the SLA. Without that prerequisite, the expected operational evidence may not appear: compare health state of both links with their assigned costs. the documented recovery path is to correct the failed lower-cost link or misconfigured probe before rewriting cost preference.
Incorrect Answers
A:Confirm the configured factor measures the quality attribute the service values is relevant when the organization must apply the quality-based link-cost-factor tie-breaker. Here the prerequisite instead concerns first verify whether the lower-cost member actually passes the SLA, so that different condition would not establish the necessary setup for the stated deployment.
C:Check patch support before deploying a hybrid-only service rule is relevant when the organization must validate hybrid feature availability against the specific 7.6 maintenance release. Here the prerequisite instead concerns first verify whether the lower-cost member actually passes the SLA, so that different condition would not establish the necessary setup for the stated deployment.
D:Confirm no higher-priority rule matches the test session is relevant when the organization must examine the implicit SD-WAN rule behavior rather than inventing a hidden explicit match. Here the prerequisite instead concerns first verify whether the lower-cost member actually passes the SLA, so that different condition would not establish the necessary setup for the stated deployment.
Question 179
A team implemented this choice for a customer: First verify whether the lower-cost member actually passes the SLA. The requirement was: an operator sees higher link cost selected and suspects Lowest Cost logic is broken. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Inspect service-rule lookup for the flow and its winning rule ID
- Inspect each candidate's SLA value before examining cost
- Compare health state of both links with their assigned costs
- Verify the payment flow selects the specific service rule before generic rules
Explanation
Correct Answer
C:Compare health state of both links with their assigned costs. It is the specific operational evidence for the requirement that an operator sees higher link cost selected and suspects Lowest Cost logic is broken. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
A:Inspect service-rule lookup for the flow and its winning rule ID would be meaningful evidence when attempting to correct the specificity and order of user-defined SD-WAN rules. It does not directly demonstrate whether compare health state of both links with their assigned costs, which is the stated acceptance result for this Fortinet deployment.
B:Inspect each candidate's SLA value before examining cost would be meaningful evidence when attempting to select the highest SLA-value member as the first hybrid comparison. It does not directly demonstrate whether compare health state of both links with their assigned costs, which is the stated acceptance result for this Fortinet deployment.
D:Verify the payment flow selects the specific service rule before generic rules would be meaningful evidence when attempting to create a specific SD-WAN service rule matching the payment application's traffic. It does not directly demonstrate whether compare health state of both links with their assigned costs, which is the stated acceptance result for this Fortinet deployment.
Question 180
A Fortinet team is working on this situation: an operator sees higher link cost selected and suspects Lowest Cost logic is broken. It attempted: First verify whether the lower-cost member actually passes the SLA. Expected evidence (Compare health state of both links with their assigned costs) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Repair cost configuration if a more expensive tied member is preferred
- Correct the quality factor rather than changing the already equal costs
- Repair rule precedence or criteria before adjusting interface cost
- Correct the failed lower-cost link or misconfigured probe before rewriting cost preference
Explanation
Correct Answer
D:Correct the failed lower-cost link or misconfigured probe before rewriting cost preference. The missing evidence (compare health state of both links with their assigned costs) points to a problem with the implementation of first verify whether the lower-cost member actually passes the SLA. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A:Repair cost configuration if a more expensive tied member is preferred addresses a different operational issue: two members tie on hybrid SLA value but have different costs. This situation calls for correct the failed lower-cost link or misconfigured probe before rewriting cost preference because the missing result relates to compare health state of both links with their assigned costs.
B:Correct the quality factor rather than changing the already equal costs addresses a different operational issue: two hybrid candidates have equal SLA value and cost but different link quality. This situation calls for correct the failed lower-cost link or misconfigured probe before rewriting cost preference because the missing result relates to compare health state of both links with their assigned costs.
C:Repair rule precedence or criteria before adjusting interface cost addresses a different operational issue: a team is troubleshooting why a general cloud rule defeats a specific critical-service rule. This situation calls for correct the failed lower-cost link or misconfigured probe before rewriting cost preference because the missing result relates to compare health state of both links with their assigned costs.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests