156-561 · Question #130
Which deployment methods are allowed on Azure?
The correct answer is B. Single Gateway, Cluster, Auto-Scale. Option B is correct because Azure supports all three deployment methods: Single Gateway (a single instance for basic workloads), Cluster (multiple instances for high availability and load distribution), and Auto-Scale (dynamic scaling based on demand). Together, these cover the…
Question
Which deployment methods are allowed on Azure?
Options
- AAuto-scale, Single Gateway
- BSingle Gateway, Cluster, Auto-Scale
- CCluster, Auto-scale
- DSingle Gateway, Cluster
How the community answered
(25 responses)- B92% (23)
- C4% (1)
- D4% (1)
Explanation
Option B is correct because Azure supports all three deployment methods: Single Gateway (a single instance for basic workloads), Cluster (multiple instances for high availability and load distribution), and Auto-Scale (dynamic scaling based on demand). Together, these cover the full spectrum of Azure deployment flexibility.
Why the distractors are wrong:
- A (Auto-scale, Single Gateway) omits Cluster, which is a fully supported and commonly used Azure deployment method.
- C (Cluster, Auto-scale) omits Single Gateway, which is a valid basic deployment option in Azure.
- D (Single Gateway, Cluster) omits Auto-Scale, which is one of Azure's core capabilities for elastic workloads.
Memory tip: Think "SCA" - Single Gateway, Cluster, Auto-Scale. All three form a progression from simplest to most dynamic, and Azure supports the entire spectrum - so when in doubt, the answer that includes all three is correct.
Topics
Community Discussion
4B is correct. Azure supports all three deployment methods, Single Gateway, Cluster, and Auto-Scale, giving you the full range of options whether you need a simple setup, high availability, or dynamic scaling based on load.
Worth adding that each of those three deployment types lands in SmartConsole as a different object class, so before you push policy make sure your session is not holding a stale lock on a gateway object from a prior topology, or the Auto-Scale group will install fine while your cluster object silently skips the push.
I was leaning toward D because I kept confusing Azure's deployment options with the on-prem ones where auto-scale felt like an add-on that wasn't always listed, but the Azure documentation is clear that all three methods, Single Gateway, Cluster, and Auto-Scale, are supported deployment options on that platform. Once I stopped mixing up my study notes from the on-prem section and focused strictly on Azure, B was the only answer that made sense.
Thought D, then remembered Azure explicitly supports all three: Single Gateway, Cluster, and Auto-Scale.