Not via the deployment scanner, no.
You can upload a deployment to the server via the CLI but not have it deployed though:
[standalone@localhost:9999 /] deploy ~/tmp/helloworld.war --disabled
[standalone@localhost:9999 /] cd deployment=helloworld.war
[standalone@localhost:9999 deployment=helloworld.war] ls -l
ATTRIBUTE VALUE TYPE
content [{"hash" => bytes { 0x6f, 0xcd, 0x9e, 0xae, 0x34, 0x3e, 0xd6, 0xd5, 0xaa, 0x9f, 0xff, 0xa8, 0x30, 0x12, 0xd1, 0x55, 0xb1, 0xef, 0x91, 0x1c }}] LIST
enabled false BOOLEAN
name helloworld.war STRING
persistent true BOOLEAN
runtime-name helloworld.war STRING
status STOPPED STRING
CHILD MIN-OCCURS MAX-OCCURS
subdeployment n/a n/a
subsystem n/a n/a
Note the "enabled" attribute.
Later you could use the CLI to trigger the deployment:
[standalone@localhost:9999 deployment=helloworld.war] deploy --name=helloworld.war
[standalone@localhost:9999 deployment=helloworld.war] ls -l
ATTRIBUTE VALUE TYPE
content [{"hash" => bytes { 0x6f, 0xcd, 0x9e, 0xae, 0x34, 0x3e, 0xd6, 0xd5, 0xaa, 0x9f, 0xff, 0xa8, 0x30, 0x12, 0xd1, 0x55, 0xb1, 0xef, 0x91, 0x1c }}] LIST
enabled true BOOLEAN
name helloworld.war STRING
persistent true BOOLEAN
runtime-name helloworld.war STRING
status OK STRING
CHILD MIN-OCCURS MAX-OCCURS
subdeployment n/a n/a
subsystem n/a n/a