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 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.

SOURCE

https://technet.microsoft.com/en-us/library/aa996395(v=exchg.150).aspx

Read More

What 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.

SOURCE

https://en.wikipedia.org/wiki/Windows_Imaging_Format

Read More

In Microsoft Dynamics AX - what does a BOM stand for?

In Microsoft Dynamics AX - what does a BOM stand for?

• Bob Of Murrays
• Bill Of Materials
• Bill Of Manufacturing
• Building Off Memory 

QUESTION BY

bengarbutt in MICROSOFT DYNAMICS

EXPLANATION

The correct answer is Bill Of Materials.
This clarifies what components are needed in order to make an item beginning to end when manufacturing a product end-to-end.

SOURCE

https://docs.microsoft.com/en-us/dynamics365/supply-chain/production-control/bill-of-material-bom

Read More

On Linux, what is the output of: find . -print -mtime -10

On Linux, what is the output of: find . -print -mtime -10

• Only those files in & below the current directory with modification times greater than 10 days.
• Only those files in & below the current directory with modification times from exactly 10 days ago.
• Only those files in & below the current directory with modification times less than 10 minutes.
• All files found in & below the current directory. 

EXPLANATION

Expressions in "find" are evaluated left to right.  In the command given, "-print" is the first action in the expression, so each file found is printed.  Each file is evaluated against "-mtime -10", but no corresponding action follows the -mtime test.  Adding "-ls" to the end of the expression will make it clear, because those files with modification dates of less than 10 days will then be listed again, but in a different format.
Find and print everything below the current directory:

$ find  .  -print
.
./May
./May/file03
./May/file01
./May/file02
./May/file04
./June
./June/file03
./June/file01
./June/file02
./June/file04
./July
./July/file03
./July/file01
./July/file02
./July/file04

Test the "find" command, as given in the challenge:

$ find  .  -print  -mtime -10
.
./May
./May/file03
./May/file01
./May/file02
./May/file04
./June
./June/file03
./June/file01
./June/file02
./June/file04
./July
./July/file03
./July/file01
./July/file02
./July/file04

Append another action for the "find" command, "-ls", which will list  those files again that have modification times of less than 10 days:

$ find  .  -print  -mtime -10 -ls
.
2370731    4 drwxr-xr-x   5 dan      users        4096 Jul 14 21:11 .
./May
2506551    4 drwxr-xr-x   2 dan      users        4096 Jul 14 21:17 ./May
./May/file03
./May/file01
./May/file02
./May/file04
./June
2506552    4 drwxr-xr-x   2 dan      users        4096 Jul 14 21:18 ./June
./June/file03
./June/file01
./June/file02
./June/file04
./July
2506554    4 drwxr-xr-x   2 dan      users        4096 Jul 14 21:18 ./July
./July/file03
./July/file01
./July/file02
./July/file04

Understanding that the order of evaluation moves left to right is critical. If the specified action had been "-delete", instead of "-print", every file from the current directory down would have been deleted.
http://man7.org/linux/man-pages/man1/find.1.html
Warnings: Don't forget that the find command line is evaluated as an expression, so putting -delete first will make find try to delete everything below the starting points you specified.
See also:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/find.html
https://www.gnu.org/software/findutils/manual/html_node/find_html/find-Expressions.html#find-Expressions

SOURCE

http://man7.org/linux/man-pages/man1/find.1.html

Read More

On a Linux system, what is the output of " ls -si /tmp "

On a Linux system, what is the output of " ls -si /tmp "

• Human-readable sizes of names in /tmp using powers of 1000
• Index (inode) number of each name in /tmp, the allocated size in blocks of each name, and the name
• Human-readable size of names in /tmp using powers of 1024
• Names in /tmp sorted by inode number 

EXPLANATION

Most Linux utilities, including "ls", can be used with short options (prefixed with a single hyphen), or long options, (prefixed with two hyphens).  Some Linux utilities, like "tar" and "ps", do not require a prefix for short options.  Multiple short options may be combined following a single hyphen.
So the short option for size,  " -s ", may be combined with the short option for inode,  " -i ", as in 

ls -si  /tmp

Short options can be given in any order, but the order of the options does not affect the order of the output.
Long options (more than one character), are prefixed with two hyphens, as in

ls  --si  /tmp

The long option above, " --si ", is not the same as the combined short options, " -si ", and the long option, "--si",   will list the allocated block sizes of the names in /tmp in human-readable form using powers of 1000 (as opposed to 1024).

SOURCE

http://www.man7.org/linux/man-pages/man1/ls.1.html

Read More