Question 570
A form shows a friendly label for a choice field but an import sends an unknown underlying choice value. Which configuration or administrative response BEST addresses the primary issue?
Explanation
Correct Answer
Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage. Dictionary settings define schema characteristics that can affect many views and integrations; changing a label does not change the stored data type. Verify prerequisites with: Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.
Incorrect Answers
Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever. This approach instead addresses Security Center evidence and posture exception control. Accepting a known exception is a governance decision, not evidence the security configuration meets the baseline. The targeted response is: Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.
Investigate failed or duplicated event-driven notifications by correlating the generated event with notification conditions and outbound delivery logs. This approach instead addresses Event-driven messaging and notification diagnostics. Event creation, notification evaluation, and email delivery are separate lifecycle stages; a queued event is not proof a message reached its user. The targeted response is: Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.
Improve CMDB trust using health checks and source remediation for duplicate, stale or incomplete CI data rather than presenting a dashboard score as proof of accurate dependencies. This approach instead addresses CMDB health completeness correctness and relationship audits. A CMDB health score is only as meaningful as the selected rules and data sources; dashboards alone do not repair faulty CI relationships. The targeted response is: Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.


