MCP 70-665 Study Guide(Lync 2010 Admin exam)

* 아래 주소에서 70-665 시험에 대한 좋은 정보가 있어 인용했습니다.

ref url: http://designinglync.blogspot.com/p/study-guide-for-70-665-exam.html

 

 

70-665 Study Guide

This will be a living post as I seek out information covering the topics of the Lync Administrator exam, 70-665. Skills Being Measured This exam measures your ability to accomplish the technical tasks listed below. The percentages indicate the relative weight of each major topic area on the exam.

Designing a Topology for Lync Server 2010 (25 percent) Design address book. This objective may include but is not limited to: generation; distribution; filtering; normalization; size management Microsoft Documentation New Address Book Features PartitionByOU Replaced with msRTCSIP-GroupingID Administering the Address Book Service Address Book Server Cmdlets Address Book Capacity Planning Microsoft Lync Server 2010 Resource Kit Tool: ABSConfig Other Blogs Updating the Lync 2010 Address Book Forcing Lync Address Book Web Query Lync 2010 Address Book Normalization Address Book Server in Microsoft Lync Design central and branch office topology. This objective may include but is not limited to: designing sites and pools  placement of front-end servers  simple URLs  co-locating roles  designing browser-based access Director role capacity considerations Design mediation topology. This objective may include but is not limited to:  pooled Mediation Servers;  standalone mediation servers;  media bypass;  co-location with other front-end services; refer to Technet and Elan articles capacity considerations Design archiving and Quality of Experience (QoE) monitoring topology. - Deployment Guide This objective may include but is not limited to:  designing QoE monitoring;  placement of servers;  Call Detail Recording (CDR);  archiving policies Design Edge topology. This objective may include but is not limited to:  sizing, security, network, and capacity considerations;  deployment;  federation;  reverse proxy configuration;  XMPP;  PIC;  firewall requirements;  remote access Design Call Admission Control (CAC). This objective may include but is not limited to: sites; site links;  exemptions;  PSTN bypass;  rerouting;  CAC policies Calculate bandwidth. This objective may include but is not limited to:  specify network requirements;  calculate voice bandwidth;  calculate video bandwidth;  P2P vs. conference Designing a Conferencing and Enterprise Voice Infrastructure (25 percent) Design a dial plan. This objective may include but is not limited to:  formulate normalization rules and apply them as dial plan policies Design for voice routing. This objective may include but is not limited to:  PSTN breakout points;  PBX phones;  trunk routing; media gateway;  least cost/alternate routing Define voice policies. This objective may include but is not limited to:  phone usage records;  policy scope; decide level of access to certain features;  private line;  call parking Define conference policies. This objective may include but is not limited to:  controlling usage;  system capacity considerations Design for Response Group Services (RGS). This objective may include but is not limited to:  workflow; contact objects;  agents and queues;  groups Design for emergency services implementation. This objective may include but is not limited to:  Enhanced 911 (E911);  SIP trunk emergency service providers;  location policies;  Location Information Service (LIS) wiremap;  analyze network mapping Plan for devices. This objective may include but is not limited to:  considerations for different endpoint types, including analog devices, common area phones, and standalone devices;  DNS and DHCP requirements Planning for External Dependencies and Migration (24 percent) Plan for DNS implementation. This objective may include but is not limited to:  internal and external DNS;  identify supported DNS records;  identify supported DNS servers Plan for PKI requirements. This objective may include but is not limited to:  public and private certificates;  Subject Alternate Names (SANs) Plan for Exchange Unified Messaging (UM). This objective may include but is not limited to:  specify requirements to integrate Exchange UM with Lync Server 2010;  Exchange UM dependencies;  design Exchange UM dial plans Plan for migration. This objective may include but is not limited to:  configuration requirements;  side-by-side migration;  Edge migration;  meeting considerations;  client limitation considerations Planning for High Availability and Business Continuity (26 percent) Plan for high availability. This objective may include but is not limited to:  choosing Survivable Branch Appliance (SBA) vs. Standard vs. Enterprise in high availability;  number of servers and pools required;  server redundancy Plan for load balancing. This objective may include but is not limited to:  DNS;  Hardware Load Balancing (HLB) Plan for backup and restore. This objective may include but is not limited to:  partial recovery;  database considerations;  DBIMPEXP Plan for disaster recovery. This objective may include but is not limited to:  bare metal recovery;  spread pools;  CMS reactivation Plan for system monitoring. This objective may include but is not limited to:  synthetic transactions;  identifying components to monitor;  monitoring technologies such as Microsoft System Center Operations Manager Plan for site resiliency. This objective may include but is not limited to:  SBA;  backup registrar