Question 790A user impersonation test shows a server script logging the administrator who wrote it rather than the active user. A practitioner proposes: Use a current-user GlideSystem identity method at execution time. Which technical principle most directly explains why that correction is appropriate? Client-supplied role values are not an authoritative permission source. Runtime identity must reflect the executing session rather than an author constant. Navigation roles and sensitive record permissions represent different privileges. A role check is ineffective unless its denial branch blocks the operation. ExplanationCorrect Answer B:Runtime identity must reflect the executing session rather than an author constant. That is why the appropriate action is: Use a current-user GlideSystem identity method at execution time. Confirm it by observing: The log and permission check identify the impersonated test user.Incorrect Answers A:Client-supplied role values are not an authoritative permission source. That is a different technical consideration. For this problem, the governing mechanism is: Runtime identity must reflect the executing session rather than an author constant. The appropriate action is: Use a current-user GlideSystem identity method at execution time. C:Navigation roles and sensitive record permissions represent different privileges. That is a different technical consideration. For this problem, the governing mechanism is: Runtime identity must reflect the executing session rather than an author constant. The appropriate action is: Use a current-user GlideSystem identity method at execution time. D:A role check is ineffective unless its denial branch blocks the operation. That is a different technical consideration. For this problem, the governing mechanism is: Runtime identity must reflect the executing session rather than an author constant. The appropriate action is: Use a current-user GlideSystem identity method at execution time.
Question 791A user impersonation test shows a server script logging the administrator who wrote it rather than the active user. If no correction is made, which avoidable consequence follows most directly? A logging-only role failure does not prevent unauthorized changes. Conflating module visibility with data access can leak secrets. Baked-in author identity can subvert audits. Role spoofing can result if client data controls authorization. ExplanationCorrect Answer C:Baked-in author identity can subvert audits. Runtime identity must reflect the executing session rather than an author constant. The preventive measure is: Use a current-user GlideSystem identity method at execution time.Incorrect Answers A:A role check is ineffective unless its denial branch blocks the operation. This is not the primary failure in the question. The direct unmitigated outcome here is: Baked-in author identity can subvert audits. B:Navigation roles and sensitive record permissions represent different privileges. This is not the primary failure in the question. The direct unmitigated outcome here is: Baked-in author identity can subvert audits. D:Client-supplied role values are not an authoritative permission source. This is not the primary failure in the question. The direct unmitigated outcome here is: Baked-in author identity can subvert audits.
Question 792A security utility checks a high-privilege role but does not record failed authorization attempts for sensitive exports. Which specific correction best addresses the described problem? Compare stable user identifiers from authenticated context rather than display names. Use role-based authorization checks such as gs.hasRole with an approved application role. Use GlideSystem current-session identity such as gs.getUserID() for authorization context. Add safe server-side denial logging without exposing protected values. ExplanationCorrect Answer D:Add safe server-side denial logging without exposing protected values. Authorization diagnostics should support review while minimizing sensitive data. The resulting check is specific: Denied exports create a traceable event without secret payloads.Incorrect Answers A:Display labels and record identifiers are not interchangeable identity values. This supports a different intervention; the stated problem requires: Add safe server-side denial logging without exposing protected values. The decisive reason is: Authorization diagnostics should support review while minimizing sensitive data. B:Roles express privileges more robustly than hardcoded usernames. This supports a different intervention; the stated problem requires: Add safe server-side denial logging without exposing protected values. The decisive reason is: Authorization diagnostics should support review while minimizing sensitive data. C:Server authorization must rely on authenticated session identity. This supports a different intervention; the stated problem requires: Add safe server-side denial logging without exposing protected values. The decisive reason is: Authorization diagnostics should support review while minimizing sensitive data.
Question 793A scheduled cleanup job runs hourly but should run only once per night. Which specific correction best addresses the described problem? Set the Scheduled Script Execution to the approved nightly cadence. Use a stable notification identity or deduplication condition for sensitive effects. Use a targeted filter and an appropriate schedule interval. Validate the configured property and use a safe explicit fallback. ExplanationCorrect Answer A:Set the Scheduled Script Execution to the approved nightly cadence. Scheduled jobs execute according to configured intervals. The resulting check is specific: The next run time matches the nightly maintenance window.Incorrect Answers B:Asynchronous events may need idempotent downstream handling. This supports a different intervention; the stated problem requires: Set the Scheduled Script Execution to the approved nightly cadence. The decisive reason is: Scheduled jobs execute according to configured intervals. C:Scheduled queries should bound work to qualifying records. This supports a different intervention; the stated problem requires: Set the Scheduled Script Execution to the approved nightly cadence. The decisive reason is: Scheduled jobs execute according to configured intervals. D:Shared application utilities should fail predictably under bad configuration. This supports a different intervention; the stated problem requires: Set the Scheduled Script Execution to the approved nightly cadence. The decisive reason is: Scheduled jobs execute according to configured intervals.
Question 794A procurement app sends sensitive details to a REST endpoint without verifying a trusted TLS connection. After correcting the issue, which observation most directly verifies success? Replaying the same test request creates one vendor purchase record. A valid endpoint succeeds while an untrusted certificate fails safely. A test fixture spanning two pages yields the full expected record count. A test error log contains correlation IDs without token values. ExplanationCorrect Answer B:A valid endpoint succeeds while an untrusted certificate fails safely. This result demonstrates that transport authentication and encryption protect data in transit. The corresponding change is: Require an approved HTTPS endpoint and validated transport trust.Incorrect Answers A:Timeouts can leave remote side effects uncertain. The alternative observation tests a different condition. The direct acceptance evidence here is: A valid endpoint succeeds while an untrusted certificate fails safely. C:Paginated APIs return partial datasets when continuation is not handled. The alternative observation tests a different condition. The direct acceptance evidence here is: A valid endpoint succeeds while an untrusted certificate fails safely. D:Logging must not duplicate confidential authentication material. The alternative observation tests a different condition. The direct acceptance evidence here is: A valid endpoint succeeds while an untrusted certificate fails safely.
Question 795A support team plans to store thousands of attachments in multiple free-text fields on an app form. If no correction is made, which avoidable consequence follows most directly? An unnecessary duplicate app fragments maintenance and user navigation. Unverified rollout can spread unsuitable forms to many users. Embedding large binary data in text fields creates fragile records. Undefined role boundaries can expose restricted requests. ExplanationCorrect Answer C:Embedding large binary data in text fields creates fragile records. Platform attachments and typed fields serve different storage functions. The preventive measure is: Use supported attachment handling and a normalized record design.Incorrect Answers A:The smallest suitable platform change avoids unnecessary custom ownership. This is not the primary failure in the question. The direct unmitigated outcome here is: Embedding large binary data in text fields creates fragile records. B:Early application fit testing exposes mismatched business steps. This is not the primary failure in the question. The direct unmitigated outcome here is: Embedding large binary data in text fields creates fragile records. D:Access and process rules derive from user responsibilities. This is not the primary failure in the question. The direct unmitigated outcome here is: Embedding large binary data in text fields creates fragile records.
Question 796An application works on a developer instance but fails after moving because its scoped REST call is disallowed. If no correction is made, which avoidable consequence follows most directly? Granting blanket table operations expands potential data loss. Full table duplication risks stale and overexposed employee details. Testing in the wrong scope can mask deployment failures. Missing target privileges can disable integrations after release. ExplanationCorrect Answer D:Missing target privileges can disable integrations after release. Cross-scope authorizations are deployment-relevant application configuration. The preventive measure is: Capture and validate cross-scope privileges in the target application environment.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: Missing target privileges can disable integrations after release. B:Cross-application integration should minimize data duplication and access. This is not the primary failure in the question. The direct unmitigated outcome here is: Missing target privileges can disable integrations after release. C:Scope behavior depends on the actual caller and target ownership. This is not the primary failure in the question. The direct unmitigated outcome here is: Missing target privileges can disable integrations after release.
Question 797An event handler sends duplicate notifications when the same business action emits an event twice. A practitioner proposes: Use a stable notification identity or deduplication condition for sensitive effects. Which technical principle most directly explains why that correction is appropriate? Asynchronous events may need idempotent downstream handling. Scheduled execution cannot depend on an active form session. Client-callable Script Includes must enforce data minimization and authorization. Scheduled jobs execute according to configured intervals. ExplanationCorrect Answer A:Asynchronous events may need idempotent downstream handling. That is why the appropriate action is: Use a stable notification identity or deduplication condition for sensitive effects. Confirm it by observing: Replayed events generate only the intended single notice.Incorrect Answers B:Scheduled execution cannot depend on an active form session. That is a different technical consideration. For this problem, the governing mechanism is: Asynchronous events may need idempotent downstream handling. The appropriate action is: Use a stable notification identity or deduplication condition for sensitive effects. C:Client-callable Script Includes must enforce data minimization and authorization. That is a different technical consideration. For this problem, the governing mechanism is: Asynchronous events may need idempotent downstream handling. The appropriate action is: Use a stable notification identity or deduplication condition for sensitive effects. D:Scheduled jobs execute according to configured intervals. That is a different technical consideration. For this problem, the governing mechanism is: Asynchronous events may need idempotent downstream handling. The appropriate action is: Use a stable notification identity or deduplication condition for sensitive effects.
Question 798A user does not see a module despite having the table read ACL role. A practitioner proposes: Check the module's required role separately from table ACL authorization. Which technical principle most directly explains why that correction is appropriate? Application and module navigation restrictions operate at separate levels. Navigation role checks and record data permission checks are distinct. Effective role assignment can flow from groups and contained roles. Direct and group-supplied role grants both contribute to effective access. ExplanationCorrect Answer B:Navigation role checks and record data permission checks are distinct. That is why the appropriate action is: Check the module's required role separately from table ACL authorization. Confirm it by observing: After the role correction, the permitted user can open the module.Incorrect Answers A:Application and module navigation restrictions operate at separate levels. That is a different technical consideration. For this problem, the governing mechanism is: Navigation role checks and record data permission checks are distinct. The appropriate action is: Check the module's required role separately from table ACL authorization. C:Effective role assignment can flow from groups and contained roles. That is a different technical consideration. For this problem, the governing mechanism is: Navigation role checks and record data permission checks are distinct. The appropriate action is: Check the module's required role separately from table ACL authorization. D:Direct and group-supplied role grants both contribute to effective access. That is a different technical consideration. For this problem, the governing mechanism is: Navigation role checks and record data permission checks are distinct. The appropriate action is: Check the module's required role separately from table ACL authorization.
Question 799A procurement app sends sensitive details to a REST endpoint without verifying a trusted TLS connection. If no correction is made, which avoidable consequence follows most directly? Ignoring pagination silently drops source records. Uncontrolled retries worsen vendor outages. Weak transport validation exposes data to interception. Superficial status checks can conceal silent data mismatches. ExplanationCorrect Answer C:Weak transport validation exposes data to interception. Transport authentication and encryption protect data in transit. The preventive measure is: Require an approved HTTPS endpoint and validated transport trust.Incorrect Answers A:Paginated APIs return partial datasets when continuation is not handled. This is not the primary failure in the question. The direct unmitigated outcome here is: Weak transport validation exposes data to interception. B:External APIs can throttle callers and need controlled backoff. This is not the primary failure in the question. The direct unmitigated outcome here is: Weak transport validation exposes data to interception. D:That exposure arises in the separate situation: A partner changes the outbound API field name and the request still returns 200 but omits the intended business update. It follows because HTTP success alone does not prove the intended integration effect. The more direct danger for this question is: Weak transport validation exposes data to interception.
Question 800A routine workflow has a branch for Approved and Rejected but no response to canceled approvals. A practitioner proposes: Add a defined canceled or timed-out outcome path. Which technical principle most directly explains why that correction is appropriate? Flow changes can affect both happy-path and error-state behavior. Targeted record lookups reduce unnecessary data retrieval. Workflow and Flow Designer capabilities can differ by configuration and release. Approval orchestration requires handling every material terminal state. ExplanationCorrect Answer D:Approval orchestration requires handling every material terminal state. That is why the appropriate action is: Add a defined canceled or timed-out outcome path. Confirm it by observing: A canceled approval closes or escalates predictably.Incorrect Answers A:Flow changes can affect both happy-path and error-state behavior. That is a different technical consideration. For this problem, the governing mechanism is: Approval orchestration requires handling every material terminal state. The appropriate action is: Add a defined canceled or timed-out outcome path. B:Targeted record lookups reduce unnecessary data retrieval. That is a different technical consideration. For this problem, the governing mechanism is: Approval orchestration requires handling every material terminal state. The appropriate action is: Add a defined canceled or timed-out outcome path. C:Workflow and Flow Designer capabilities can differ by configuration and release. That is a different technical consideration. For this problem, the governing mechanism is: Approval orchestration requires handling every material terminal state. The appropriate action is: Add a defined canceled or timed-out outcome path.