Sunday, January 31, 2010

Exchange Server 2003 Interview Questions and Answers - 3

This chapter contains the Interview Question and answers on Exchange Server 2003 permissions, Modes of Exchange Server 2003 and Exchange Server 2003 Clustering.

1. What types of permissions are configurable for Exchange?

  • Exchange full admin – full control over the exchange organization including permission

  • Exchange Admin – Manage everything within the organization except org permission.

  • Exchange view only administrator – read only administrative access to Exchange organization


2. Which of the privileges does the Exchange Administrator role have?

This Role has the ability to administer all configuration details of the Exchange organization and ability to modify permission

3. What are the modes of Exchange Server 2003?

There are two modes in Exchange server 2003

1. Mixed Mode – If Exchange 5.5 exists and in future gain to have Exchange 5.5

2. Native Mode – if only Exchange server 2003 running in your organization

4. What are the benefits of running Exchange Server 2003 in native, rather than mixed mode?

There are lot of benefits which includes,

  1. Greater flexibility for defining routing groups and Administrative groups

  2. Ability to move mailboxes

  3. Configure both routing and administrative groups independent of each other

  4. We can create query base distribution group


5. When Exchange Server 2003 Mixed mode is used?

By default exchange server in Mixed mode, we can have mixed mode in situation where Exchange server 5.5 situated in our Exchange organization. Mixed modes are used to have backward compatibility with Exchange server 5.5 and sites

6. When Exchange Server 2003 Native mode is used?

We can choose this option if No Exchange server 5.5 present in our Exchange organization and make sure that all the exchange servers are Exchange server 2000 and Exchange server 2003. Native mode allows administrative groups and Routing Groups to be configured independent of each other

7. Can you switch Exchange Organization from native mode to mixed mode?

yes we can change Exchange organization from Mixed mode to Native mode and changing the mode form Mixed to Native is onetime, one way process and it cannot be reversed

8. How to switch Exchange Organization from mixed mode to native mode?

We can accomplish this by Exchange system Manager, by right clicking the Exchange organization name at the top of the window and click properties. On the New window click the change Mode option. This changed mode option will be unavailable if you are already in Native mode.

9. Which service needs to be restarted on all Exchange Server 2003 systems within the domain once you have switched to native mode?

If you Know the answer, please help to Me publish

10. What is Clustering?

It’s a technique for providing hardware and software redundancy for an application like exchange server 2003, with clustering you can ensure there is no single point of failure with your server hardware that would results in email services going offline. Clustering allows you to bring one node for maintenance by allowing other nodes to continue functioning.

11. What is Network Load balancing?

It is a resource (server-aware) clustering technology. Primary purpose to load balance by distributing the TCP/IP traffic among each server node in cluster. To client computers, the cluster is seen as a single resource and is address by a single IP

12. What are the advantages and disadvantages of Network Load Balancing?

Advantages

  • No special hardware required

  • Cluster can use different operating system

  • Clusters are to be member of domain or perimeter


Disadvantages

  • NLB uses hear beat to communicate between cluster, if a server goes offline. It sent 5 heart beats and if no response and if client if a client is requesting a request then it neglect the request

  • Work only with TCP/IP. It will not consider network link protocol


13. What is Failover?

Its related to cluster servers, it refers to the ability to of a backup server to immediate begin servicing requests if a primary server fails, without an interruption in servicing user request

14. When Failover occurs?

Failover occurs when a primary server fails to function, this failback automatically process the service request to secondary servers which is already clustered.

15. What is Failback?

Fail back defines how failed over application services are moved back to original server node, once the node is back online

16. How Failback occurs?

By default, cluster groups that failover to another node do not automatically failback. In Failback policy we can configure the allow failback option to take place immediately or over a certain period

To make a failback occur, we have to create a failback policy to occur immediately or over a certain period

17. What are the different clustering options in Exchange 2003?

Exchange server 2003 supports two types of clustering option which is already supported by windows server 2003

1. Network Load balancing – server aware clustering technology , load balance by distributing the TCP/IP traffic among each server node in cluster. To client computers, the cluster is seen as a single resource and is address by a single IP

2. Cluster service – application or service aware clustering technology, provides continual application service availability through failover and failback

18. Name the exchange server 2003 clustering configuring option

Single node server cluster – can be configured with or without external cluster storage device. For this clusters without an external storage device, the local disk in configured as the clustered storage device

Single Quorum device server cluster – have two or more nodes and are configured so that every node is shared to one or more shared devices. Cluster configuration is stored in single cluster storage device, known as quorum device.

Majority node set server cluster – have two or more node and are may or may not be attached to one or more cluster storage devices. Cluster configuration data is stored on multiple disks across the cluster

19. Which service pack is required for installing Exchange Server 2003 Clustering on Windows 2000 Server?

Windows 2000 server SP4 is needed

20. Why SP4 is needed for Windows 2000 server for Exchange Clustering?

If you Know the answer, please help to Me publish

21. How many nodes are supported with Exchange Server 2003 clusters?

Exchange Server 2003 supports Two Node active/active clusters and up to eight-node active/passive clusters with at least one passive node

22. What are the hardware requirements for a cluster server configuration?
Network components


  1. Each server node the cluster has two static IP address ( public or private) with one net bios name

  2. The cluster itself has a primary static IP and NETBIOS Name

  3. Each exchange virtual servers have a static IP and NETBIOS Name


Disk Components

1. Quorum Disk resource - maintains configuration data.

For Example: For a 4 Node cluster
Server hardware


  • Four 1 gigahertz (GHz), 1 megabyte (MB) or 2 MB L2 cache processors

  • 4 gigabytes (GB) of Error Correction Code (ECC) RAM

  • Two 100 megabits per second (Mbps) or 1000 Mbps network interface cards

  • RAID-1 array with two internal disks for the Windows Server 2003 and Exchange Server 2003 program files

  • Two redundant 64-bit fiber Host Bus Adapters (HBAs) to connect to the Storage Area Network


Local area network hardware


  • Two 100 Mbps or 1000 Mbps network switches (full duplex)


Storage Area Network hardware


  • Redundant fiber switches

  • 106 disk spindles (Ultra Wide SCSI) with spindle speeds of 10,000 RPM or greater

  • 256 MB or more read/write cache memory


Storage groups and databases


  • Three storage groups per Exchange Virtual Server

  • Five databases per storage group


23. What is purpose of Exchange Server Clustering?

The purpose of Exchange Server Clustering is to prevent the Exchange server from going offline.

24. What is the version of Windows Server 2003 required for Exchange Server 2003 Clustering?

The cluster service requires windows server 2003 enterprise edition or windows server 2003 Datacenter edition. Up to eight node clusters are supported

25. What is Heartbeat?

Heart beat is a special type of network packet that is sent out to each server node participating in a cluster to determine the responsiveness of a node. Server nodes that do not respond to heart beat packets for a configurable period of time are marked a inactive

26. What are the different numbers of nodes with different type of operating system for Exchange Server 2003?

Windows server 2003 standard edition supports 4 nodes

Windows server 2003 enterprise edition or windows server 2003 Datacenter edition supports up to eight node clusters

27. What are the different cluster models?

Two types of cluster models are there

  1. Active/Active – limited to two nodes and both the nodes are active at the same time, limited to 1900 concurrent client connection at a time

  2. Active/Passive – supports more than two nodes and highly reliable. Recommended by Microsoft.


28. Which are the Cluster operations modes?

N-Node failover server pairs – applications are configured to failover only between two specified server pairs

N+I Hot-Standby Server – commonly referred to as active/passive mode, on two node cluster, one node process the client request and the second node monitors the first node. where N – Active node, I - Passive Node

Fail over Ring - Active/Active – all servers are active and process the client request, when one node fails the cluster, failover the cluster to another active node. Administrator has to define the failover

Random Failover – similar to failover ring, if a node fails the failover is randomly changed to active node. The Administrative burden of having a define failover is removed

29. What is teaming?

Teaming is the process included in clustering service, where multiple adapters are joined through software to function as a single unit, with a single MAC address and single IP address

30. Which settings must be configured for failover policies?

We can configure the number the times the node to failover (Threshold) during the period, which is defined in hours

31. Which settings must be configured for failback policies?

By default, cluster groups that failover to another node do not automatically failback. In Failback policy we can configure the allow failback option to take place immediately or over a certain period

No comments:

Post a Comment