Which scenario is appropriate for using a Choice with Alias parameter?

• A. When letting users choose the output coordinate system.
• B. When letting users choose the Database Connection
• C. When defining a private value for destination format encoding
• D. When letting users choose a buffer distance in meters

Answer: (B)

A Choice with Alias parameter is used when you want to present user-friendly labels (aliases) for options that map to underlying, often more technical values or resources. This lets the user pick by a readable name while the workspace uses the actual internal reference behind the scenes.

The scenario of letting users choose the Database Connection is the best fit because database connections are defined in the workspace (potentially many of them) and each connection has a friendly alias. The parameter can show those aliases to the user, while the engine uses the actual connection details (strings, credentials, host, etc.) stored behind the alias. This keeps the interface clean and avoids exposing the raw connection data, and it also makes it easy to swap connections without changing the user-facing options.

Other options aren’t as appropriate for an alias-based choice. Choosing an output coordinate system can be handled with a straightforward list or code, but it doesn’t typically require alias mapping to an internal resource. Defining a private value for destination format encoding is usually a fixed internal setting rather than a user-facing resource to select by alias. A buffer distance in meters is a numeric value better served by a numeric parameter rather than a choice from aliases.