Skip to main content

best ccna exam prepration

CCNA is one of the most respected Associate level Certifications in the world today. Getting a CCNA will definitely help you to get a better job or at least get your foot into the Professional Networking Field. This article will describe the tips we give our students at IPSR to achieve CCNA.

1. Getting ready mentally:First thing you need to do is mentally prepare yourself. That is, you have to seriously think about why why you want to be CCNA certified. You have to firmly decide and believe that you will get CCNA within next 1-2 months or so. Try to budget your study time well. If you a very social person you will have to give up some of your socialising for the next couple of months. Since CCNA includes all the basics of networking you need to spend around 5 hrs per day for a fast track. Keep one thing in mind though; CCNA needs interest and dedication. it covers the most modern communication.
2. Step into the right institute: Find aninstitute with good lab infrastructure, reputation and good results. For a good start, you need a systematically prepared study material rather than a big text. Get an overall view of the topics. Master each chapter and tackle questions from just one chapter until you get sick of it with the help of your teacher. Then move on to the next chapter. Solve Previous Question papers. Practice each protocol with our well planned scenarios in Real Lab. That will make you a WAN expert. Your will be an expert after attending our WAN trouble shooting labs. You can repeat the Labs at your home by using the Router Simulations. Practice makes a man perfect.
3. Getting the right study material: The third thing you need to do is to get proper study material. There is a lot of controversy around this and some people go overboard with study guides, books, Router simulators and such. Cisco Press books INTR and ICND by Wendell Odom are enough as far as books go. They are really well written and easy to follow. Tata McGraw Hills CCNA is also a good reference. Other good stuff is video and audio tutorials like CBT Nuggets. You will get Best CBTs which are prepared by our own experts. To be an expert you should also familiar with installation and usage of some networking tools in real environment. Almost all resourses can be collected from our Resource Manager.
4. Schedule the test: When you schedule for online test you will become more serious about your studies naturally. If you are not comfortable with all topics at the end you can even reschedule the test before 24 hrs. You will get our special exam preparation classes for online exam.
5. Read books one more time to refresh: This is optional, but highly recommended. Reading books one more time before your exam.
6. Cram, Cram and Cram: This is the last part of your study and there is no turning back. The deadline is hanging around your neck like a noose. You should cram Q&A for no more then 10 days before you take the test. Don't do any studying the night or day before the test. Go out with your friends or significant other for a dinner and a movie. Relax. It is very important to relax and get a good night sleep since one of those testing boots could really be intimidating.
7. Interview Preparation.
If you work hard, our experts will make you pass at the first attempt itself. The next step is to win a job interview. Create a good cover letter and resume. You can find good formats which are created by our own expert; and you will get training in interview techniques and other tips. The Cisco Press The IT Career Builder's Toolkit By Matthew Moran is a good reference. After you attend our mock interview session you will be confident to attend any challenging interview

Comments

Popular posts from this blog

Docker Container Management from Cockpit

Cockpit can manage containers via docker. This functionality is present in the Cockpit docker package. Cockpit communicates with docker via its API via the /var/run/docker.sock unix socket. The docker API is root equivalent, and on a properly configured system, only root can access the docker API. If the currently logged in user is not root then Cockpit will try to escalate the user’s privileges via Polkit or sudo before connecting to the socket. Alternatively, we can create a docker Unix group. Anyone in that docker group can then access the docker API, and gain root privileges on the system. [root@rhel8 ~] #  yum install cockpit-docker    -y  Once the package installed then "containers" section would be added in the dashboard and we can manage the containers and images from the console. We can search or pull an image from docker hub just by searching with the keyword like nginx centos.   Once the Image downloaded we can start a contai

Remote Systems Management With Cockpit

The cockpit is a Red Hat Enterprise Linux web-based interface designed for managing and monitoring your local system, as well as Linux servers located in your network environment. In RHEL 8 Cockpit is the default installation candidate we can just start the service and then can start the management of machines. For RHEL7 or Fedora based machines we can follow steps to install and configure the cockpit.  Following are the few features of cockpit.  Managing services Managing user accounts Managing and monitoring system services Configuring network interfaces and firewall Reviewing system logs Managing virtual machines Creating diagnostic reports Setting kernel dump configuration Configuring SELinux Updating software Managing system subscriptions Installation of cockpit package.  [root@rhel8 ~] #  dnf   install cockpit cockpit-dashboard  -y  We need to enable the socket.  [root@rhel8 ~] #  systemctl enable --now cockpit.socket If firewall is runnin

Containers Without Docker on RHEL/Fedora

Docker is perfectly doing well with the containerization. Since docker uses the Server/Client architecture to run the containers. So, even if I am a client or developer who just wants to create a docker image from Dockerfile I need to start the docker daemon which of course generates some extra overhead on the machine.  Also, a daemon that needs to run on your system, and it needs to run with root privileges which might have certain security implications. Here now the solution is available where we do not need to start the daemon to create the containers. We can create the images and push them any of the repositories and images are fully compatible to run on any of the environment.  Podman is an open-source Linux tool for working with containers. That includes containers in registries such as docker.io and quay.io. let's start with the podman to manage the containers.  Install the package  [root@rhel8 ~] # dnf install podman -y  OR [root@rhel8 ~] # yum