Why should resources be provisioned for production use rather than left at pilot sizing?
Select an answer to reveal the explanation.
Short Explanation
Production workloads analyze larger codebases and run more concurrent work. If you leave resources at pilot sizing, you'll see failures and timeouts that look like product defects.
Full Explanation
Production workloads analyze larger codebases and run more concurrent work, so pilot-sized resources produce failures and timeouts that look like product defects. Analysis and generation are resource-intensive, so a pilot-sized environment will not sustain a real codebase, producing failures whose cause is not obvious from the symptom.
Pilot-sized deployments being unsupported and refusing to start in production is incorrect because the platform runs; it simply performs badly. Resource size determining which product features are licensed is incorrect because feature availability follows licensing, not sizing. Provisioning being unchangeable after initial installation is incorrect because resources can be adjusted; the point is planning for the real workload.
For the exam, size for production workload rather than for the pilot.