What kind of information about your e-mail environment is not stored in DNS?
- Certificate expiration date
- SPF record
- DKIM selector
- MX
What kind of information about your e-mail environment is not stored in DNS?
Friday, February 7, 2020
From a hardware perspective what is the default paging file size requirements for Exchange 2019
From a hardware perspective what is the default paging file size requirements for Exchange 2019
- 75% of installed memory
- 25% of installed memory
- 10% of installed memory
- 50% of installed memory
EXPLANATION
When installing Exchange 2019 it is required to set the paging file size to 25% of the installed memory.SOURCE
https://docs.microsoft.com/en-us/exchange/plan-and-deploy/system-requirements?view=exchserver-2019Thursday, February 6, 2020
Which of these is NOT a type of intrusion detection system (IDS)?
Which of these is NOT a type of intrusion detection system (IDS)?
- Behavior-based
- Host-based
- Tunnel-based
- Network-based
EXPLANATION
Behavior-based IDS looks for variations in behavior, like unusually high traffic, policy violations,things like that. Deviations in behavior help it recognize potential threats. A network-based IDS examines all network traffic going to and from network systems. A host-based IDS refers to applications like spyware or virus applications that are installed on individual network systems and monitor for things like system file modifications or registry changes.
Tuesday, February 4, 2020
How many default receive connectors are there in Exchange 2013?
How many default receive connectors are there in Exchange 2013?
- 6
- 4
- 3
- 5
EXPLANATION
Default Receive connectors created during setup
Certain Receive connectors are created by default when you install the Mailbox server role.
Default Receive connectors created on a Mailbox server running the Transport service
When you install a Mailbox server running the Transport service, two
Receive connectors are created. No additional Receive connectors are
needed for typical operation, and in most cases the default Receive
connectors don't require a configuration change. These connectors are
the following:
Default <server name> Accepts connections from Mailbox servers running the Transport service and from Edge servers.
Client Proxy <server name> Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously mentioned, their TransportRole value is HubTransport.
To view the default Receive connectors and their parameter values, you can use the Get-ReceiveConnector cmdlet.
Default <server name> Accepts connections from Mailbox servers running the Transport service and from Edge servers.
Client Proxy <server name> Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously mentioned, their TransportRole value is HubTransport.
To view the default Receive connectors and their parameter values, you can use the Get-ReceiveConnector cmdlet.
Default Receive connectors created on a Front End Transport server
During installation, three Receive connectors are created on the
Front End transport, or Client Access server. The default Front End
Receive connector is configured to accept SMTP communications from all
IP address ranges. Additionally, there is a Receive connector that can
act as an outbound proxy for messages sent to the front-end server from
Mailbox servers. Finally, there is a secure Receive connector configured
to accept messages encrypted with Transport Layer Security (TLS). These
connectors are the following:
Default FrontEnd <server name> Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
Outbound Proxy Frontend <server name> Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
Client Frontend <server name> Accepts secure connections, with Transport Layer Security (TLS) applied.
In a typical installation, no additional Receive connectors are required.
Default FrontEnd <server name> Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
Outbound Proxy Frontend <server name> Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
Client Frontend <server name> Accepts secure connections, with Transport Layer Security (TLS) applied.
In a typical installation, no additional Receive connectors are required.
SOURCE
https://technet.microsoft.com/en-us/library/aa996395(v=exchg.150).aspxWhat is the output file extension once you have captured a machine using sysprep?
What is the output file extension once you have captured a machine using sysprep?
- .PKG
- .MSI
- .ESD
- .WIM
EXPLANATION
A captured image file is a .WIM.The .WIM holds a complete copy of your reference computer. The .WIM can be used to deploy a Windows image across a network using WDS.
