A customer plans to pick a deployment topology straight from the platform's default template rather than designing one. Why is that risky?
Select an answer to reveal the explanation.
Short Explanation
A default template is someone else's guess at a typical workload. Yours might not be typical, so check it against your real availability, latency, and integration needs before you accept it.
Full Explanation
The correct answer is the generic-case template warning. Templates are built to be broadly reasonable, not tailored, so a workload with tighter latency needs, higher availability targets, or specific integration needs can be under-served if the default is picked without checking it against requirements. The deprecated-support claim is wrong because support status is not the concern raised here. The once-per-organisation claim is wrong because template reuse is not restricted in this way. The separate-licence claim is wrong because licensing is unrelated to whether a template fits the workload. For the exam, validate any default against the stated requirements before accepting it.