試験NSE4_FGT_AD-7.6-JPN トピック2 問題44 スレッド
Fortinet NSE4_FGT_AD-7.6-JPNのリアル試験問題集
問題 #: 44
トピック #: 2
問題 #: 44
トピック #: 2
展示資料を参照してください。

管理者が静的ルートの宛先として使用する新しいファイアウォールアドレスを作成しました。管理者が新しい静的ルートの宛先フィールドで新しいアドレスを選択できないのはなぜですか?(回答を1つ選択してください)

管理者が静的ルートの宛先として使用する新しいファイアウォールアドレスを作成しました。管理者が新しい静的ルートの宛先フィールドで新しいアドレスを選択できないのはなぜですか?(回答を1つ選択してください)
おすすめの解答:D 解答を投票する
"If you create a firewall address object with the type Subnet or FQDN, you can use that firewall address as the destination of one or more static routes. First, enable Routing configuration in the firewall address configuration. After you enable it, the firewall address object becomes available for use in the Destination drop-down list for static routes with named addresses." Technical Deep Dive:
The correct answer is D. The exhibit shows an FQDN address object (www.fortinet.com), but Routing configuration is disabled. FortiGate does not make that object available as a selectable destination for named static routes until this option is enabled.
Why the others are wrong:
A is incomplete. Even if the static route uses Named Address, the object still will not appear unless Routing configuration is enabled on the address object.
B is not the first requirement from the study guide. DNS resolution matters operationally for FQDN objects, but the documented reason it does not appear in the drop-down is the missing Routing configuration setting.
C is unrelated. The interface does not have to be set to port2 first just to make the address object selectable.
In practice, the fix is:
config firewall address
edit "Fortinet"
set type fqdn
set fqdn "www.fortinet.com"
set allow-routing enable
next
end
After that, the object becomes available in the static route Destination field when using a named address.
The correct answer is D. The exhibit shows an FQDN address object (www.fortinet.com), but Routing configuration is disabled. FortiGate does not make that object available as a selectable destination for named static routes until this option is enabled.
Why the others are wrong:
A is incomplete. Even if the static route uses Named Address, the object still will not appear unless Routing configuration is enabled on the address object.
B is not the first requirement from the study guide. DNS resolution matters operationally for FQDN objects, but the documented reason it does not appear in the drop-down is the missing Routing configuration setting.
C is unrelated. The interface does not have to be set to port2 first just to make the address object selectable.
In practice, the fix is:
config firewall address
edit "Fortinet"
set type fqdn
set fqdn "www.fortinet.com"
set allow-routing enable
next
end
After that, the object becomes available in the static route Destination field when using a named address.
真*瞳 2026-05-12 07:49:49
コメント
他人の解答コメントを賛成するのも、その解答に一票を入れることになります。したがって、すでに同じ意見の投票コメントが存在する場合、新規コメントをする代わりに賛成することもできます。
コメントを通報する
コメント中
今すぐ 新規登録 / ログイン (無料です)。