Users on a remote office subnet () report that they cannot access a cloud database hosted at . Follow the standard CompTIA network troubleshooting methodology to arrange the administrative actions into the correct logical sequence from first step to last step.
- 1Question affected users to determine exact error messages, and review local workstation default gateway settings.
- 2Execute traceroute and inspect interface ACLs on the edge router to confirm if traffic is being dropped by an implicit deny entry.
- 3Modify the edge router access list to explicitly permit database traffic from to .
- 4Test database connectivity from a user workstation to ensure full system functionality and confirm no secondary issues were introduced.
- 5Log the root cause, revised ACL rule order, and connectivity test results in the central ticketing system.
Answer
The correct order follows the standard troubleshooting methodology: first gather information from users and host settings, second test a theory using diagnostic tools like traceroute and inspecting ACL configuration, third implement the corrective ACL rule change, fourth verify full database connectivity from the client workstation, and finally document the findings and actions taken.
The standard CompTIA network troubleshooting sequence requires progressing linearly through: 1) Identify the problem / gather information, 2) Establish and test a theory of probable cause, 3) Plan and implement the solution, 4) Verify full system functionality, and 5) Document findings, actions, and outcomes.
Step-by-Step Solution
Key Concept
CompTIA Network Troubleshooting Methodology applied to Gateway ACL issues