An end user of an online car dealer is facing poor response. The car dealer checks with the system administrator and is told that there is no problem in the web or DBMS servers. Which of the following is likely to be true?
-
The system administrator is telling a lie
-
There is a delay either at network or client PC or both
-
The problem will get solved upon reboot
-
Network capacity will need to be upgraded
To solve this question, the user needs to understand the possible reasons for poor response from an online car dealer.
Option A: This option is unlikely to be true. Assuming the system administrator is competent, they would have checked the web or DBMS servers before giving an answer. It is also unprofessional to lie about a technical issue.
Option B: This option is likely to be true. Poor response from an online car dealer could be due to a network delay or an issue with the client PC. It is possible that the client PC is not powerful enough to handle the website's requirements, or that there is a delay in the network connection.
Option C: This option is unlikely to be true. Rebooting the system may fix some issues, but it is unlikely to solve a delay issue caused by a network or client PC.
Option D: This option is possible, but it is not the most likely scenario. Upgrading network capacity may be necessary if the website is receiving a large amount of traffic, but it is not the first solution to consider when facing poor response.
Therefore, the most likely answer is:
The Answer is: B. There is a delay either at network or client PC or both.
Since the web and database servers have already been ruled out, the remaining links in the request/response chain are the network path and the client's own PC — either of which can introduce latency (bandwidth, congestion, browser/hardware slowness) that the server-side admin wouldn't see. This is a classic troubleshooting elimination: if the server tier is clear, look downstream toward the client.