Question 77 of 1,000
Advanced VPN and Zero TrusthardMultiple ChoiceObjective-mapped

Quick Answer

The answer is that the FortiGate’s EMS connector is not syncing tag information in real-time, so even though the device tag shows 'Compliant' in EMS, the firewall policy still sees an outdated or missing tag. This happens because ZTNA tag evaluation occurs at session initiation; if the FortiGate has not received the latest tag update from EMS—or if the session was established before the tag was applied—the policy will deny traffic based on the cached, non-compliant state. On the Fortinet NSE 7 Advanced Security NSE7 exam, this scenario tests your understanding of the ZTNA tag synchronization flow and the critical role of the EMS connector’s real-time sync interval. A common trap is assuming that a tag visible in the EMS console is immediately available to the FortiGate, but the connector may poll on a schedule or require a manual refresh. Remember the memory tip: “Tag in EMS doesn’t mean tag in FortiGate—sync before you trust.”

NSE7 Advanced VPN and Zero Trust Practice Question

This NSE7 practice question tests your understanding of advanced vpn and zero trust. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

During a routine audit, a FortiGate administrator discovers that all traffic from a specific user group is being denied by a firewall policy. The policy uses a ZTNA rule that requires the device tag 'Compliant'. The administrator checks the user's device in EMS and sees it is tagged as 'Compliant'. However, the traffic is still denied. What could be the problem?

Question 1hardmultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

The FortiGate's EMS connector is not syncing tag information in real-time

Even if the tag exists, the FortiGate may not have updated tag information from EMS or the session may have been established before the tag was applied. Option A is correct because the FortiGate must re-evaluate tags for new connections; if the EMS connector is not syncing or the session is cached with old tags, it may deny.

Key principle: ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • The FortiGate's EMS connector is not syncing tag information in real-time

    Why this is correct

    ZTNA tags are pulled from EMS periodically. If the connector hasn't synced recently, the FortiGate might still have old tag information for that device.

    Related concept

    Standard ACLs match source addresses.

  • The user's IP address has changed and the tag is mapped to a different IP

    Why it's wrong here

    Tags are typically mapped to device IDs, not IPs; IP changes shouldn't affect tag association.

  • The ZTNA rule is configured with the wrong application port

    Why it's wrong here

    Wrong port would cause the rule not to match at all, not deny with a tag mismatch.

  • The device posture compliance check requires additional criteria not met

    Why it's wrong here

    If the device is tagged as 'Compliant', that tag should satisfy the rule's requirement. However, the rule might require multiple tags; but the stem says the rule requires 'Compliant' and the device has it.

Common exam traps

Common exam trap: ACLs stop at the first match

ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.

Detailed technical explanation

How to think about this question

ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.

KKey Concepts to Remember

  • Standard ACLs match source addresses.
  • Extended ACLs can match source, destination, protocol and ports.
  • The first matching ACL entry is used.
  • There is usually an implicit deny at the end.

TExam Day Tips

  • Check inbound versus outbound direction.
  • Read the ACL from top to bottom.
  • Look for a broader permit or deny above the intended line.

Key takeaway

ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.

Real-world example

How this comes up in practice

A security administrator must allow nursing staff to reach a patient records server while blocking access from the guest Wi-Fi VLAN. After applying an extended ACL, traffic is still blocked from nursing workstations. The ACL was applied outbound instead of inbound on the wrong interface. Questions like this test ACL direction and placement rules.

What to study next

Got this wrong? Here's your next step.

Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related NSE7 ACL questions on filtering logic and placement.

Related practice questions

Related NSE7 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free NSE7 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this NSE7 question test?

Advanced VPN and Zero Trust — This question tests Advanced VPN and Zero Trust — Standard ACLs match source addresses..

What is the correct answer to this question?

The correct answer is: The FortiGate's EMS connector is not syncing tag information in real-time — Even if the tag exists, the FortiGate may not have updated tag information from EMS or the session may have been established before the tag was applied. Option A is correct because the FortiGate must re-evaluate tags for new connections; if the EMS connector is not syncing or the session is cached with old tags, it may deny.

What should I do if I get this NSE7 question wrong?

Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related NSE7 ACL questions on filtering logic and placement.

What is the key concept behind this question?

Standard ACLs match source addresses.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 21, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This NSE7 practice question is part of Courseiva's free Fortinet certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the NSE7 exam.