- The Windows 2000\XP\.NET Resource Index
Home | About Us | Search

Last Updated December 16, 2003

Windows 2003
Windows 2000
Windows XP
Book Reviews
Career Tools
Device Drivers
Hardware Guides
MCSE Toolkit
  Where to Start
  Articles & Advice
  Book Reviews
  Certification News
  Cheap Study Guides
  Exam Prep Software
  MCSE Links
Exam Guides
  Exam 70-270
  Exam 70-210
  Exam 70-215
  Exam 70-216
  Exam 70-217
  Exam 70-218
  Exam 70-219
  Exam 70-220
  Exam 70-221
  Exam 70-222
Service Packs






Windows 2000 MCSE Exam 70-221:
Designing a Microsoft Windows 2000 Network Infrastructure

This certification exam tests the skills required to analyze the business requirements for a network infrastructure and design a network infrastructure that meets business requirements. Network infrastructure elements include: Network topology, Routing, IP addressing, Name resolution such as WINS and DNS, Virtual private networks, Remote access, and Telephony solutions
Exam Objectives:
Analyzing Business Requirements

Analyze the existing and planned business models.
  • Analyze the company model and the geographical scope. Models include regional, national, international, subsidiary, and branch offices.
  • Analyze company processes. Processes include information flow, communication flow, service and product life cycles, and decision-making.

Analyze the existing and planned organizational structures. Considerations include management model; company organization; vendor, partner, and customer relationships; and acquisition plans.

Analyze factors that influence company strategies.

  • Identify company priorities.
  • Identify the projected growth and growth strategy.
  • Identify relevant laws and regulations.
  • Identify the company's tolerance for risk.
  • Identify the total cost of operations.

Analyze the structure of IT management. Considerations include type of administration, such as centralized or decentralized; funding model; outsourcing; decision-making process, and change-management process.

Analyzing Technical Requirements

Evaluate the company's existing and planned technical environment and goals.

  • Analyze company size and user and resource distribution.
  • Assess the available connectivity between the geographic location of worksites and remote sites.
  • Assess net available bandwidth and latency issues.
  • Analyze performance, availability, and scalability requirements of services.
  • Analyze data and system access patterns.
  • Analyze network roles and responsibilities.
  • Analyze security considerations.
Analyze the impact of infrastructure design on the existing and planned technical environment.
  • Assess current applications.
  • Analyze network infrastructure, protocols, and hosts.
  • Evaluate network services.
  • Analyze TCP/IP infrastructure.
  • Assess current hardware.
  • Identify existing and planned upgrades and rollouts.
  • Analyze technical support structure.
  • Analyze existing and planned network and systems management.
Analyze the network requirements for client computer access.
  • Analyze end-user work needs.
  • Analyze end-user usage patterns.
Analyze the existing disaster recovery strategy for client computers, servers, and the network.

Designing a Windows 2000 Network Infrastructure

Modify and design a network topology.

Design a TCP/IP networking strategy.

  • Analyze IP subnet requirements.
  • Design a TCP/IP addressing and implementation plan.
  • Measure and optimize a TCP/IP infrastructure design.
  • Integrate software routing into existing networks.
  • Integrate TCP/IP with existing WAN requirements.
Design a DHCP strategy.
  • Integrate DHCP into a routed environment.
  • Integrate DHCP with Windows 2000.
  • Design a DHCP service for remote locations.
  • Measure and optimize a DHCP infrastructure design.
Design name resolution services.
  • Create an integrated DNS design.
  • Create a secure DNS design.
  • Create a highly available DNS design.
  • Measure and optimize a DNS infrastructure design.
  • Design a DNS deployment strategy.
  • Create a WINS design.
  • Create a secure WINS design.
  • Measure and optimize a WINS infrastructure design.
  • Design a WINS deployment strategy.
Design a multi-protocol strategy. Protocols include IPX/SPX and SNA.

Design a Distributed file system (Dfs) strategy.

  • Design the placement of a Dfs root.
  • Design a Dfs root replica strategy.

Designing for Internet Connectivity

Design an Internet and extranet access solution. Components of the solution could include proxy server, firewall, routing and remote access, Network Address Translation (NAT), connection sharing, web server, or mail server.

Design a load-balancing strategy.

Designing a Wide Area Network Infrastructure

Design an implementation strategy for dial-up remote access.

  • Design a remote access solution that uses Routing and Remote Access.
  • Integrate authentication with Remote Authentication Dial-In User Service (RADIUS).
Design a virtual private network (VPN) strategy.

Design a Routing and Remote Access routing solution to connect locations.

  • Design a demand-dial routing strategy.

Designing a Management and Implementation Strategy for Windows 2000 Networking
Design a strategy for monitoring and managing Windows 2000 network services. Services include global catalog, Lightweight Directory Access Protocol (LDAP) services, Certificate Services, DNS, DHCP, WINS, Routing and Remote Access, Proxy Server, and Dfs.

Design network services that support application architecture.

Design a plan for the interaction of Windows 2000 network services such as WINS, DHCP, and DNS.

Design a resource strategy.

  • Plan for the placement and management of resources.
  • Plan for growth.
  • Plan for Decentralized resources or centralized resources.

Entire contents
© 1999-2003 and TechTarget
All rights reserved

This site and its contents are Copyright 1999-2003 by Microsoft, NT, BackOffice, MCSE, and Windows are registered trademarks of Microsoft Corporation. Microsoft Corporation in no way endorses or is affiliated with The products referenced in this site are provided by parties other than makes no representations regarding either the products or any information about the products. Any questions, complaints, or claims regarding the products must be directed to the appropriate manufacturer or vendor.