What is the purpose of using a custom form?

Question

Options

• ATo customize Service Broker and enhance the user interface
• BTo customize the Cloud Assembly user interface
• CTo customize the input parameters and enhance a request form
• DTo customize a blueprint to enable guest customization

• A
  6% (1)
• C
  94% (15)

Explanation

Custom forms exist specifically to let administrators control what input fields appear when a user submits a request - they modify, hide, reorder, or add constraints to those input parameters, making the request experience cleaner and more tailored. Option A is wrong because Service Broker's overall UI customization goes beyond what a custom form does - a form targets the request dialog, not the broker interface broadly. Option B is wrong because Cloud Assembly is the design/blueprint environment, and its UI is not what custom forms are meant to alter. Option D is wrong because guest customization (OS-level personalization like hostname and credentials) is a blueprint-level setting, not a form concern.

Memory tip: Think of a custom form as the front desk intake sheet - it controls exactly what questions a requester must answer before their order is processed, nothing more, nothing less.

No community discussion yet for this question.