Question 50
A solution was implemented for this need: A business needs numeric MarginPct rather than a text field containing '25%'. The selected approach was: Strip or parse the percent representation with the correct locale and set a numeric Percentage-compatible type. Which result most directly proves it worked?
Explanation
Correct Answer
This checks the actual result rather than a saved setting. Analytical percentage fields need numeric storage with appropriate presentation formatting. A failed implementation may show: Leaving percentages as text causes lexical sorting and invalid numeric aggregations.
Incorrect Answers
Sample dates match the source agreement and downstream monthly aggregations reconcile. However, this does not establish the required outcome: marginPct can be aggregated or compared numerically and 25% evaluates as 0.25.
FirstName and LastName are populated in the agreed order without leading spaces. However, this does not establish the required outcome: marginPct can be aggregated or compared numerically and 25% evaluates as 0.25.
Cloud refresh continues even when the analyst's laptop and synced drive are offline. However, this does not establish the required outcome: marginPct can be aggregated or compared numerically and 25% evaluates as 0.25.