1.Where are the communication between Exchange Servers and past and future versions of Exchange occurs?
The protocol layer. Cross-Layer communication isn’t allowed.
2.What services or infrastructure that Mailbox Servers contains?
- Mailbox servers contain the transport services that are used to route mail;
- Mailbox servers contain mailbox databases that process, render, and store data;
- Mailbox servers contain the Client Access services that accept client connections for all protocols;
- Mailbox servers contain the Unified Messaging services that provide voice mail and other telephony features to mailboxes (in Exchange 2016);
- We manage Mailbox servers by using the Exchange admin center (EAC) and the Exchange Management Shell.
3.What behaviors that Edge Transport Servers have?
- Edge Transport servers handle all external mail flow for the Exchange organization;
- Edge Transport servers are typically installed in the perimeter network, and are subscribed to the internal Exchange organization;
- Edge Transport servers provide antispam and mail flow rules as mail enters and leaves your Exchange organization;
- We manage Edge Transport servers by using the Exchange Management Shell.
4.What is database availability group?
A DAG is a group of Mailbox servers that host a set of databases and provides automatic, database-level recovery from database, network, and server failures.
5.What Transport high availability that Exchange Server provides?
- Shadow redundancy: The Transport service makes redundant copies of all messages in transit;
- Safety Net: The transport service makes redundant copies of all delivered messages;
- In Exchange Server, a DAG represents a transport high availability boundary. We can achieve site resilience by spanning a DAG across multiple Active Directory sites;
- Exchange Server attempts to guarantee message redundancy by keeping multiple copies of messages during and after delivery.
6.What is the exception while the clients communicating with the backend service on Mailbox Server?
In Exchange 2016, telephony requests are different than other client connections. Instead of proxying the request, telephony devices are required to establish their SIP and RTP sessions directly with the Unified Messaging services on the destination Exchange 2016 Mailbox server.