Server sk0-005 Samplelesson
Server sk0-005 Samplelesson
CompTIA
Server+
Student Guide
(Exam SK0-005)
Acknowledgments
Notices
Disclaimer
While CompTIA, Inc. takes care to ensure the accuracy and quality of these materials, we cannot guarantee their accuracy,
and all materials are provided without any warranty whatsoever, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose. The use of screenshots, photographs of another entity's products, or
another entity's product name or service in this book is for editorial purposes only. No such use should be construed to imply
sponsorship or endorsement of the book by nor any affiliation of such entity with CompTIA. This courseware may contain links
to sites on the Internet that are owned and operated by third parties (the "External Sites"). CompTIA is not responsible for
the availability of, or the content located on or through, any External Site. Please contact CompTIA if you have any concerns
regarding such links or External Sites.
Trademark Notice
CompTIA®, Server+®, and the CompTIA logo are registered trademarks of CompTIA, Inc., in the U.S. and other countries.
All other product and service names used may be common law or registered trademarks of their respective proprietors.
Copyright Notice
Copyright © 2021 CompTIA, Inc. All rights reserved. Screenshots used for illustrative purposes are the property of the
software proprietor. Except as permitted under the Copyright Act of 1976, no part of this publication may be reproduced
or distributed in any form or by any means, or stored in a database or retrieval system, without the prior written permission
of CompTIA, 3500 Lacey Road, Suite 100, Downers Grove, IL 60515-5439.
This book conveys no rights in the software or other products about which it was written; all use or licensing of such
software or other products is the responsibility of the user according to terms and conditions of the owner. If you believe
that this book, related materials, or any other CompTIA materials are being reproduced or transmitted without permission,
please call 1-866-835-8020 or visit https://help.comptia.org.
Table of Contents
Table of Contents
Solutions......................................................................................................................... S-1
Glossary ..........................................................................................................................G-1
Table of Contents
Course Description
Course Objectives
This course can benefit you in two ways. If you intend to pass the CompTIA Server+
(Exam SK0-005) certification examination, this course can be a significant part of
your preparation. But certification is not the only key to professional success in
the field of server management. Today's job market demands individuals with
demonstrable skills, and the information and activities in this course can help you
build your sysadmin skill set so that you can confidently perform your duties in any
entry-level server administration role.
On course completion, you will be able to achieve the following:
• Understand server administration concepts.
• Decommission servers.
Target Student
The Official CompTIA Server+ Guide (Exam SK0-005) is the primary course you will
need to take if your job responsibilities include server administration, installation,
and security within your organization. You can take this course to prepare for the
CompTIA Server+ (Exam SK0-005) certification examination.
Prerequisites
To ensure your success in this course, you should have basic IT skills comprising
18 months to two years' experience. CompTIA A+ certification, or the equivalent
knowledge, is strongly recommended.
The prerequisites for this course might differ significantly from the prerequisites for
the CompTIA certification exams. For the most up-to-date information about the exam
prerequisites, complete the form on this page: www.comptia.org/training/resources/
exam-objectives
As You Learn
At the top level, this course is divided into Lessons, each representing an area of
competency within the target job roles. Each Lesson is composed of a number of
Topics. A Topic contains subjects that are related to a discrete job task, mapped
to objectives and content examples in the CompTIA exam objectives document.
Rather than follow the exam domains and objectives sequence, Lessons and
Topics are arranged in order of increasing proficiency. Each Topic is intended
to be studied within a short period (typically 30 minutes at most). Each Topic
is concluded by one or more Activities, designed to help you to apply your
understanding of the study notes to practical scenarios and tasks.
In addition to the study content in the Lessons, there is a glossary of the terms and
concepts used throughout the course. There is also an index to assist in locating
particular terminology, concepts, technologies, and tasks within the Lesson and
topic content.
In many electronic versions of the book, you can click links on key words in the Topic
content to move to the associated glossary definition and on page references in
the index to move to that term in the content. To return to the previous location in
the document after clicking a link, use the appropriate functionality in your eBook
viewing software.
As You Review
Any method of instruction is only as effective as the time and effort you, the
student, are willing to invest in it. In addition, some of the information that you
learn in class may not be important to you immediately, but it may become
important later. For this reason, we encourage you to spend some time reviewing
the content of the course after your time in the classroom.
After the lesson content, you will find a table mapping the Lessons and Topics
to the exam domains, objectives, and content examples. You can use this as a
checklist as you prepare to take the exam, and review any content that you are
uncertain about.
As a Reference
The organization and layout of this book make it an easy-to-use resource for future
reference. Guidelines can be used during class and as after-class references when
you're back on the job and need to refresh your understanding. Taking advantage
of the glossary, index, and table of contents, you can use this book as a first source
of definitions, background information, and summaries.
LESSON INTRODUCTION
In order to effectively manage servers in an enterprise environment, you must
understand the role of the systems administrator (sysadmin). You must also
understand the differences between servers and workstations and how to manage
the server lifecycle. Troubleshooting is a key skill for sysadmins. A troubleshooting
methodology will make it more efficient to address server and network issues. Finally,
in this lesson, you will learn about licensing models and compare open source and
proprietary software licenses.
Lesson Objectives
In this lesson, you will:
• Understand server administration concepts.
• Manage licenses.
Topic 1A
Understand Server
Administration Concepts
• Troubleshooting
• Working with other information technology (IT) teams, possibly including the
service desk, developers, desktop support
• Providing documentation
Take a few minutes to research the job descriptions and requirements for several server
administrator jobs to discover a list of common responsibilities.
• College degree
• Years of experience
Take a few minutes to research the education and certification requirements for several
server administrator jobs.
Server Lifecycle
Server administrators are responsible for the lifecycle of the server. The term
"lifecycle" normally specifies four phases: procurement, usage, end of life, and
disposal/recycling. These phases are covered in more detail later in the course.
At this stage, it useful for you to recognize that the server administrator's role
is to maintain the server through its lifecycle.
• Memory—the RAM represents storage capacity available to the CPU for quick
access to data.
Linux
Linux is actually a very big family of related OSs. Each version of Linux is referred
to as a "distribution" (or "distro"). Each distribution is typically purpose specific.
For example, Red Hat Enterprise Linux (RHEL) is designed to be used in a large-
scale business deployment. Kali Linux is designed to be used in penetration
testing situations.
Linux is licensed under the General Public License (GPL) and is an open-source OS.
That means that the source code that makes up the OS is available to anyone to be
modified and redistributed. The Linux OS is available for free download.
Most Linux distributions trace their lineage back to either Debian Linux or Red Hat
Linux. The primary difference between the two branches of the Linux family is how
software is managed.
• Fedora
• CentOS
• Ubuntu
• Kali
Two common areas of consideration for choosing between Linux and Windows Server
OSs are device driver compatibility and software availability.
Windows Server
The Microsoft Windows Server OS is very common and is closely related to the
Windows desktop OSs. Windows Server is designed to be used in a business setting
to provide centralized administration.
Windows is a closed-source OS. That means that the source code that makes up
the OS is not available to be modified or redistributed. The Windows Server OS is
available for purchase from Microsoft or resellers.
Review Activity:
Server Administration Concepts
Answer the following questions:
6. What are the two main branches of the Linux family of distributions?
Topic 1B
Understand Troubleshooting Methods
Troubleshooting Methodology
A formalized and consistent troubleshooting methodology can make identifying
issues and discovering fixes more efficient. While the steps can vary depending
on the actual issue and components involved, there are several universal
troubleshooting steps.
The following list represents the basic steps in a troubleshooting methodology:
• Identify the problem
Note: In Linux, the log file service is named "rsyslog." In Windows, the log file service is
named "Event Viewer."
Some service desk management software requires the use of tickets. Such software may
require that troubleshooting documentation be entered before the ticket can be closed.
Review Activity:
Discuss a Troubleshooting
Methodology
Answer the following questions:
3. The service desk escalates a ticket to you that indicates a user cannot
access any network servers or any websites. While troubleshooting,
you ask several employees near the user whether they can access the
network servers and websites. Those users all indicate that they can
access the requested resources. You have now determined that only
one user is experiencing issues. Which step of the troubleshooting
methodology are you applying?
Topic 1C
Manage Licenses
Proprietary—a licensing model where the source code for the software is hidden,
and users are not allowed to freely modify and rerelease the software. Proprietary
software may also have an associated purchase cost. Proprietary licenses may be
subscription or volume based.
• Not free to use
While FOSS does not require a formal license, many vendors utilize a subscription
service to maintain the OS or software. Red Hat, for example, has a subscription
service associated with RHEL8.
Licensing Models
There are many different license models. Licensing varies between on-premises and
cloud solutions, OSs, applications, virtualization technologies, and even number of
users. The following list is a summary of some common license types:
• Subscription—a license that permits the use of software hosted in the cloud.
Subscription licenses are billed yearly or monthly. They may include support
costs as part of the subscription.
• Volume licensing—a single license that covers a specified number of installations
for the convenience of large businesses. This model simplifies the license
management process.
• Per-instance—one license for each instance of the software installed. If you run
twenty copies of the software, you will need twenty licenses.
• Per-concurrent-user—one license for each software instance in use by a user.
This is typically less expensive than per-seat licensing. If your organization has
ten of these licenses, and there are twenty copies of the software installed, then
only ten users may use the software simultaneously.
• Per-seat license—one license for each potential user of the software. This is
typically more expensive than per-concurrent-user licensing.
• Per-server—client access licenses (CALs) installed on the server. The number
of licenses determines the number of simultaneous connections that clients
may make to the server. A server with ten per-server CALs will permit up to ten
simultaneous client connections.
• Per-socket—licenses allocated to each processor socket that is enabled on the
server’s motherboard. It is important to note that the motherboard may contain
more sockets than are licensed, but the extra sockets are disabled.
• Per-core—licenses allocated to each processor core that is enabled on the CPU.
It is important to note that the CPU may contain more cores than are licensed,
but the extra cores are disabled.
• Site-based—licenses that permit the installation of software within a specified
site, building, or organization.
• Node-locked—licenses stored on a single node or on a Universal Serial Bus (USB)
dongle, and any number of instances of the software may run on that node. The
goal is to permit the software to run only on one computer.
• Physical vs. virtual—not all licenses apply the same way between physical
installations on a server and installations that are done on VMs. You need to
further investigate the licenses when dealing with VMs.
Electronic Signatures
In many cases, you may be required to provide a digital signature or e-signature
acknowledging a license agreement. Organizations such as DocuSign provide
electronic signing options for licenses, contacts, and other legal agreements.
The digital signatures referenced in this section are not the same thing as the digital
signature function found with the Public Key Infrastructure. In this case, the focus is
on signatures for legal documents.
Version Compatibility
Licenses may permit users to use a specified software version and any version
previous to that one. For example, a current software license for version three of
a software package might also enable the use of versions one and two. This is an
example of license backward compatibility. Licenses that are forward compatible
permit the use of the current software version and one or more future releases of
the software.
As a systems administrator, you must understand the license requirements for OSs
and software to ensure that your organization remains compliant. There can be
legal and financial penalties for failing to maintain proper licensing.
• Remember that proprietary licensing does not permit modification of the source
code.
• Understand the licensing methods, and recognize that a vendor may offer
several license models.
Review Activity:
Licenses
Answer the following question:
3. You are a systems administrator, and you are responsible for managing the
licenses for a piece of cloud-based software. Currently, you have 100 users
that access the software. Your organization is billed monthly for these
users. Your organization hires an additional 50 users who also need access.
You increase your licenses by using a web-based management tool. You
also notice that the vendor has automatically given your users access to
the newly released 2.0 version of the software. This is an example of what
kind of licensing?
4. You are systems administrator, and you are responsible for managing
the license for a piece of server-based software. The software license
requires you to pay based on the number of physical CPUs enabled on
the server’s motherboard. This is an example of what kind of license?
Lesson 1
Summary
Systems administrators have a broad range of responsibilities. The sysadmin's
role includes understanding the server's place in the network as a component
that provides services to end-user workstations or remote clients and requires
a high degree of security. Effectively troubleshooting servers calls for a reliable
troubleshooting methodology that quickly narrows the scope of the problem and
helps to prevent future issues. Sysadmins are also responsible for licensing, which
can become complex very quickly. Frequently, server environments rely on a mix of
proprietary licenses, as with Microsoft Windows Server, and open-source licenses,
aswith Linux distributions, such as RHEL or Ubuntu.
1. Compare and contrast proprietary licensing versus open source. What
are the benefits and drawbacks of each?