How can administrators ensure security when using custom inputs?

Question

Options

• ABy using encrypted fields for sensitive data
• BBy disabling all user-defined inputs
• CBy restricting inputs to predefined lists only
• DBy enforcing static values for all provisioning processes

• A
  80% (41)
• B
  10% (5)
• C
  6% (3)
• D
  4% (2)

Explanation

Using encrypted fields for sensitive data (A) is the correct approach because it protects confidential information - like passwords, API keys, or tokens - from being exposed in logs, UI, or storage, while still allowing administrators the flexibility to accept custom input values securely.

Why the distractors are wrong:

• B is impractical and defeats the purpose of customization - blocking all user-defined inputs removes the flexibility administrators need to manage diverse environments.
• C is overly restrictive; predefined lists work for some inputs but can't cover all legitimate custom values, especially credentials or dynamic configuration data.
• D enforcing static values eliminates customization entirely, making provisioning inflexible and unable to adapt to different environments or use cases.

Memory tip: Think "sensitive = encrypt" - whenever an input might contain a secret, encryption is the security layer that lets you keep flexibility without losing protection. If an answer lets you do both, it's usually right over options that just eliminate the feature altogether.

No community discussion yet for this question.