Database server slow on access switch: move to core switch?

N10-008 By islever Editorial Last updated

Short answer

D Move the server connection from the access switch to the core switch.

Question

Users report that a database server responds slowly or drops connections to other servers at random during busy times. A technician notices the database and servers are connected to an access switch in the office. Which of the following should the technician do to improve the performance of the database server?
  1. Use different ports on the access switch.
  2. Implement LACP on the connection to the database server.
  3. Move the cable connection for users to the same switch as the database server.
  4. Move the server connection from the access switch to the core switch. Correct Answer

Key Takeaways

The exam tests your understanding of access vs core switch roles and oversubscription; the common trap is choosing LACP when the real issue is server placement on the congested access layer.

The question tests where to place high-traffic servers for optimal performance. The community is split, but the correct answer is D: move the server connection from the access switch to the core switch to avoid oversubscribed access-layer bandwidth.

Common mistake: B. Implement LACP on the connection to the database server is the most common mistake because it seems to increase bandwidth, but it does not address the underlying bottleneck caused by the server being on an access switch with limited uplink capacity.

Expert Analysis

Why the Answer Is Correct

D is correct because database servers and other high-availability servers should be connected to the core switch, not an access switch. Access switches are designed for end-user connectivity and have oversubscribed uplinks to the core, which can cause latency, drops, and slow performance during busy periods. Moving the server to the core switch places it closer to the network backbone, reducing the number of hops and eliminating the access-layer bottleneck. Community comments supporting D correctly note that moving a server to the core switch is a best practice for server traffic, while LACP only helps if the bottleneck is the single link itself.

Why the Other Options Are Wrong

A. Using different ports on the access switch does not increase uplink bandwidth or solve oversubscription; it only changes physical ports on the same congested switch. B. LACP can combine multiple links into one logical link, but the server would still be on the access switch, and the access switch's uplink to the core remains the bottleneck. C. Moving user connections to the same switch as the database server would actually make congestion worse, because user traffic and server traffic would compete for the same limited access-layer resources.

Community Comment Notes

Several commenters advocate B, arguing that moving a server to the core switch is "bad practice" or "pointless." However, those comments miss the distinction between physical placement and logical network design: core switches are built for high-throughput, low-latency traffic, and hosting servers on the core is a valid and common design. One commenter notes that a DBA would first check CPU, RAM, or indexes, but that is outside the scope of this network exam. The tie in votes reflects a common misconception; the exam expects you to focus on network design principles, not server tuning.

Official Reference

https://partners.comptia.org/docs/default-source/resources/comptia-network-n10-008-exam-objectives-(5-0)

This link opens the official vendor documentation in a new tab.

Exam Strategy

When choosing between server placement and link aggregation, remember that access switches are for end users and have limited uplink capacity. If a server is on an access switch, the first improvement is to relocate it to the core or distribution switch, not to add more links to the same congested access layer.

Community Votes

D
50%
B
50%

50% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 7 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 7

  1. subaie503 👍 4 Answered D
    D. Move the server connection from the access switch to the core switch.
  2. bdemps98 👍 2 Answered D
    I don't normally like ChatGPT, but I actually think its response is helpful here to clarify: While implementing LACP could help distribute traffic more evenly across multiple links and provide redundancy, it may not fully address the performance issues experienced during busy times. Therefore, moving the server connection to the core switch (option D) is likely to be a more comprehensive solution in this scenario.
  3. ETQ 👍 2 Answered B
    It's B. There's no way you'd move a server to a core switch, not only that, but the servers are also on the access switch, what good would that do? You need LACP to increase bandwidth during busy times.
  4. ATrek 👍 2 Answered B
    Moving a server to the Core switch is very bad and pointless practise. LACP will provide better speed for the server link.
  5. 72abe44 👍 1
    As a Sr DBA, I would look at the database server and see if it needs CPU, Ram, Stats updated or indexes defragmented.... But that is outside of the scope of this test.
Show 2 more comments
  1. emilia_088 👍 17
    B should be correct
  2. schoha8874 👍 2 Answered B
    be is correct

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

How to Resolve Printer-Workstation Connectivity Issues?

S-grade

Why Can a Workstation Reach the Internet but Not Internal Resources?

S-grade

Which Factor Most Impacts IDF Physical Design?

S-grade

Which database must be deleted to prevent network settings persisting on a reused switch?

S-grade

← Back to N10-008 Study Guide