Professional Documents
Culture Documents
nment, such as a local area network (LAN). The responsibilities of the system ad
ministrator typically include installing and configuring system hardware and sof
tware, establishing and managing user accounts, upgrading software and performin
g backup and recovery tasks.
The main responsibilities performed by a system administrator are:
Active Directory management (adding and configuring new workstations and set
ting up user accounts to provide authorizations)
Installing and updating system software
OS patching/upgrades
Preventing the spread of viruses and malicious programs
Allocating mass storage space
Reviewing system logs
System security management
Creating a backup and recovery policy
Performance monitoring and optimization
Before facing any interview for a system administrator position, make sure that
you have enough knowledge on these technologies:
Basic Network Concepts:
Data communication and transmission techniques
Fundamentals of OSI and TCP/IP model
IP address classes
IP subnetting
IPv6 fundamentals
Basics of switching
Microsoft Server Functionalities:
Active Directory Domain Controller (Read only DC , Child DC)
Active Directory Domain Services
DHCP Server
DNS
File and print server
Database storage server
Windows Deployment Services (WDS)
Group Policy management
Registry management
Hyper V
Schedule tasks (Backup, AD DS Backup)
High Availability Features (Failover Clustering, Network Load Balancing)
Top Interview Questions for a System Administrator (Microsoft) Position:
All of the questions below are very common and must be prepared for before facin
g any interview for a System-Server Administrator position.
Q: What is Active Directory?
A: Active Directory provides a centralised control for network administration an
d security. Server computers configured with Active Directory are known as domai
n controllers. Active Directory stores all information and settings for a deploy
ment in a central database, and allows administrators to assign policies and dep
loy and update software.
Q: What is a Domain?
a Windows-based comp
central database. It
that authenticates u
policy for a Windows
cmd
When the backup process has finished you should get a message that the backup co
mpleted successfully. If it did not complete properly you will need to troublesh
oot.
The questions above are very tricky and important from the standpoint of clearin
g any interview for a System Administrator (Microsoft) position. It is not possi
ble for anyone to list every possible question, but you can get more frequently
asked interview questions for System/Server Administrator (Microsoft) Jobsfrom t
he download link posted here. If you find any difficulty in answering any questi
ons, ask me below @ the Comments section.
You are running an Exchange 2010 or newer exchange environment. You need to
make sure that if your mail box server that is hosting your mailbox database exp
eriences an outage, that users can still get to their mail without much issue. W
hat feature can you implement?
Why do you need AD with exchange?
--domain name systems
zones & forwarders
MS cornerstone for directory services / implementation of ldap
namespaces
locked = condition, disabled = administrative
managed service account or virtual account.
forest = different name spaces / made of tree's (made of domains)
domains & trust, right click, raise.
replication, domains & trusts
relationship of contextual inheritance (implicit, explicit, one way, transit
ive, etc)
schema, domain, pdc, inf - blah blah blah.
depending on the role - AD-Schema, Domains & Trusts, or Users & Computers
ntp
blah blah blah - how dns works
foward= name->ip rev= ip-> name A vs PTR
2012 promotes via role.
addressing
configuration of dhcp properties
network segment or AD-OU depending on topo
when it expires, reboots, or manual
broadcast - packet sniffer
static = manual assignment. reservation = set aside in dhcp. Depends on the
situation. Reservations = lower
think switch inside a switch. isolate broadcasts
either allow it on the ACL, configure routes, or put them all on the same tr
unk - depends where they terminate.
APIPA, fallback addressing, plug their cable in / get them a real address.
Hub, probably never these days. Switch, usually most of the time. Switch = h
igher end to end bandwidth.
802.1p / QOS
The place where your network is no longer really your network.
failover / redundancy, vtp, teaming and probably 3 other decent answers.
routing protocols - depends on where you want to use them... rip the inside,
bgp the wan, ospf your sites, eigrp if you've got all cisco gear and want to ge
t fancy.
combine 1 port to many ports.
dont plug it in there. put it on its own vlan, 802.1x, radius & nac
WPA2 enterprise the whole thing with client certificates and captive portals
.
stripe, mirror, parity, parity+1, nested raids - balance performance and rel
iability.
not my area of expertise.
0=0, 1=1, 5=1, 6=2, etc.
I dont do storage...
Storage... nope.
Performance & Archive states. (I do work with a lot of logging systems).
Thin = promise to pay. Thick = full allocation.
Replication = multiple copies, RAID = integrity, Snapshot = point in time, B
ack up = continuity.
Optical.
Temporary, Normal, Depends - who's cloud and why cant we just do it ourselve
s?
Basically, without going into how PKI works... it proves you are you you say
you are.
Ignoring the glaring flaws in this system, its the computer (organization) t
hat issues certificates
Root CA validates itself. Intermediates validate others chains.
When they expire, become compromised, and in accordance with your organizati
ons policy.
Lets skip this for now and assume we all know what PKI is. But basicaly - wh
en ever you want to protect the Confidentiality or Integrity of something in you
r network.
Self signed certs (unless you have your own root ca added to the store) wont
validate up the chain.
Slap your SA and tell him to add the cert to the trust store for the domain.
Instantiated compute environment.
Host = the thing running the VM. Guest = the VM itself.
Control the resource allocation and abstraction for the VM's.
Type 1 = bare metal (esx, xen, hyper-v) Type 2 = desktop virtualization (vmw
are, virtualbox)
VM's are all software = really fast deployment, really flexible, blah blah b
lah.
Fiber
Ummmm? repeat the question.
That you thin provisioned them and dont actually have the required storage.
You're runnning them on slow
Not enoguh info here... whats your protocol, whats your destination, lets ju
st say it leaves the client, hits the server, gets routed to the gateway, and se
nt on its way.
Get a barracuda. Dont run an open relay. Verify PTR's, Only accept mail that
follows strict protocol rules. Authenticate senders...
SPF record
Transport Layer Security & its all tied up in that PKI business we talked ab
out earlier.
HTTPS, HTTP, SMTP, other SMTP
I want to say it has soemthign to do with the transport setup... meh, not a
mail guy.
Because thats just how these things work.
------------------------------------