HPE6-A85 Exam - Topic 3 Question 47 Discussion

Actual exam question for HP's HPE6-A85 exam

Question #: 47
Topic #: 3

You have been asked to troubleshoot failed connectivity between a local subnet in the HQ Office and a remote subnet in the Branch Office. PC1 is unable to ping PC2.

Use the provided topology and show command output to identify the reason for the failure:

AOn Branch Office - L3-SW-2- There is no Layer 3 SVI configured in the correct subnet.

BOn HQ Office L3-SW-1 - There is no route to the Branch Office.

COn HQ Office L3-SW-1 - The switch does not have a static default route to the internet.

DOn Branch Office L3-SW-2- The switch does not have a static route to the HQ Office Local Subnet.

Show Suggested Answer

Suggested Answer: D

Using the provided topology and show command output, it can be determined that L3-SW-2 in the Branch Office does not have a route to reach the subnet where PC1 resides (192.168.1.0/24 in the HQ Office). L3-SW-1 in the HQ Office has a route to the Branch Office subnet (172.16.1.0/24), but without the reciprocal route on L3-SW-2, traffic from the Branch Office will not be able to reach the HQ Office subnet, hence PC1 cannot ping PC2.

by Telma at Aug 18, 2025, 06:15 PM

Limited Time Offer

25%

Off

Get Premium HPE6-A85 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Lynsey

2 months ago

HQ's switch missing a static route could also be the problem.

upvoted 0 times

...

Jesus

2 months ago

Totally agree, that's a common issue!

upvoted 0 times

...

Cherelle

3 months ago

Wait, how can there be no route to the Branch Office? That seems odd.

upvoted 0 times

...

Asuncion

3 months ago

Nah, I think the default route issue is a red herring here.

upvoted 0 times

...

Garry

3 months ago

Looks like there's no Layer 3 SVI on the Branch Office switch.

upvoted 0 times

...

Kris

3 months ago

I think option D makes sense too; if L3-SW-2 doesn’t have a route back to HQ, that could definitely block the ping.

upvoted 0 times

...

Jenise

4 months ago

I feel like option C is less likely since it mentions the internet, but I guess it could still affect local subnet communication somehow?

upvoted 0 times

...

Micaela

4 months ago

I’m not entirely sure, but I think option B about the route on L3-SW-1 could also be a possibility since routing issues often come up in practice questions.

upvoted 0 times

...

Ashleigh

4 months ago

I remember we discussed how missing SVIs can cause connectivity issues, so option A might be a strong candidate.

upvoted 0 times

...

Filiberto

4 months ago

This seems like a classic routing problem. I'll focus on checking the routing configuration on both the HQ Office and Branch Office switches to see if there are any missing or incorrect routes that could be causing the connectivity failure.

upvoted 0 times

...

Merlyn

4 months ago

Okay, let's see here. Based on the information provided, it seems like the issue could be either a missing Layer 3 SVI on the Branch Office switch or a missing route on the HQ Office switch. I'll need to analyze the details closely to determine the exact problem.

upvoted 0 times

...

Cordell

4 months ago

Hmm, I'm a bit unsure about this one. There are a lot of details to consider with the different switches and subnets. I'll need to carefully review the topology and command outputs to identify the root cause.

upvoted 0 times

...

Mila

5 months ago

This looks like a pretty straightforward connectivity issue. I'll start by checking the Layer 3 configuration on the switches to see if the subnets are properly configured and routed.

upvoted 0 times

...

Hector

5 months ago

Seriously, who designs a network with this many switches and no redundancy? I mean, come on, they're just asking for trouble. Whoever came up with this topology needs to go back to networking school.

upvoted 0 times

...

Enola

5 months ago

I think the issue might be with the Layer 3 SVI configuration on L3-SW-2 in the Branch Office.

upvoted 0 times

...

Hayley

6 months ago

Ah, this one's tricky. The connectivity issue seems to be on the Branch Office side, but which part is the real problem? I'm leaning towards D, but I'll have to double-check those command outputs to be sure.

upvoted 0 times

Abraham

5 months ago

User 1: I think the problem might be on the Branch Office side.

upvoted 0 times

...