Hard Difficulty Questions

The SLA has breached its response time

Why wrong: A breach occurs when the SLA timer expires, but a processing error indicates a configuration issue, not a breach. Thus, this option is incorrect.

The SLA definition's condition is not satisfied

Why wrong: The SLA definition's condition determines when an SLA starts, but a processing error during SLA processing typically indicates a schedule issue, not a condition failure. Thus, this option is incorrect.

The SLA response time has exceeded the target

Why wrong: The error log entry is about processing the SLA, not about the response time exceeding the target; that would be a breach event, not a processing error. Thus, this option is incorrect.

The 'Wait for Condition' activity is not in the same application scope as the custom table.

Why wrong: Application scope does not affect workflow condition evaluation.

The user updating the record does not have the 'workflow_admin' role.

Why wrong: No special role is needed to trigger condition evaluation.

The custom table record is not related to the catalog item.

Why wrong: The condition can reference any table; relation is not required.

The incident is assigned to a group

Why wrong: Assignment is not a requirement for SLA start.

The incident is in a state of 'New'

Why wrong: State is part of the condition; it is not a separate requirement.

The SLA definition has a business schedule attached

Why wrong: Schedules affect timing but not starting.

The discovered CIs are in different classes that do not have relationship rules.

Why wrong: Relationships are generally cross-class and defined by the probes, not class rules.

The IRE is set to 'reconcile only' and not 'create'.

Why wrong: IRE reconcile only would still update relationships, not prevent creation.

The relationship type is not defined in the CMDB.

Why wrong: If the relationship type is missing, discovery would still create it using a default type or fail, but this is less common.

It automatically reconciles imported CIs with existing CIs.

Why wrong: Reconciliation is performed by IRE, not Data Manager.

It can directly import data from external databases.

Why wrong: Data Manager imports from CSV, not directly from databases.

An ACL can only have one role specified.

Why wrong: Multiple roles can be listed.

An ACL must have a script to evaluate conditions.

Why wrong: Script is optional; condition can be simple.

Transform maps run in the context of the source table

Why wrong: They run in context of target table.

Each field mapping can have a unique coalesce field

Why wrong: Coalesce is defined at the table level, not per field map.

Import sets automatically deduplicate based on sys_id

Why wrong: No automatic deduplication without coalesce.

The record producer is not mapped to the correct table.

Why wrong: Wrong: The table is correctly specified as sc_req_item.

The 'model' variable is not mapped to a field in the target table.

Why wrong: Wrong: The mapping shows 'model' to 'short_description', so it is mapped.

The record producer is inactive.

Why wrong: Wrong: If inactive, the record producer would not run at all.

Create a UI policy that changes the form when state is 'In Progress'

Why wrong: UI policy does not control UI action appearance.

Write an ACL on the UI action table

Why wrong: ACL can control execution but not visibility on form.

Assign the UI action to a role that only users in this state have

Why wrong: Role assignment is not state-based.

A Data Policy overrides the mandatory attribute

Why wrong: Data Policies enforce server-side and do not affect client-side highlighting.

The UI Policy is set to OnSubmit

Why wrong: OnSubmit would validate on submit, but the symptom is lack of client-side highlighting.

The UI Policy runs after the Client Script

Why wrong: If it runs after, the value would be set and the condition would apply correctly.

Modify the form view to remove the button

Why wrong: Modifying the form view removes the button for all users, not role-specific.

Business rule checking role

Why wrong: Business rules run server-side and cannot hide form buttons.

ACL with condition on role

Why wrong: ACLs control record access, not button visibility on a form.

personalize_form

Why wrong: The `personalize_form` role allows personalization of forms but does not provide access to the Form Designer for creating and editing forms. Thus, it does not meet the requirement.

ui_policy_admin

Why wrong: The `ui_policy_admin` role is for managing UI policies, not form design.

admin

Why wrong: The `admin` role has full access, including global publishing, which is more than required.

The trigger is set to 'State changed' but the state field is not properly referenced

Why wrong: The trigger fired, so the field is correctly referenced.

The flow is set to 'Deactivated'

Why wrong: If deactivated, the trigger would not fire.

The email notification is blocked by an email property

Why wrong: Email properties are system-wide and would affect other emails too.

The business rule condition is incorrect

Why wrong: Condition would prevent execution entirely, not cause inconsistency.

The system property 'glide.sys.schedulers.max_threads' is set too low

Why wrong: This would affect performance, not inconsistency.

The business rule is running 'before' instead of 'after'

Why wrong: Async rules can be before or after; consistency is more about concurrency.

The ACL is defined on a different table that extends 'incident'.

Why wrong: Wrong: ACLs on parent tables apply to child tables.

The script uses gs.hasRole('service_desk') which checks role, not group membership.

Why wrong: Wrong: group membership check would be different but the scenario says the user is in group.

Another read ACL exists that explicitly denies read access to the 'service_desk' group.

Why wrong: Wrong: No deny ACLs exist; they are only grant.

The SLA schedule is set to 24x7 but the incident was created outside business hours.

Why wrong: The schedule affects elapsed time counting, not the start condition.

The SLA definition has a pause condition that triggers on state change.

Why wrong: A pause condition halts an active SLA, it does not prevent starting.

The SLA definition is on the 'task' table instead of 'incident'.

Why wrong: 'task' is the parent table, so SLA on 'task' applies to incidents.

Increase the instance size

Why wrong: This may not address the root cause and is costly.

Remove all widgets from the homepage

Why wrong: This reduces functionality and user engagement.

Disable the search feature

Why wrong: Disabling search harms usability.

Checking CI status field for 'Retired'.

Why wrong: This only finds CIs already marked as retired, not those that should be retired.

Manually auditing each CI in the CMDB.

Why wrong: Manual auditing is not efficient or scalable.

The notification is triggered by a business rule that runs on after update.

Why wrong: This is standard and usually does not cause duplicates.

The notification has two separate conditions that both evaluate to true.

Why wrong: Duplicate conditions can cause multiple sends, but typically a notification has one condition.

The notification is set to 'Send for each record' and the record is being updated multiple times.

Why wrong: This would send multiple emails on each update, not necessarily duplicates on the same update.

The flow is deactivated

Why wrong: If deactivated, it would not run, but the question implies it is active.

The flow is scoped incorrectly

Why wrong: Scope issues might prevent access but are less likely than a trigger configuration mismatch.

The condition is incorrect

Why wrong: The condition 'state = requested' is typical for pending approvals.