Yes, and no.

Code:

file=/home/Config.*

will set file to /home/Config.* (not /home/Config.txt and not /home/Config.xml).

After setting file=/home/Config.*, [ -f "$file" ] won't match either file, but [ -f $file ] (without quotes) would be OK until /home/Config.txt.bak or /home/Config.xml.bak is created and then you'd get syntax errors from the test command when the expansion of the unquoted $file expands to two filenames. And, the common commands to create a backup file:

Code:

cp $file $file.bak

and:

Code:

cp $file "$file.bak"

would create a file named Config.*.bak; not Config.txt.bak and not Config.xml.bak. And, the more commonly used:

Code:

cp "$file" "$file.bak"

would fail with a file not found error.