NSE4_FGT_AD-7.6 Premium File
- 94 Questions & Answers
- Last Update: Nov 17, 2026
A FortiGate deployment has two independent requirements. First: A corporate HTTPS proxy policy must inspect encrypted payloads for malware, but clients show untrusted certificate warnings after deep SSL inspection is enabled. Second: A TLS client receives a chain validation error because a remote server omitted an intermediate certificate during handshake. Which TWO actions directly address both issues?
Deep TLS inspection re-signs inspected server sessions using the configured trusted issuing CA, which clients must trust. The verification is: a managed browser accepts the inspected site certificate and the security profile can inspect the decrypted test payload.
TLS trust validation requires an intact chain from leaf through intermediates to a trusted root. The verification is: a new handshake verifies the expected certificate chain without disabling certificate checks.
Certificate inspection can retain limited metadata visibility without terminating and re-encrypting full application content. The proposed alternative does not demonstrate that a managed browser accepts the inspected site certificate and the security profile can inspect the decrypted test payload and that a new handshake verifies the expected certificate chain without disabling certificate checks.
SSL/SSH inspection only examines encrypted sessions it can intercept and decode under the selected profile and protocol constraints. The proposed alternative does not demonstrate that a managed browser accepts the inspected site certificate and the security profile can inspect the decrypted test payload and that a new handshake verifies the expected certificate chain without disabling certificate checks.
A FortiOS 7.6.0 rollout has already applied: Check FSSO event collection permissions and log source bindings on the replacement domain controllers. The acceptance requirement was: FSSO reports only a subset of employee sign-ins after a domain controller migration, despite LDAP queries working. What evidence should an auditor request?
Passive logon collection depends on domain event access, which is distinct from being able to query LDAP directory objects. Confirm it by checking that sign-ins handled by the new domain controller create corresponding user/IP mappings.
FSSO mappings require visibility of the relevant logon events and usable current IP associations. It does not verify that sign-ins handled by the new domain controller create corresponding user/IP mappings.
Passive identity visibility and imported group membership are separate prerequisites for group-aware firewall policy. It does not verify that sign-ins handled by the new domain controller create corresponding user/IP mappings.
FSSO is intended to reuse supported enterprise sign-on events instead of soliciting credentials on each session. It does not verify that sign-ins handled by the new domain controller create corresponding user/IP mappings.
The firewall maintenance report records: Configure supported IPsec NAT traversal and verify intermediary UDP 500/4500 access as applicable. The documented motivation is: A site-to-site tunnel occasionally drops when a NAT device between peers changes UDP mappings, despite compatible cryptographic proposals. Which follow-up observation demonstrates success?
NAT traversal can encapsulate IPsec traffic over UDP 4500 when NAT devices interfere with native ESP. Confirm it by checking that iKE and protected traffic survive the tested NAT path using the supported encapsulation.
VPN connectivity should be expanded with scoped routing and authorization for explicitly approved subnets. It does not verify that iKE and protected traffic survive the tested NAT path using the supported encapsulation.
Detecting an inactive IKE peer and selecting a viable backup forwarding route are related but distinct controls. It does not verify that iKE and protected traffic survive the tested NAT path using the supported encapsulation.
Phase 2 child SA negotiation requires compatible traffic selectors and cryptographic parameters after IKE is established. It does not verify that iKE and protected traffic survive the tested NAT path using the supported encapsulation.
A FortiOS 7.6.0 team must simultaneously correct: (1) A FortiGate VM in a public cloud receives packets on its external network interface but its secondary data interface never forwards traffic after new deployment. and (2) A compliance team needs a stable record of which public-cloud networks are protected by a virtual firewall before creating an application exception. Select TWO changes that address those distinct deficiencies.
Cloud virtual-network controls can block forwarding even when FortiOS security policies permit it. The verification is: a controlled packet traverses the intended FortiGate VM interfaces and reaches the approved cloud destination.
Cloud inventory by itself does not establish which flows pass through the FortiGate dataplane. The verification is: a sampled protected flow maps to a documented network route and logged FortiGate policy decision.
FortiGate CNF integrates managed cloud firewall inspection with supported cloud network routing patterns. The proposed alternative does not demonstrate that a controlled packet traverses the intended FortiGate VM interfaces and reaches the approved cloud destination and that a sampled protected flow maps to a documented network route and logged FortiGate policy decision.
Cloud-native inspection scope follows supported VPC or network integrations, not all account resources by default. The proposed alternative does not demonstrate that a controlled packet traverses the intended FortiGate VM interfaces and reaches the approved cloud destination and that a sampled protected flow maps to a documented network route and logged FortiGate policy decision.
A FortiOS 7.6.0 administrator receives this production change request: Two FortiGates use certificate-based IKE authentication and one peer fails because the presented certificate's subject does not match the configured identity expectation. The change will be accepted when both peers negotiate successfully with verified expected certificate identities.. Which action best meets both conditions?
IKE certificate authentication validates identity as well as trust, so a valid certificate alone may not satisfy peer ID matching. The required result is: both peers negotiate successfully with verified expected certificate identities.
VPN control-plane logs distinguish negotiation states, while forwarding diagnostics evaluate post-decryption policy and routing. It does not demonstrate that both peers negotiate successfully with verified expected certificate identities.
Certificate-based IKE authentication must enforce trust and revocation policy rather than bypassing validation for availability. It does not demonstrate that both peers negotiate successfully with verified expected certificate identities.
Redundant VPN design needs eligible backup routing and health detection; having two tunnels alone does not implement failover. It does not demonstrate that both peers negotiate successfully with verified expected certificate identities.
A production FortiGate ticket states: A network change creates a VIP using a public address already assigned to an unrelated translation, resulting in unexpected forwarding matches. To close the ticket, the team must show that each public destination and port forwards to exactly the intended backend in controlled tests.. What change directly meets the requirement?
Overlapping destination translations can make inbound service matching ambiguous or conflict with the intended mapping. The required result is: each public destination and port forwards to exactly the intended backend in controlled tests.
Source NAT return translation is normally tracked in the session state and does not require an unsolicited inbound VIP. It does not demonstrate that each public destination and port forwards to exactly the intended backend in controlled tests.
VIP destination translations continue using their configured mapped address until the object changes. It does not demonstrate that each public destination and port forwards to exactly the intended backend in controlled tests.
Hairpin traffic may require a dedicated matching policy and translation to maintain a symmetric return path. It does not demonstrate that each public destination and port forwards to exactly the intended backend in controlled tests.
A production FortiGate ticket states: FSSO reports only a subset of employee sign-ins after a domain controller migration, despite LDAP queries working. To close the ticket, the team must show that sign-ins handled by the new domain controller create corresponding user/IP mappings.. What change directly meets the requirement?
Passive logon collection depends on domain event access, which is distinct from being able to query LDAP directory objects. The required result is: sign-ins handled by the new domain controller create corresponding user/IP mappings.
Passive identity visibility and imported group membership are separate prerequisites for group-aware firewall policy. It does not demonstrate that sign-ins handled by the new domain controller create corresponding user/IP mappings.
The collector must receive or query Windows logon events to build user/IP mappings for FSSO. It does not demonstrate that sign-ins handled by the new domain controller create corresponding user/IP mappings.
The FortiGate must have a working trusted link to the collector to receive passive identity mappings. It does not demonstrate that sign-ins handled by the new domain controller create corresponding user/IP mappings.
A FortiOS 7.6.0 team must simultaneously correct: (1) A newly installed branch FortiGate should be reachable only from the management VLAN, but its LAN interface currently permits administrative HTTPS from every attached subnet. and (2) New firewall antivirus features show unavailable update status even though basic forwarding is functional and internet reachability has been confirmed. Select TWO changes that address those distinct deficiencies.
FortiGate management exposure depends on interface administrative protocols and administrator source restrictions, not on forwarding-policy order. The verification is: an approved management workstation opens the GUI and a client from an unapproved VLAN cannot establish an admin session.
Licensed security services require valid entitlements and connectivity to the appropriate FortiGuard update infrastructure. The verification is: fortiGuard service status is valid and the required security database update succeeds without opening unrelated inbound policies.
FortiOS firmware transitions require a supported path and rollback planning; selecting the newest file without compatibility review is unsafe. The proposed alternative does not demonstrate that an approved management workstation opens the GUI and a client from an unapproved VLAN cannot establish an admin session and that fortiGuard service status is valid and the required security database update succeeds without opening unrelated inbound policies.
Factory defaults are not a safe assumption for production interface or resolver configuration. The proposed alternative does not demonstrate that an approved management workstation opens the GUI and a client from an unapproved VLAN cannot establish an admin session and that fortiGuard service status is valid and the required security database update succeeds without opening unrelated inbound policies.
An administrator implements the reviewed control: Restore approved FortiGuard update reachability while retaining unrelated egress restrictions. It was intended to address: A downloaded file remains undetected because the antivirus database update route is blocked by a newly added egress rule. Which test result proves it worked?
Security signature maintenance requires authorized update connectivity, which can fail independently of user traffic. Confirm it by checking that a fresh security update succeeds and the known test signature is recognized.
Antivirus logs capture malicious-content verdicts, whereas traffic logs primarily show policy and session disposition. It does not verify that a fresh security update succeeds and the known test signature is recognized.
Flow-based antivirus analyzes streams without the same complete-object buffering semantics used in proxy mode. It does not verify that a fresh security update succeeds and the known test signature is recognized.
Log-only monitoring is not equivalent to a blocking antivirus enforcement decision. It does not verify that a fresh security update succeeds and the known test signature is recognized.
A FortiGate change record shows this action: Define a task-appropriate administrator profile and trusted-host restriction, then assign it to the automation administrator. The original problem was: An automation operator needs CLI administration without granting unrestricted super_admin privileges to the account. Which observation most directly verifies the intended outcome?
Administrator profiles define management permissions and trusted hosts constrain where an administrator may connect. Confirm it by checking that the automation account performs its delegated task but cannot change unrelated global settings or log in from an untrusted source.
FortiGate management exposure depends on interface administrative protocols and administrator source restrictions, not on forwarding-policy order. It does not verify that the automation account performs its delegated task but cannot change unrelated global settings or log in from an untrusted source.
DHCP service options are supplied by the interface's DHCP configuration, not by DNS filtering security profiles. It does not verify that the automation account performs its delegated task but cannot change unrelated global settings or log in from an untrusted source.
Licensed security services require valid entitlements and connectivity to the appropriate FortiGuard update infrastructure. It does not verify that the automation account performs its delegated task but cannot change unrelated global settings or log in from an untrusted source.
A FortiOS 7.6.0 engineer faces this problem: A FortiGate has local disks available, but the team selected memory logging while expecting several days of on-box search history. The planned action is: Change the supported log-storage configuration to an appropriate persistent disk destination and set retention according to capacity. Which technical explanation makes that action appropriate?
Device-specific log destinations and retention settings determine how much historical traffic evidence remains locally searchable.
The proposed step would enable the relevant security-event logging and inspect the web-filter log action, category and policy details; it does not establish that traffic logs created before a maintenance restart remain queryable within the configured retention interval.
The proposed step would validate analyzer registration, management connectivity and the configured log destination before changing security inspection profiles; it does not establish that traffic logs created before a maintenance restart remain queryable within the configured retention interval.
The proposed step would verify structured log forwarding and preserve device identifiers, timestamps and policy IDs in the ingestion mapping; it does not establish that traffic logs created before a maintenance restart remain queryable within the configured retention interval.
Please check your mailbox for a message from support@examlabs.com and follow the directions.