Question 50A project links service requests to employees by copying each employee's display name into a text field. If no correction is made, which avoidable consequence follows most directly? Fixed repeated columns cap growth and complicate access controls. Free-text names can become stale or ambiguous. String comparisons can misorder dates and undermine time calculations. Static labels can misidentify the authoritative asset. ExplanationCorrect Answer B:Free-text names can become stale or ambiguous. Reference relationships preserve record identity independent of display-name changes. The preventive measure is: Create a reference field to the authoritative user record.Incorrect Answers A:Relational cardinality should be represented with flexible child records. This is not the primary failure in the question. The direct unmitigated outcome here is: Free-text names can become stale or ambiguous. C:Dictionary field types provide consistent storage and comparison behavior. This is not the primary failure in the question. The direct unmitigated outcome here is: Free-text names can become stale or ambiguous. D:A reference stores the record relationship, while the display value is presentation. This is not the primary failure in the question. The direct unmitigated outcome here is: Free-text names can become stale or ambiguous.
Question 51An app owner opens cross-scope read access for every external application to solve one integration failure. If no correction is made, which avoidable consequence follows most directly? Granting blanket table operations expands potential data loss. Exposed internal helpers increase coupling and attack surface. Unrestricted access can reveal confidential records to unrelated apps. Overbroad accessibility exposes internal implementation functions. ExplanationCorrect Answer C:Unrestricted access can reveal confidential records to unrelated apps. Least-privilege scope permissions limit exposure between app boundaries. The preventive measure is: Scope cross-app privileges to the named authorized consumer and operation.Incorrect Answers A:Application access can distinguish create, read, update and delete permissions. This is not the primary failure in the question. The direct unmitigated outcome here is: Unrestricted access can reveal confidential records to unrelated apps. B:A script include should not become a broad public interface by default. This is not the primary failure in the question. The direct unmitigated outcome here is: Unrestricted access can reveal confidential records to unrelated apps. D:Script include visibility is controlled by its application accessibility configuration. This is not the primary failure in the question. The direct unmitigated outcome here is: Unrestricted access can reveal confidential records to unrelated apps.
Question 52A regional office wants a supplier onboarding app but no owner has defined record retention or sensitive fields. A practitioner proposes: Elicit data classification and lifecycle requirements before creating tables. Which technical principle most directly explains why that correction is appropriate? Platform attachments and typed fields serve different storage functions. Access and process rules derive from user responsibilities. Separate custom apps reduce unintended changes to baseline business processes. Application design should encode custody and retention requirements early. ExplanationCorrect Answer D:Application design should encode custody and retention requirements early. That is why the appropriate action is: Elicit data classification and lifecycle requirements before creating tables. Confirm it by observing: The approved design lists each sensitive field and its retention policy.Incorrect Answers A:Platform attachments and typed fields serve different storage functions. That is a different technical consideration. For this problem, the governing mechanism is: Application design should encode custody and retention requirements early. The appropriate action is: Elicit data classification and lifecycle requirements before creating tables. B:Access and process rules derive from user responsibilities. That is a different technical consideration. For this problem, the governing mechanism is: Application design should encode custody and retention requirements early. The appropriate action is: Elicit data classification and lifecycle requirements before creating tables. C:Separate custom apps reduce unintended changes to baseline business processes. That is a different technical consideration. For this problem, the governing mechanism is: Application design should encode custody and retention requirements early. The appropriate action is: Elicit data classification and lifecycle requirements before creating tables.
Question 53A Business Rule authorizes updates using a username passed in a form field rather than the current authenticated user. If no correction is made, which avoidable consequence follows most directly? Trusting user-supplied identity enables impersonation. Checking a broader role accidentally expands data export rights. Conflating module visibility with data access can leak secrets. Assuming an interactive user exists can fail or overauthorize the job. ExplanationCorrect Answer A:Trusting user-supplied identity enables impersonation. Server authorization must rely on authenticated session identity. The preventive measure is: Use GlideSystem current-session identity such as gs.getUserID() for authorization context.Incorrect Answers B:Authorization must match the sensitivity of the requested operation. This is not the primary failure in the question. The direct unmitigated outcome here is: Trusting user-supplied identity enables impersonation. C:Navigation roles and sensitive record permissions represent different privileges. This is not the primary failure in the question. The direct unmitigated outcome here is: Trusting user-supplied identity enables impersonation. D:Background execution identity differs from a live end-user form session. This is not the primary failure in the question. The direct unmitigated outcome here is: Trusting user-supplied identity enables impersonation.
Question 54An external scoped application can delete the records of a privately scoped finance app after receiving broad app access. Which specific correction best addresses the described problem? Use approved scoped interfaces and validate that the operation is authorized. Limit the finance table's cross-application access to the required operations. Create and maintain the Business Rule in the owning application scope. Use a supported extension or authorized cross-scope interface instead of editing the protected file. ExplanationCorrect Answer B:Limit the finance table's cross-application access to the required operations. Cross-scope application access distinguishes read, update, create and delete. The resulting check is specific: The integration reads approved data but a delete attempt is denied.Incorrect Answers A:Server-side coding does not erase application access boundaries. This supports a different intervention; the stated problem requires: Limit the finance table's cross-application access to the required operations. The decisive reason is: Cross-scope application access distinguishes read, update, create and delete. C:Application-file scope controls ownership and change boundaries. This supports a different intervention; the stated problem requires: Limit the finance table's cross-application access to the required operations. The decisive reason is: Cross-scope application access distinguishes read, update, create and delete. D:Scope protections limit configuration changes across app ownership boundaries. This supports a different intervention; the stated problem requires: Limit the finance table's cross-application access to the required operations. The decisive reason is: Cross-scope application access distinguishes read, update, create and delete.
Question 55A designer labels two distinct business fields identically, leading users to confuse the incident date and approval date. After correcting the issue, which observation most directly verifies success? Dependent reports and scripts continue to function after a controlled migration. Each device item can be filtered and updated separately. Users correctly populate both dates during a representative test. Two similar-looking loan records remain individually retrievable. ExplanationCorrect Answer C:Users correctly populate both dates during a representative test. This result demonstrates that clear field semantics reduce incorrect input and improve maintenance. The corresponding change is: Assign distinct labels and dictionary descriptions to each field.Incorrect Answers A:Schema changes can affect consumers beyond the visible form. The alternative observation tests a different condition. The direct acceptance evidence here is: Users correctly populate both dates during a representative test. B:One-to-many relationships support independent records and queries. The alternative observation tests a different condition. The direct acceptance evidence here is: Users correctly populate both dates during a representative test. D:A record sys_id uniquely identifies the record independent of descriptive fields. The alternative observation tests a different condition. The direct acceptance evidence here is: Users correctly populate both dates during a representative test.
Question 56A technician adds a string field for equipment purchase date and later cannot filter it chronologically. Which specific correction best addresses the described problem? Distinguish form removal from dictionary field deletion before approving changes. Preserve stable technical field names and update display labels separately. Choose an appropriate data type and validation policy for phone input. Replace the inappropriate type through a safe migration to a Date field. ExplanationCorrect Answer D:Replace the inappropriate type through a safe migration to a Date field. Dictionary types determine storage and filtering semantics. The resulting check is specific: A date-range filter finds the expected purchase records.Incorrect Answers A:Removing a field from a view does not remove persisted table data. This supports a different intervention; the stated problem requires: Replace the inappropriate type through a safe migration to a Date field. The decisive reason is: Dictionary types determine storage and filtering semantics. B:Technical column names are referenced by scripts and integrations. This supports a different intervention; the stated problem requires: Replace the inappropriate type through a safe migration to a Date field. The decisive reason is: Dictionary types determine storage and filtering semantics. C:Data definition and input validation work together to support quality. This supports a different intervention; the stated problem requires: Replace the inappropriate type through a safe migration to a Date field. The decisive reason is: Dictionary types determine storage and filtering semantics.
Question 57A routine workflow has a branch for Approved and Rejected but no response to canceled approvals. If no correction is made, which avoidable consequence follows most directly? Unmodeled outcomes leave workflow records hanging. Partial data can pollute downstream systems. Premature notifications can mislead customers. Incorrect comparison logic misroutes expensive approvals. ExplanationCorrect Answer A:Unmodeled outcomes leave workflow records hanging. Approval orchestration requires handling every material terminal state. The preventive measure is: Add a defined canceled or timed-out outcome path.Incorrect Answers B:Flow actions should enforce preconditions before producing external side effects. This is not the primary failure in the question. The direct unmitigated outcome here is: Unmodeled outcomes leave workflow records hanging. C:Flow execution order should enforce dependent business approvals. This is not the primary failure in the question. The direct unmitigated outcome here is: Unmodeled outcomes leave workflow records hanging. D:Flow decisions depend on accurate conditions and data types. This is not the primary failure in the question. The direct unmitigated outcome here is: Unmodeled outcomes leave workflow records hanging.
Question 58Users want a quick view of overdue application tasks but the menu links to an unfiltered master list. If no correction is made, which avoidable consequence follows most directly? Poor menu placement creates discoverability and support problems. An overly broad module can hide urgent work among unrelated records. An application without discoverable navigation limits adoption. An inherited visibility assumption can expose restricted navigation. ExplanationCorrect Answer B:An overly broad module can hide urgent work among unrelated records. Modules can launch tailored lists based on configured filters. The preventive measure is: Add an appropriately filtered module for overdue records.Incorrect Answers A:Menu hierarchy should reflect ownership and task flow. This is not the primary failure in the question. The direct unmitigated outcome here is: An overly broad module can hide urgent work among unrelated records. C:Modules make application entry points available through navigation. This is not the primary failure in the question. The direct unmitigated outcome here is: An overly broad module can hide urgent work among unrelated records. D:Navigation security depends on both app-level and module-level configuration. This is not the primary failure in the question. The direct unmitigated outcome here is: An overly broad module can hide urgent work among unrelated records.
Question 59A REST action returns HTTP 401 but the application treats the empty body as valid success. Which specific correction best addresses the described problem? Follow supported pagination until all intended records are retrieved. Test the full request-and-response contract, including the remote business outcome. Handle authentication failures explicitly and verify the configured outbound credential. Use a stable business idempotency key or equivalent controlled duplicate prevention. ExplanationCorrect Answer C:Handle authentication failures explicitly and verify the configured outbound credential. HTTP response status is part of the integration result contract. The resulting check is specific: An expired token produces a monitored failure, not a success record.Incorrect Answers A:Paginated APIs return partial datasets when continuation is not handled. This supports a different intervention; the stated problem requires: Handle authentication failures explicitly and verify the configured outbound credential. The decisive reason is: HTTP response status is part of the integration result contract. B:HTTP success alone does not prove the intended integration effect. This supports a different intervention; the stated problem requires: Handle authentication failures explicitly and verify the configured outbound credential. The decisive reason is: HTTP response status is part of the integration result contract. D:Timeouts can leave remote side effects uncertain. This supports a different intervention; the stated problem requires: Handle authentication failures explicitly and verify the configured outbound credential. The decisive reason is: HTTP response status is part of the integration result contract.
Question 60A routine workflow has a branch for Approved and Rejected but no response to canceled approvals. Which specific correction best addresses the described problem? Map the action outputs before consuming them downstream. Resolve the manager dynamically from the approved user or assignment data. Use a lookup step with a specific employee reference condition. Add a defined canceled or timed-out outcome path. ExplanationCorrect Answer D:Add a defined canceled or timed-out outcome path. Approval orchestration requires handling every material terminal state. The resulting check is specific: A canceled approval closes or escalates predictably.Incorrect Answers A:Flow data pills convey outputs between steps when explicitly mapped. This supports a different intervention; the stated problem requires: Add a defined canceled or timed-out outcome path. The decisive reason is: Approval orchestration requires handling every material terminal state. B:Dynamic lookup reduces hardcoded lifecycle dependencies. This supports a different intervention; the stated problem requires: Add a defined canceled or timed-out outcome path. The decisive reason is: Approval orchestration requires handling every material terminal state. C:Targeted record lookups reduce unnecessary data retrieval. This supports a different intervention; the stated problem requires: Add a defined canceled or timed-out outcome path. The decisive reason is: Approval orchestration requires handling every material terminal state.