Designing Highly Available Web Solns

MCSE Video + 10 Free Vouchers

Practice Exams

CISSP

CCNP

MORE...

EXAMS: WHAT TO KNOW

Designing Highly Available Web Solns - What to Know

Email this Article

Print this Article

• Relates to: MCSE 2000

This certification exam measures your ability to design Web solutions that incorporate Microsoft Windows 2000 Server technologies.

Please note: This is a design-based exam. You will have to know the technology AND know how to implement it in a design-based scenario. Make sure you are familiar with the objectives below.

Before taking the exam, you should be proficient in the job skills listed below:

Design NLB solutions to improve availability, scalability, and fault tolerance. Considerations include the number of hosts, number of clusters, placement of servers, multicast versus unicast, failover strategy, priority, affinity, filtering, load weighting, and application types
Design Cluster service cluster solutions to improve fault tolerance. Considerations include the number of nodes, placement of servers, cluster resource groups, failover and failback strategy, active/active, active/passive, application types, and dependencies
Design CLB solutions to provide redundancy and load balancing of COM+ components. Considerations include the number of nodes, placement of servers, NLB, and CLB routing
Design data storage for high availability. Considerations include RAID and storage area networks.
Design a system management and monitoring strategy. Considerations include performance monitoring, event monitoring, services, data analysis, and WMI.
Design a disaster recovery strategy.
Design a TCP/IP network infrastructure. Considerations include subnet addressing, DNS hierarchy and naming, DHCP server environment, and routed and switched environments.
Design a highly available network topology. Considerations include redundant paths, redundant services, and redundant components.
Plan server configurations. Considerations include network adapters, cluster communication, connectivity, and bandwidth.
Calculate network, server, and cluster capacity. Considerations include memory, CPU, cost, flexibility, manageability, application scalability, and client/server and server/server communications.
Design an upgrade strategy for networks, servers, and clusters. Considerations include scaling up and scaling out
Calculate storage requirements. Considerations include placement, RAID level, and redundancy.
Design directory services. Considerations include Active Directory, LDAP, availability, authentication, and sizing.
Design an authentication strategy. Considerations include certificates, anonymous access, directory services, Kerberos, and public key infrastructure (PKI).
Design an authorization strategy. Considerations include group membership, IP blocking, access control lists, and Web content zones.
Design an encryption strategy. Considerations include IPSec, SSL, certificates, Encrypting File System (EFS), and PPTP.
Design a firewall strategy. Considerations include packet filters, proxy servers, protocol settings, network address translation (NAT), and perimeter networks (also known as DMZs).
Design a security auditing strategy. Considerations include intrusion detection, security, performance, and denial of service, logging, and data risk assessments.
Design a Microsoft Exchange 2000 Server messaging Web integration strategy. Considerations include browser access and Wireless Access Protocol (WAP) gateways.
Design a database Web integration strategy. Considerations include database access and authentication.
Design content and application topology. Considerations include scaling out, load balancing, fault tolerance, deploying and synchronizing Web applications, state management, service placement, and log shipping
Design an n-tier, component-based topology. Considerations include component placement and CLB
Design an application management and monitoring strategy. Considerations include detection and notification of application failure