Pass Juniper JN0-650 Exam in First Attempt Easily
Real Juniper JN0-650 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts

JN0-650 Premium File

  • 107 Questions & Answers
  • Last Update: Nov 8, 2026
$69.99 $76.99

Enterprise Routing and Switching, Professional (JNCIP-ENT) JN0-650 Practice Test 53

Question 520

A campus phone learns no voice network policy while basic LLDP neighbor discovery succeeds. If the team bypasses or fails to implement the targeted correction (Enable supported LLDP-MED network-policy advertisement on the phone-facing EX interface.), which direct operational risk or residual exposure is MOST relevant?

  1. Plain LLDP neighbor discovery alone does not guarantee that a voice VLAN policy is advertised.
  2. Mismatched tagging between phone and switch can strand voice traffic in the data VLAN.
  3. Assuming a switch interface label equals the physical handset connection can misdirect repairs.
  4. Placing both devices into one unrestricted VLAN can defeat traffic segregation and security.

Explanation

Correct Answer

A:

Plain LLDP neighbor discovery alone does not guarantee that a voice VLAN policy is advertised. This is the consequence linked to the observed situation: A campus phone learns no voice network policy while basic LLDP neighbor discovery succeeds. It is prevented by: Enable supported LLDP-MED network-policy advertisement on the phone-facing EX interface. The underlying reason is: LLDP-MED extends LLDP with endpoint network-policy information for voice deployments.

Incorrect Answers

B:

Mismatched tagging between phone and switch can strand voice traffic in the data VLAN. This risk belongs to a different operational problem: An IP phone sends untagged voice packets despite a switch VLAN configuration that requires 802.1Q tagged voice frames. The stated condition instead exposes this direct risk: Plain LLDP neighbor discovery alone does not guarantee that a voice VLAN policy is advertised. The appropriate mitigation is: Enable supported LLDP-MED network-policy advertisement on the phone-facing EX interface.

C:

Assuming a switch interface label equals the physical handset connection can misdirect repairs. This risk belongs to a different operational problem: An IP phone receives an LLDP neighbor identity from the wrong switch port after cabling was moved across a patch panel. The stated condition instead exposes this direct risk: Plain LLDP neighbor discovery alone does not guarantee that a voice VLAN policy is advertised. The appropriate mitigation is: Enable supported LLDP-MED network-policy advertisement on the phone-facing EX interface.

D:

Placing both devices into one unrestricted VLAN can defeat traffic segregation and security. This risk belongs to a different operational problem: A phone and downstream desktop PC share one physical EX switch port but their traffic must use different voice and data VLANs. The stated condition instead exposes this direct risk: Plain LLDP neighbor discovery alone does not guarantee that a voice VLAN policy is advertised. The appropriate mitigation is: Enable supported LLDP-MED network-policy advertisement on the phone-facing EX interface.

Question 521

An IP phone sends untagged voice packets despite a switch VLAN configuration that requires 802.1Q tagged voice frames. Which targeted engineering change is MOST directly justified by the observed evidence?

  1. Verify DHCP, routing, and call-server reachability from the newly assigned voice VLAN.
  2. Check power budget, supported PoE class and per-port power allocation before modifying voice VLAN tags.
  3. Verify the LLDP-MED network-policy VLAN tag advertisement and phone tagging capability.
  4. Review LLDP-MED QoS policy, ingress classification, and the forwarding-class mapping.

Explanation

Correct Answer

C:

Verify the LLDP-MED network-policy VLAN tag advertisement and phone tagging capability. This change specifically addresses the reported evidence: An IP phone sends untagged voice packets despite a switch VLAN configuration that requires 802.1Q tagged voice frames. The relevant protocol mechanism is: LLDP-MED can communicate tagged voice VLAN and CoS parameters to compatible phones. A decisive acceptance test would be: A capture shows the handset using the intended voice VLAN tag for media and signaling.

Incorrect Answers

A:

Verify DHCP, routing, and call-server reachability from the newly assigned voice VLAN. This is a valid solution to a different Junos situation: A remote phone cannot register after a voice VLAN migration: PoE and LLDP-MED work and tagged frames reach the gateway, but DHCP offers and call-server routes are missing. It does not directly correct the specific failure evidence here: An IP phone sends untagged voice packets despite a switch VLAN configuration that requires 802.1Q tagged voice frames. The required targeted change is: Verify the LLDP-MED network-policy VLAN tag advertisement and phone tagging capability.

B:

Check power budget, supported PoE class and per-port power allocation before modifying voice VLAN tags. This is a valid solution to a different Junos situation: An IP phone powered by PoE fails to boot on an access switch because the interface has no available power budget after several new devices were connected. It does not directly correct the specific failure evidence here: An IP phone sends untagged voice packets despite a switch VLAN configuration that requires 802.1Q tagged voice frames. The required targeted change is: Verify the LLDP-MED network-policy VLAN tag advertisement and phone tagging capability.

D:

Review LLDP-MED QoS policy, ingress classification, and the forwarding-class mapping. This is a valid solution to a different Junos situation: A call-quality test shows voice media entering a best-effort queue even though the handset is marked with a supported 802.1p priority. It does not directly correct the specific failure evidence here: An IP phone sends untagged voice packets despite a switch VLAN configuration that requires 802.1Q tagged voice frames. The required targeted change is: Verify the LLDP-MED network-policy VLAN tag advertisement and phone tagging capability.

Question 522

An IP phone sends untagged voice packets despite a switch VLAN configuration that requires 802.1Q tagged voice frames. The proposed correction is: Verify the LLDP-MED network-policy VLAN tag advertisement and phone tagging capability. Which observation MOST directly confirms this fault is resolved?

  1. The handset receives valid voice-subnet addressing and connects to its call service.
  2. Voice frames on the advertised VLAN are accepted and the phone reaches its call server.
  3. The phone marks the expected class and the ingress switch counters place RTP in the intended queue.
  4. A capture shows the handset using the intended voice VLAN tag for media and signaling.

Explanation

Correct Answer

D:

A capture shows the handset using the intended voice VLAN tag for media and signaling. This is the direct acceptance evidence for the observed failure: An IP phone sends untagged voice packets despite a switch VLAN configuration that requires 802.1Q tagged voice frames. The mechanism being validated is: LLDP-MED can communicate tagged voice VLAN and CoS parameters to compatible phones.

Incorrect Answers

A:

The handset receives valid voice-subnet addressing and connects to its call service. That would validate a different condition: A remote phone cannot register after a voice VLAN migration: PoE and LLDP-MED work and tagged frames reach the gateway, but DHCP offers and call-server routes are missing. The decisive check for the current issue is: A capture shows the handset using the intended voice VLAN tag for media and signaling.

B:

Voice frames on the advertised VLAN are accepted and the phone reaches its call server. That would validate a different condition: A configured LLDP-MED phone receives a voice VLAN ID that is absent from allowed VLAN membership on its switch port. The decisive check for the current issue is: A capture shows the handset using the intended voice VLAN tag for media and signaling.

C:

The phone marks the expected class and the ingress switch counters place RTP in the intended queue. That would validate a different condition: A call-quality test shows voice media entering a best-effort queue even though the handset is marked with a supported 802.1p priority. The decisive check for the current issue is: A capture shows the handset using the intended voice VLAN tag for media and signaling.

Question 523

A Junos engineer proposes this response: Verify the LLDP-MED network-policy VLAN tag advertisement and phone tagging capability. The situation is: An IP phone sends untagged voice packets despite a switch VLAN configuration that requires 802.1Q tagged voice frames. Which technical principle BEST justifies the response?

  1. LLDP-MED can communicate tagged voice VLAN and CoS parameters to compatible phones.
  2. LLDP-MED extends LLDP with endpoint network-policy information for voice deployments.
  3. Voice VLAN assignment depends on network policy messages and port VLAN support.
  4. LLDP carries neighboring device and port identity for link discovery.

Explanation

Correct Answer

A:

LLDP-MED can communicate tagged voice VLAN and CoS parameters to compatible phones. This is the controlling mechanism in the specific case: An IP phone sends untagged voice packets despite a switch VLAN configuration that requires 802.1Q tagged voice frames. It predicts the acceptance result: A capture shows the handset using the intended voice VLAN tag for media and signaling.

Incorrect Answers

B:

LLDP-MED extends LLDP with endpoint network-policy information for voice deployments. This principle explains a separate situation: A campus phone learns no voice network policy while basic LLDP neighbor discovery succeeds. For this issue the relevant mechanism is: LLDP-MED can communicate tagged voice VLAN and CoS parameters to compatible phones.

C:

Voice VLAN assignment depends on network policy messages and port VLAN support. This principle explains a separate situation: A corporate handset supports LLDP-MED, but the switch still provides an incorrect voice VLAN after a site migration. For this issue the relevant mechanism is: LLDP-MED can communicate tagged voice VLAN and CoS parameters to compatible phones.

D:

LLDP carries neighboring device and port identity for link discovery. This principle explains a separate situation: An IP phone receives an LLDP neighbor identity from the wrong switch port after cabling was moved across a patch panel. For this issue the relevant mechanism is: LLDP-MED can communicate tagged voice VLAN and CoS parameters to compatible phones.

Question 524

An IP phone sends untagged voice packets despite a switch VLAN configuration that requires 802.1Q tagged voice frames. If the team bypasses or fails to implement the targeted correction (Verify the LLDP-MED network-policy VLAN tag advertisement and phone tagging capability.), which direct operational risk or residual exposure is MOST relevant?

  1. Plain LLDP neighbor discovery alone does not guarantee that a voice VLAN policy is advertised.
  2. Mismatched tagging between phone and switch can strand voice traffic in the data VLAN.
  3. Powering the phone successfully does not mean the voice network policy is correct.
  4. Assuming a switch interface label equals the physical handset connection can misdirect repairs.

Explanation

Correct Answer

B:

Mismatched tagging between phone and switch can strand voice traffic in the data VLAN. This is the consequence linked to the observed situation: An IP phone sends untagged voice packets despite a switch VLAN configuration that requires 802.1Q tagged voice frames. It is prevented by: Verify the LLDP-MED network-policy VLAN tag advertisement and phone tagging capability. The underlying reason is: LLDP-MED can communicate tagged voice VLAN and CoS parameters to compatible phones.

Incorrect Answers

A:

Plain LLDP neighbor discovery alone does not guarantee that a voice VLAN policy is advertised. This risk belongs to a different operational problem: A campus phone learns no voice network policy while basic LLDP neighbor discovery succeeds. The stated condition instead exposes this direct risk: Mismatched tagging between phone and switch can strand voice traffic in the data VLAN. The appropriate mitigation is: Verify the LLDP-MED network-policy VLAN tag advertisement and phone tagging capability.

C:

Powering the phone successfully does not mean the voice network policy is correct. This risk belongs to a different operational problem: A corporate handset supports LLDP-MED, but the switch still provides an incorrect voice VLAN after a site migration. The stated condition instead exposes this direct risk: Mismatched tagging between phone and switch can strand voice traffic in the data VLAN. The appropriate mitigation is: Verify the LLDP-MED network-policy VLAN tag advertisement and phone tagging capability.

D:

Assuming a switch interface label equals the physical handset connection can misdirect repairs. This risk belongs to a different operational problem: An IP phone receives an LLDP neighbor identity from the wrong switch port after cabling was moved across a patch panel. The stated condition instead exposes this direct risk: Mismatched tagging between phone and switch can strand voice traffic in the data VLAN. The appropriate mitigation is: Verify the LLDP-MED network-policy VLAN tag advertisement and phone tagging capability.

Question 525

A phone and downstream desktop PC share one physical EX switch port but their traffic must use different voice and data VLANs. Which targeted engineering change is MOST directly justified by the observed evidence?

  1. Align the advertised voice VLAN with the switch's permitted port VLAN membership.
  2. Use LLDP neighbor detail and physical port mapping to locate the actual access connection.
  3. Verify the available external power and focus troubleshooting on the phone's data and voice policy instead.
  4. Configure supported voice VLAN and data VLAN handling with the appropriate endpoint/authentication design.

Explanation

Correct Answer

D:

Configure supported voice VLAN and data VLAN handling with the appropriate endpoint/authentication design. This change specifically addresses the reported evidence: A phone and downstream desktop PC share one physical EX switch port but their traffic must use different voice and data VLANs. The relevant protocol mechanism is: Voice VLAN features separate telephony traffic from the data traffic sharing an access link. A decisive acceptance test would be: The phone's frames use the voice VLAN while the desktop remains on its permitted data VLAN.

Incorrect Answers

A:

Align the advertised voice VLAN with the switch's permitted port VLAN membership. This is a valid solution to a different Junos situation: A configured LLDP-MED phone receives a voice VLAN ID that is absent from allowed VLAN membership on its switch port. It does not directly correct the specific failure evidence here: A phone and downstream desktop PC share one physical EX switch port but their traffic must use different voice and data VLANs. The required targeted change is: Configure supported voice VLAN and data VLAN handling with the appropriate endpoint/authentication design.

B:

Use LLDP neighbor detail and physical port mapping to locate the actual access connection. This is a valid solution to a different Junos situation: An IP phone receives an LLDP neighbor identity from the wrong switch port after cabling was moved across a patch panel. It does not directly correct the specific failure evidence here: A phone and downstream desktop PC share one physical EX switch port but their traffic must use different voice and data VLANs. The required targeted change is: Configure supported voice VLAN and data VLAN handling with the appropriate endpoint/authentication design.

C:

Verify the available external power and focus troubleshooting on the phone's data and voice policy instead. This is a valid solution to a different Junos situation: A telephone with an external AC adapter works on a port with PoE disabled, yet engineers plan to enable PoE solely for voice service. It does not directly correct the specific failure evidence here: A phone and downstream desktop PC share one physical EX switch port but their traffic must use different voice and data VLANs. The required targeted change is: Configure supported voice VLAN and data VLAN handling with the appropriate endpoint/authentication design.

Question 526

A phone and downstream desktop PC share one physical EX switch port but their traffic must use different voice and data VLANs. The proposed correction is: Configure supported voice VLAN and data VLAN handling with the appropriate endpoint/authentication design. Which observation MOST directly confirms this fault is resolved?

  1. The phone's frames use the voice VLAN while the desktop remains on its permitted data VLAN.
  2. Voice frames on the advertised VLAN are accepted and the phone reaches its call server.
  3. The observed remote chassis and port identifiers match the corrected physical connection.
  4. The phone stays powered by its adapter and joins the expected authorized VLAN.

Explanation

Correct Answer

A:

The phone's frames use the voice VLAN while the desktop remains on its permitted data VLAN. This is the direct acceptance evidence for the observed failure: A phone and downstream desktop PC share one physical EX switch port but their traffic must use different voice and data VLANs. The mechanism being validated is: Voice VLAN features separate telephony traffic from the data traffic sharing an access link.

Incorrect Answers

B:

Voice frames on the advertised VLAN are accepted and the phone reaches its call server. That would validate a different condition: A configured LLDP-MED phone receives a voice VLAN ID that is absent from allowed VLAN membership on its switch port. The decisive check for the current issue is: The phone's frames use the voice VLAN while the desktop remains on its permitted data VLAN.

C:

The observed remote chassis and port identifiers match the corrected physical connection. That would validate a different condition: An IP phone receives an LLDP neighbor identity from the wrong switch port after cabling was moved across a patch panel. The decisive check for the current issue is: The phone's frames use the voice VLAN while the desktop remains on its permitted data VLAN.

D:

The phone stays powered by its adapter and joins the expected authorized VLAN. That would validate a different condition: A telephone with an external AC adapter works on a port with PoE disabled, yet engineers plan to enable PoE solely for voice service. The decisive check for the current issue is: The phone's frames use the voice VLAN while the desktop remains on its permitted data VLAN.

Question 527

A Junos engineer proposes this response: Configure supported voice VLAN and data VLAN handling with the appropriate endpoint/authentication design. The situation is: A phone and downstream desktop PC share one physical EX switch port but their traffic must use different voice and data VLANs. Which technical principle BEST justifies the response?

  1. LLDP-MED policy distribution and actual switch forwarding VLAN membership must agree.
  2. Voice VLAN features separate telephony traffic from the data traffic sharing an access link.
  3. LLDP carries neighboring device and port identity for link discovery.
  4. PoE is not required when the endpoint already has a supported external power source.

Explanation

Correct Answer

B:

Voice VLAN features separate telephony traffic from the data traffic sharing an access link. This is the controlling mechanism in the specific case: A phone and downstream desktop PC share one physical EX switch port but their traffic must use different voice and data VLANs. It predicts the acceptance result: The phone's frames use the voice VLAN while the desktop remains on its permitted data VLAN.

Incorrect Answers

A:

LLDP-MED policy distribution and actual switch forwarding VLAN membership must agree. This principle explains a separate situation: A configured LLDP-MED phone receives a voice VLAN ID that is absent from allowed VLAN membership on its switch port. For this issue the relevant mechanism is: Voice VLAN features separate telephony traffic from the data traffic sharing an access link.

C:

LLDP carries neighboring device and port identity for link discovery. This principle explains a separate situation: An IP phone receives an LLDP neighbor identity from the wrong switch port after cabling was moved across a patch panel. For this issue the relevant mechanism is: Voice VLAN features separate telephony traffic from the data traffic sharing an access link.

D:

PoE is not required when the endpoint already has a supported external power source. This principle explains a separate situation: A telephone with an external AC adapter works on a port with PoE disabled, yet engineers plan to enable PoE solely for voice service. For this issue the relevant mechanism is: Voice VLAN features separate telephony traffic from the data traffic sharing an access link.

Question 528

A phone and downstream desktop PC share one physical EX switch port but their traffic must use different voice and data VLANs. If the team bypasses or fails to implement the targeted correction (Configure supported voice VLAN and data VLAN handling with the appropriate endpoint/authentication design.), which direct operational risk or residual exposure is MOST relevant?

  1. Advertising an unusable voice VLAN does not create forwarding connectivity for tagged packets.
  2. Assuming a switch interface label equals the physical handset connection can misdirect repairs.
  3. Placing both devices into one unrestricted VLAN can defeat traffic segregation and security.
  4. Misidentifying the phone power source can waste remediation time on a nonissue.

Explanation

Correct Answer

C:

Placing both devices into one unrestricted VLAN can defeat traffic segregation and security. This is the consequence linked to the observed situation: A phone and downstream desktop PC share one physical EX switch port but their traffic must use different voice and data VLANs. It is prevented by: Configure supported voice VLAN and data VLAN handling with the appropriate endpoint/authentication design. The underlying reason is: Voice VLAN features separate telephony traffic from the data traffic sharing an access link.

Incorrect Answers

A:

Advertising an unusable voice VLAN does not create forwarding connectivity for tagged packets. This risk belongs to a different operational problem: A configured LLDP-MED phone receives a voice VLAN ID that is absent from allowed VLAN membership on its switch port. The stated condition instead exposes this direct risk: Placing both devices into one unrestricted VLAN can defeat traffic segregation and security. The appropriate mitigation is: Configure supported voice VLAN and data VLAN handling with the appropriate endpoint/authentication design.

B:

Assuming a switch interface label equals the physical handset connection can misdirect repairs. This risk belongs to a different operational problem: An IP phone receives an LLDP neighbor identity from the wrong switch port after cabling was moved across a patch panel. The stated condition instead exposes this direct risk: Placing both devices into one unrestricted VLAN can defeat traffic segregation and security. The appropriate mitigation is: Configure supported voice VLAN and data VLAN handling with the appropriate endpoint/authentication design.

D:

Misidentifying the phone power source can waste remediation time on a nonissue. This risk belongs to a different operational problem: A telephone with an external AC adapter works on a port with PoE disabled, yet engineers plan to enable PoE solely for voice service. The stated condition instead exposes this direct risk: Placing both devices into one unrestricted VLAN can defeat traffic segregation and security. The appropriate mitigation is: Configure supported voice VLAN and data VLAN handling with the appropriate endpoint/authentication design.

Question 529

A configured LLDP-MED phone receives a voice VLAN ID that is absent from allowed VLAN membership on its switch port. Which targeted engineering change is MOST directly justified by the observed evidence?

  1. Align the advertised voice VLAN with the switch's permitted port VLAN membership.
  2. Configure supported voice VLAN and data VLAN handling with the appropriate endpoint/authentication design.
  3. Correct the per-port or site voice network policy rather than changing unrelated PoE wattage.
  4. Enable supported LLDP-MED network-policy advertisement on the phone-facing EX interface.

Explanation

Correct Answer

A:

Align the advertised voice VLAN with the switch's permitted port VLAN membership. This change specifically addresses the reported evidence: A configured LLDP-MED phone receives a voice VLAN ID that is absent from allowed VLAN membership on its switch port. The relevant protocol mechanism is: LLDP-MED policy distribution and actual switch forwarding VLAN membership must agree. A decisive acceptance test would be: Voice frames on the advertised VLAN are accepted and the phone reaches its call server.

Incorrect Answers

B:

Configure supported voice VLAN and data VLAN handling with the appropriate endpoint/authentication design. This is a valid solution to a different Junos situation: A phone and downstream desktop PC share one physical EX switch port but their traffic must use different voice and data VLANs. It does not directly correct the specific failure evidence here: A configured LLDP-MED phone receives a voice VLAN ID that is absent from allowed VLAN membership on its switch port. The required targeted change is: Align the advertised voice VLAN with the switch's permitted port VLAN membership.

C:

Correct the per-port or site voice network policy rather than changing unrelated PoE wattage. This is a valid solution to a different Junos situation: A corporate handset supports LLDP-MED, but the switch still provides an incorrect voice VLAN after a site migration. It does not directly correct the specific failure evidence here: A configured LLDP-MED phone receives a voice VLAN ID that is absent from allowed VLAN membership on its switch port. The required targeted change is: Align the advertised voice VLAN with the switch's permitted port VLAN membership.

D:

Enable supported LLDP-MED network-policy advertisement on the phone-facing EX interface. This is a valid solution to a different Junos situation: A campus phone learns no voice network policy while basic LLDP neighbor discovery succeeds. It does not directly correct the specific failure evidence here: A configured LLDP-MED phone receives a voice VLAN ID that is absent from allowed VLAN membership on its switch port. The required targeted change is: Align the advertised voice VLAN with the switch's permitted port VLAN membership.

Question 530

A configured LLDP-MED phone receives a voice VLAN ID that is absent from allowed VLAN membership on its switch port. The proposed correction is: Align the advertised voice VLAN with the switch's permitted port VLAN membership. Which observation MOST directly confirms this fault is resolved?

  1. The phone's frames use the voice VLAN while the desktop remains on its permitted data VLAN.
  2. Voice frames on the advertised VLAN are accepted and the phone reaches its call server.
  3. The handset receives and applies the new authorized voice VLAN from LLDP-MED.
  4. End-to-end packet captures show approved voice markings beyond the upstream trust boundary.

Explanation

Correct Answer

B:

Voice frames on the advertised VLAN are accepted and the phone reaches its call server. This is the direct acceptance evidence for the observed failure: A configured LLDP-MED phone receives a voice VLAN ID that is absent from allowed VLAN membership on its switch port. The mechanism being validated is: LLDP-MED policy distribution and actual switch forwarding VLAN membership must agree.

Incorrect Answers

A:

The phone's frames use the voice VLAN while the desktop remains on its permitted data VLAN. That would validate a different condition: A phone and downstream desktop PC share one physical EX switch port but their traffic must use different voice and data VLANs. The decisive check for the current issue is: Voice frames on the advertised VLAN are accepted and the phone reaches its call server.

C:

The handset receives and applies the new authorized voice VLAN from LLDP-MED. That would validate a different condition: A corporate handset supports LLDP-MED, but the switch still provides an incorrect voice VLAN after a site migration. The decisive check for the current issue is: Voice frames on the advertised VLAN are accepted and the phone reaches its call server.

D:

End-to-end packet captures show approved voice markings beyond the upstream trust boundary. That would validate a different condition: A switch is advertising LLDP-MED DSCP policy to a phone, but an upstream switch rewrites all marked voice traffic to best effort. The decisive check for the current issue is: Voice frames on the advertised VLAN are accepted and the phone reaches its call server.

Enterprise Routing and Switching, Professional (JNCIP-ENT) (JN0-650) Practice Tests

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

Enter Your Email Address to Receive Your 10% Off Discount Code

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your email address below to get started with our interactive software demo of your free trial.

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports