- Analyzing Business Requirements
- Analyzing Technical Requirements
- Designing a Windows 2000 Network Infrastructure
- Designing for Internet Connectivity
- Designing a Wide Area Network Infrastructure
- Designing a Management and Implementation Strategy for Windows 2000 Networking
- Passing the Exam
- Exam Resources
Designing a Windows 2000 Network Infrastructure
This objective is fun. You get to evaluate an organization's needs and then recommend how Windows 2000 can fulfill obligations. Approach this like the hotshot Windows 2000 guru you are, and you'll be fine.
Of course, a working grasp of TCP/IP is essential. You'll need to be able to create subnets based on the number of networks required and the number of clients needed on each network. This means subnetting, working in binary, and quickly calculating subnet masks. If you can't do this, learn it prior to shelling out 100 bucks.
You will need to know about Windows 2000's RRAS server, and what it can and can't do. For a small company, think RIP; for big companies think OSPF. Simply put, OSPF takes more time and know-how to configure, whereas RIP is pretty simple (but uses broadcasts to communicate). Your job is to determine when each is appropriate.
You need a way to assign IP addresses to users; this means DHCP servers. You need to know how to create, configure, and authorize DHCP servers in Active Directory. (Pay attention to authorizing DHCP in Active Directory.) Once again, know how to integrate DHCP with DNS for dynamic updates.
In some organizations, TCP/IP may be the only protocol on the entire network. But not the networks on this exam. You'll need to take into account NetWare and AS/400 servers, and what protocols and services are needed to interact with each.
Study Hint: Know how WINS servers push and pull resources to each other. Understand how to optimize the WINS infrastructure.