I85PREP
⌘ K
Oracle CX Sales 2026 Implementation Professional study materials
Oracle CX Sales 2026 Implementation Professional study resources

Oracle CX Sales 2026 Implementation Professional practice questions

One question at a time. Build your Oracle CX Sales 2026 Implementation Professional understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Understanding the Procurement Application

In the Oracle Procurement application, which business object represents the approved, structured request that a requisitioning employee submits so that a buyer can source and purchase goods or services?

  1. Receiving transaction
  2. Supplier negotiation
  3. Purchase requisition Correct answer.
  4. Purchase order

Explanation

A purchase requisition is the internal document an employee submits to request goods or services; it captures need-by date, item, quantity, and deliver-to information and then flows into buyer sourcing or automated ordering. A purchase order is the external commitment issued to a supplier after sourcing, so it is downstream of the requisition.

Question 2Understanding the Procurement Application

A requisition line is created for an item that is stocked in inventory. Which outcome best describes how Oracle Procurement handles that demand during requisition processing?

  1. It is rejected because inventory items cannot be requisitioned.
  2. It is automatically converted to a purchase order regardless of stock availability.
  3. It can be fulfilled from available inventory before any external purchase is created. Correct answer.
  4. It is routed to the supplier portal for a supplier-hosted catalog punch-out.

Explanation

Requisition demand for inventory items is evaluated against on-hand and available balances so that internal stock can satisfy the need before a buy is executed. Only the residual shortage is passed to purchasing for supplier sourcing.

Question 3Understanding the Procurement Application

Which statement accurately describes the role of a smart form or descriptive flexfield in the procurement setup?

  1. It captures additional business-specific attributes on procurement documents without changing the base table structure. Correct answer.
  2. It stores approved supplier bank account details for payment processing.
  3. It replaces the approval workflow for high-value requisitions.
  4. It defines the chart of accounts used for encumbrance accounting.

Explanation

Descriptive flexfields and smart forms extend procurement pages with customer-specific attributes that are stored in extension segments rather than altering base tables. They are an extensibility mechanism, not a substitute for workflow or accounting configuration.

Question 4Understanding the Procurement Application

During requisition approval, a requester's manager is out of office. Which Oracle Procurement capability allows the approval to continue without re-creating the document?

  1. Changing the requisition currency to bypass the rule
  2. Deleting the requisition and submitting a new one
  3. Cancelling the purchase order and reissuing it
  4. Reassigning or delegating the approval task to another approver Correct answer.

Explanation

Approval management supports reassignment and delegation so an in-flight approval task can move to an alternate approver while preserving the document and its history. Re-creating documents or altering financial attributes does not resolve an approver availability problem.

Question 5Understanding the Procurement Application

A buyer wants to consolidate multiple approved requisition lines from different requesters into a single order to one supplier. Which procurement feature supports this?

  1. Running a period-close reconciliation
  2. Creating a separate negotiation for each line
  3. Supplier registration
  4. Grouping requisition lines into a single purchase order during document creation Correct answer.

Explanation

Buyers can group eligible requisition lines by supplier and other criteria when creating a purchase order, which consolidates demand and reduces transaction volume. Each line remains linked to its originating requisition for tracking.

Question 6Understanding the Procurement Application

Which document type is used when an organization wants suppliers to compete on price and terms for a defined requirement before an award is made?

  1. Goods receipt
  2. Supplier negotiation Correct answer.
  3. Invoice hold
  4. Blanket purchase agreement

Explanation

A supplier negotiation is a sourcing event in which invited suppliers submit responses such as pricing and terms, and the buyer awards business based on the evaluation. It precedes the purchase order that formalizes the award.

Question 7Understanding the Procurement Application

A requisition is submitted with a deliver-to location that has no valid ship-to address for the supplier. What is the most likely procurement consequence?

  1. The requisition automatically converts to an internal transfer order.
  2. The invoice is paid before goods are shipped.
  3. The supplier negotiation is cancelled automatically.
  4. The requisition is approved but the resulting order cannot be successfully dispatched to the supplier. Correct answer.

Explanation

Deliver-to and ship-to information drives order dispatch and fulfillment; an invalid location prevents the purchase order from reaching the supplier correctly. Validating location setup before ordering avoids downstream receiving and payment exceptions.

Question 8Understanding the Procurement Application

Which statement best describes the purpose of a blanket purchase agreement in Oracle Procurement?

  1. It establishes pre-negotiated prices and terms that requesters can draw against over a defined period. Correct answer.
  2. It records a one-time receipt of consumable supplies.
  3. It is the approval workflow assigned to capital requisitions.
  4. It is the accounting entry generated at period end.

Explanation

A blanket purchase agreement captures agreed prices, quantities, and validity dates with a supplier so that releases or requisitions can be fulfilled against it without renegotiation. It reduces cycle time for repeat purchases of known items.

Question 9Understanding the Procurement Application

A requester selects a catalog item whose price differs from the negotiated contract price. Which behavior should the implementation expect?

  1. The application can validate the price against the applicable contract and flag or adjust discrepancies. Correct answer.
  2. The supplier is automatically changed to the lowest-priced supplier.
  3. The catalog price always overrides the contract price without validation.
  4. The requisition is blocked because contracts cannot be referenced from catalogs.

Explanation

Procurement can reference applicable contracts during requisitioning and validate that the price complies with negotiated terms, surfacing exceptions to the requester or buyer. This enforces contract compliance without silently ignoring the agreement.

Question 10Understanding the Procurement Application

Which setup determines the default approval hierarchy used when a requisition is submitted?

  1. The receiving tolerances
  2. The invoice match option
  3. The approval management configuration and its rules Correct answer.
  4. The supplier site assignment

Explanation

Approval management configuration defines the rules and hierarchy that determine who must approve a requisition and in what order. It is separate from supplier, receiving, and invoice settings, which govern other stages of the procure-to-pay flow.

Question 11Understanding the Procurement Application

An implementation team needs requisitions for IT hardware to route to the IT asset manager in addition to the requester's manager. Which approach achieves this?

  1. Configure approval rules that add the IT asset manager based on item category. Correct answer.
  2. Change the requisition currency for IT items.
  3. Assign the IT asset manager as the supplier contact.
  4. Disable approval for all IT categories.

Explanation

Conditional approval rules can evaluate attributes such as item category and insert additional approvers into the hierarchy for matching requisitions. This keeps standard manager approval while adding the specialist review only where required.

Question 12Understanding the Procurement Application

What is the primary purpose of the receiving function in the procure-to-pay flow?

  1. To generate the requisition approval hierarchy
  2. To confirm that ordered goods or services were delivered and to record quantities accepted Correct answer.
  3. To register a new supplier in the system
  4. To negotiate pricing with the supplier

Explanation

Receiving records the physical delivery and accepted quantities so that inventory, asset, and expense accounting and invoice matching can proceed. It is a confirmation step that follows ordering and precedes payment.

Question 13Understanding the Procurement Application

A buyer creates a purchase order from approved requisition lines, then the requester asks to change the quantity. Which statement reflects correct procurement practice?

  1. The order is automatically deleted when the requisition is edited.
  2. Quantity changes are impossible once a requisition is approved.
  3. Changes must be managed through the order or a controlled change process so the commitment and requisition remain consistent. Correct answer.
  4. The requisition can be edited freely after the order exists with no effect on the order.

Explanation

Once demand has been ordered, changes should flow through the purchase order or a controlled change process so that the supplier commitment, budget, and requisition linkage stay consistent. Editing the requisition independently risks divergence between demand and commitment.

Question 14Understanding the Procurement Application

Which configuration element controls the default unit of measure and rounding behavior applied when a requisition line is priced?

  1. The period-close checklist
  2. The item definition and its unit of measure setup Correct answer.
  3. The invoice hold name
  4. The supplier registration questionnaire

Explanation

Item definitions carry the primary unit of measure and related attributes that drive how quantities and prices are calculated and rounded on documents. Supplier questionnaires, invoice holds, and close checklists govern unrelated processes.

Question 15Understanding the Procurement Application

An organization wants employees to see only catalog items relevant to their department when creating requisitions. Which procurement configuration supports this?

  1. Removing the receiving step from the flow
  2. Disabling all supplier negotiations
  3. Local catalog content assigned to the appropriate procurement business unit or category access Correct answer.
  4. A blanket purchase agreement with no validity dates

Explanation

Catalog content can be scoped by local catalog assignment, business unit, or category access so requesters see only relevant items. This improves compliance and reduces mis-selection during requisitioning.

Question 16Understanding the Procurement Application

Which statement best describes how a purchase order differs from a purchase requisition in Oracle Procurement?

  1. Both documents are identical in purpose and differ only in numbering.
  2. A purchase order is an internal request, while a requisition is the supplier-facing commitment.
  3. A requisition is a legally binding external commitment, while a purchase order is an internal request.
  4. A requisition is an internal request for goods or services, while a purchase order is the commitment issued to the supplier. Correct answer.

Explanation

The requisition expresses internal demand and requires approval before buying, whereas the purchase order is the formal commitment communicated to the supplier for fulfillment. Keeping this distinction clear is fundamental to the procure-to-pay flow.

Question 17Understanding the Procurement Application

A requisition line references a supplier item that has been end-dated. What is the most appropriate procurement response?

  1. Convert the requisition into a supplier negotiation automatically.
  2. Ignore the status and rely on receiving to catch the problem.
  3. Approve and order the end-dated item because requisitions bypass item status.
  4. Replace or re-source the line with a valid, active item or supplier item before ordering. Correct answer.

Explanation

End-dated supplier items should not be ordered; the line must be re-sourced to an active item or supplier item so the commitment is valid and supportable. Relying on downstream receiving to catch the issue creates avoidable exceptions and delays.

Question 18Implementing Functional Setup Manager

In Oracle CX Sales Functional Setup Manager, which offering must be opted in before the Sales implementation task lists become available to an implementer?

  1. Oracle Fusion Financials offering
  2. Oracle Procurement offering
  3. Oracle CX Sales offering Correct answer.
  4. Oracle CX Sales and Fusion Service combined offering

Explanation

Functional Setup Manager exposes implementation task lists only for offerings that have been opted in for the enterprise. The Sales-specific task lists belong to the Oracle CX Sales offering, so that offering must be enabled before the implementer can provision or configure Sales objects. Opting in to unrelated offerings does not publish the Sales task lists.

Question 19Implementing Functional Setup Manager

An implementer needs to verify which setup tasks are still incomplete for the CX Sales offering. Where in Functional Setup Manager is this progress tracked?

  1. The Manage Users page
  2. The Manage Enterprise Roles page
  3. The Implementation Projects work area Correct answer.
  4. The Scheduled Processes work area

Explanation

Implementation Projects is the Functional Setup Manager work area where an implementer assigns offerings, generates task lists, and tracks completion status per task. It shows which tasks are not started, in progress, or completed. The other pages listed belong to security or process scheduling and do not report setup progress.

Question 20Implementing Functional Setup Manager

Which Functional Setup Manager object groups related setup tasks into a sequenced list that an implementer assigns to an implementation project?

  1. A business unit
  2. A reference data set
  3. A role mapping
  4. A task list Correct answer.

Explanation

A task list is the Functional Setup Manager construct that sequences related setup tasks for an offering, and implementers assign task lists into an implementation project to drive the work. Business units are organizational structures, reference data sets partition setup data, and role mappings assign security. Only the task list represents the sequenced setup work.

Question 21Implementing Functional Setup Manager

During CX Sales setup, an implementer must decide how configuration data is shared across business units. Which Functional Setup Manager concept controls this partitioning?

  1. Reference data sets Correct answer.
  2. Implementation project statuses
  3. Task dependencies
  4. Offerings

Explanation

Reference data sets determine whether a given setup object's data is shared globally or isolated per business unit. Assigning the same reference data set to multiple business units shares the configuration; assigning different sets isolates it. Task dependencies, offerings, and project statuses govern workflow and availability, not data partitioning.

Question 22Implementing Functional Setup Manager

An implementer wants to export the current CX Sales setup data from one environment and import it into a test environment. Which Functional Setup Manager capability supports this?

  1. Export and import of setup data using implementation project export Correct answer.
  2. Running the scheduled process to purge setup data
  3. Manually re-entering each task in the target environment
  4. Cloning the entire pod without Functional Setup Manager

Explanation

Functional Setup Manager provides export and import of setup data, typically scoped to an implementation project, so configuration can be migrated between environments. This packages the setup tasks and their data for transport. Purging removes data, cloning copies the whole environment, and manual re-entry is not a Functional Setup Manager migration feature.

Question 23Implementing Functional Setup Manager

A CX Sales implementer needs to run a specific setup task immediately without completing the earlier tasks in the task list. What should the implementer do?

  1. Wait until all prior tasks are marked complete
  2. Assign the task to a different implementation project
  3. Delete the implementation project and recreate it
  4. Use the Go to Task action on the individual task Correct answer.

Explanation

Functional Setup Manager allows an implementer to jump directly to an individual setup task using the Go to Task action, bypassing the suggested sequence. Task order is a recommendation, not a hard gate. Deleting the project, waiting for prior tasks, or reassigning the task are unnecessary and do not achieve the goal.

Question 24Implementing Functional Setup Manager

Which statement best describes the relationship between an offering and its task lists in Functional Setup Manager?

  1. An offering and a task list are the same object
  2. Each task list can belong to only one offering, and an offering can have multiple task lists Correct answer.
  3. Task lists exist independently of offerings and are never associated with them
  4. Each offering can have only one task list

Explanation

An offering groups one or more task lists, and each task list is associated with a single offering that owns it. This hierarchy lets an implementer opt in to an offering and then select the relevant task lists for the project. The other statements misstate the cardinality or conflate the two distinct objects.

Question 25Implementing Functional Setup Manager

An implementer is configuring CX Sales and must ensure that a newly created setup task appears in the implementation project. Which action makes the task available in the project?

  1. Assign the task to a reference data set
  2. Change the project status to Completed
  3. Add the task to the project's task list and refresh the project Correct answer.
  4. Create a new business unit for the task

Explanation

Tasks become available in an implementation project when they belong to a task list that is part of the project; adding the task to the task list and refreshing the project surfaces it. Business units, project status, and reference data sets do not control task visibility in the project.

Question 26Implementing Functional Setup Manager

Which Functional Setup Manager feature allows an implementer to copy setup data from a source business unit to a target business unit within the same environment?

  1. Manage Reference Data Sets copy
  2. Export and import of setup data Correct answer.
  3. Task list duplication
  4. Offering opt-in

Explanation

Export and import of setup data can move configuration between business units or environments, including within the same pod. It packages the setup data for the selected scope and applies it to the target. Reference data set management, task list duplication, and opt-in do not transfer configuration data between business units.

Question 27Implementing Functional Setup Manager

An implementer notices that a CX Sales setup task is marked as Optional in the task list. What does this designation mean for the implementation?

  1. The task automatically runs in the background
  2. The task is hidden from all implementers
  3. The task must be completed before the project can close
  4. The task can be skipped without blocking the implementation Correct answer.

Explanation

Optional tasks are part of the task list but are not mandatory for completing the implementation; they can be skipped when not relevant. Required tasks must be addressed before the project is considered complete. Optional tasks remain visible and do not run automatically.

Question 28Implementing Functional Setup Manager

Which Functional Setup Manager work area would an implementer use to assign an offering to an implementation project?

  1. Manage Users in the Security Console
  2. Manage Business Units
  3. Manage Scheduled Processes
  4. Manage Offerings in the Setup and Maintenance work area Correct answer.

Explanation

Offerings are selected and assigned to implementation projects from the Setup and Maintenance work area, where Functional Setup Manager resides. Security Console, scheduled processes, and business unit management serve different purposes and do not assign offerings to projects.

Question 29Implementing Functional Setup Manager

An implementer wants to compare the setup data in two CX Sales environments to identify configuration drift. Which approach uses Functional Setup Manager capabilities appropriately?

  1. Clone one environment over the other
  2. Run a purge process in both environments
  3. Disable the offering in one environment
  4. Export setup data from both environments and compare the exported packages Correct answer.

Explanation

Exporting setup data from each environment produces comparable packages that reveal differences in configuration. Purging deletes data, cloning overwrites an environment, and disabling an offering changes availability rather than enabling comparison. Only export supports a meaningful comparison of setup data.

Question 30Implementing Functional Setup Manager

An implementer must ensure that only certain roles can view and execute a sensitive CX Sales setup task. Which Functional Setup Manager mechanism governs this?

  1. Role-based access to setup tasks Correct answer.
  2. Implementation project status
  3. Task list sequencing
  4. Reference data set assignment

Explanation

Access to setup tasks is controlled through role-based security, so only users whose roles include the necessary privileges can view or execute a task. Sequencing, reference data sets, and project status affect workflow and data partitioning, not who can perform a task.

Question 31Implementing Functional Setup Manager

Which statement accurately describes how an implementer should handle a required setup task that is not applicable to the current CX Sales implementation?

  1. Ignore it permanently without documentation
  2. Mark it complete only after confirming with the business that it is genuinely inapplicable Correct answer.
  3. Delete the offering to remove the task
  4. Change the task to Optional in the offering

Explanation

Required tasks should be resolved deliberately; if a required task truly does not apply, the implementer documents the decision and marks it complete after business confirmation. Deleting the offering, ignoring the task, or altering offering definitions are not appropriate ways to handle inapplicable required tasks.

Question 32Implementing Functional Setup Manager

Which Functional Setup Manager action generates the task lists for an offering into an implementation project?

  1. Assign a role to the implementer
  2. Schedule a purge process
  3. Create a new reference data set
  4. Opt in to the offering and add its task lists to the project Correct answer.

Explanation

After opting in to an offering, the implementer adds the relevant task lists to the implementation project, which generates the tasks for tracking. Reference data sets, purge processes, and role assignment serve other purposes and do not generate task lists into a project.

Question 33Implementing Functional Setup Manager

An implementer is preparing to migrate CX Sales setup data to production and wants to limit the export to only the configuration relevant to the Sales offering. What should the implementer do?

  1. Scope the export to the implementation project containing the Sales task lists Correct answer.
  2. Export only the reference data sets
  3. Export all setup data from the source environment without scoping
  4. Export the business unit definitions only

Explanation

Scoping the export to the implementation project that contains the Sales task lists limits the migration to the relevant configuration and avoids transporting unrelated setup data. Exporting everything, only reference data sets, or only business units would omit needed configuration or include irrelevant data.

Question 34Implementing Functional Setup Manager

Which statement best explains why Functional Setup Manager uses task dependencies within a task list?

  1. To enforce that certain setup data exists before dependent tasks can be completed correctly Correct answer.
  2. To automatically assign roles to users
  3. To prevent implementers from viewing later tasks
  4. To partition data across business units

Explanation

Task dependencies reflect the logical order in which configuration must occur, so that data created by an earlier task is available to a later dependent task. They guide sequencing rather than hide tasks, assign roles, or partition data. Respecting dependencies reduces setup errors during implementation.

Question 35Provisioning Common Application Functions

A sales administrator needs to give a new hire access to CX Sales with a job role that already exists in the implementation. Which provisioning object should the administrator assign to the user?

  1. A resource role mapped to the job role in the security reference implementation Correct answer.
  2. An application composer sandbox published to production
  3. A data security policy scoped to the sales organization
  4. A custom object definition created for the sales organization

Explanation

Application access in CX Sales is granted through resource roles, which are mapped to job roles in the security reference implementation. Assigning the resource role to the user gives the functional privileges defined for that job role. Custom objects, data security policies, and sandboxes control data visibility or configuration, not the base set of application privileges.

Question 36Provisioning Common Application Functions

An implementation team wants to change the label of a standard field on the Opportunity edit page without affecting other pages. Which provisioning tool is intended for this task?

  1. Business Intelligence Publisher
  2. Application Composer Correct answer.
  3. Enterprise Scheduler Service
  4. Identity Cloud Service

Explanation

Application Composer is the declarative tool for extending and customizing CX Sales objects, pages, and field labels. Page-level label changes on standard objects are made there and deployed through a sandbox. The other components handle reporting, job scheduling, and identity management respectively.

Question 37Provisioning Common Application Functions

A sales manager must see only opportunities belonging to the territories they manage, while a sales representative sees only their own records. Which provisioning mechanism enforces this difference?

  1. Groovy scripts registered in a sandbox
  2. Page layout assignments on the opportunity object
  3. Data security policies attached to the job roles Correct answer.
  4. Reference data sets loaded during implementation

Explanation

Data security policies define the conditions under which a job role can access records, and they are attached to roles so that different users see different record sets. Page layouts and Groovy scripts affect presentation or logic, not row-level visibility. Reference data sets populate seed data rather than enforce access.

Question 38Provisioning Common Application Functions

During provisioning, a consultant needs to import a large volume of accounts and contacts from a legacy CRM. Which standard CX Sales capability should be used?

  1. SOAP calls to the identity provider
  2. File-based data import using the import management templates Correct answer.
  3. Direct SQL inserts into the application schema
  4. Manual entry through the desktop UI

Explanation

CX Sales provides import management with file-based templates for loading business objects such as accounts and contacts in bulk. Direct database access is not supported in the cloud service, and manual entry does not scale. Identity provider calls handle authentication, not data loading.

Question 39Provisioning Common Application Functions

Which statement correctly describes the purpose of a sandbox in a CX Sales implementation?

  1. It stores a copy of production transaction data for reporting
  2. It isolates configuration changes so they can be tested before publishing to the mainline Correct answer.
  3. It replaces the need for a separate test environment
  4. It automatically grants new privileges to all users

Explanation

A sandbox is an isolated layer where configuration changes are made and tested, then published to the mainline so all users see them. It does not hold transaction data copies, remove the need for testing environments, or change user privileges by itself.

Question 40Provisioning Common Application Functions

A consultant creates a new custom object for warranty registrations in a sandbox and needs it to appear as a related list on the Account detail page. Which sequence of actions is correct?

  1. Create the object in the mainline, then import records before adding the related list
  2. Define the relationship only after the object records have been migrated
  3. Create the object, define the relationship to Account, then add the related list to the page layout and publish the sandbox Correct answer.
  4. Publish the sandbox first, then create the object and relationship in the mainline

Explanation

Custom objects and their relationships are defined in Application Composer inside a sandbox, and the related list is added to the page layout there. The changes become visible to users only after the sandbox is published to the mainline. Creating objects directly in the mainline or deferring the relationship until after migration is not the supported pattern.

Question 41Provisioning Common Application Functions

A company wants its sales representatives to see the account name, industry, and a custom rating field on the Account overview, but wants managers to see additional revenue fields. Which provisioning approach achieves this?

  1. Apply a data security policy that hides revenue columns
  2. Create two custom objects, one for each audience
  3. Assign different page layouts to the resource roles for representatives and managers Correct answer.
  4. Create a separate sandbox for each audience

Explanation

Page layouts can be assigned to different roles so that each audience sees the fields relevant to them on the same page. Custom objects are unnecessary because the requirement is field visibility, not new data structures. Data security policies filter records rather than rearrange displayed fields, and sandboxes are configuration workspaces, not per-audience runtime views.

Question 42Provisioning Common Application Functions

A consultant must give a partner user access to CX Sales with restricted privileges that differ from any internal job role. What is the recommended provisioning step?

  1. Assign the internal sales administrator role and rely on data security to limit records
  2. Disable the partner user's identity and enable it after login
  3. Create a new sandbox and add the partner as a sandbox user
  4. Create a custom role, add the required function and data privileges, and assign it to the partner user Correct answer.

Explanation

When no existing job role matches the required privileges, a custom role is created with only the necessary function and data privileges and then assigned to the user. Assigning an administrator role violates least privilege even if data security limits records. Sandboxes and identity toggling do not define application privileges.

Question 43Provisioning Common Application Functions

An implementation needs a validation rule that prevents saving an opportunity when the expected revenue is negative. Where should this rule be defined?

  1. As a data security policy on the opportunity object
  2. As a reference data set loaded at setup
  3. As a page layout assignment for the sales role
  4. As an object-level validation rule in Application Composer within a sandbox Correct answer.

Explanation

Object-level validation rules are declarative constraints defined in Application Composer and deployed through a sandbox. They run when a record is saved, blocking invalid data. Data security policies, page layouts, and reference data sets do not enforce field-level business constraints.

Question 44Provisioning Common Application Functions

A consultant is asked why a newly created custom field is not visible to users after being added in a sandbox. What is the most likely explanation?

  1. The field was added to an object that has no records
  2. The sandbox changes have not yet been published to the mainline Correct answer.
  3. The field was created with the wrong data type
  4. The user's identity has expired

Explanation

Configuration changes made in a sandbox remain isolated until the sandbox is published, at which point they become visible in the mainline. Data type or record volume does not determine visibility of a configured field. An expired identity would block login entirely rather than hide a single field.

Question 45Provisioning Common Application Functions

A team wants to automate assigning a follow-up task when a lead is qualified. Which provisioning capability is designed for this?

  1. An object workflow or trigger defined in Application Composer and deployed via a sandbox Correct answer.
  2. A page layout assigned to the lead record type
  3. A data security policy on the lead object
  4. A reference data set containing task types

Explanation

Workflow rules and triggers in Application Composer automate actions such as creating follow-up tasks when a record condition is met. They are configured in a sandbox and published. Data security policies, page layouts, and reference data sets do not execute business automation.

Question 46Provisioning Common Application Functions

A consultant must ensure that when an account is deleted, its related warranty registration records are also removed. Which configuration is required?

  1. Add the related list to the Account page layout
  2. Create a data security policy on the custom object
  3. Import the records again after each deletion
  4. Define the relationship between the custom object and Account with a cascading delete behavior Correct answer.

Explanation

Referential behavior such as cascading delete is configured on the relationship definition between the child custom object and its parent. Page layouts and data security policies affect display and access, not referential integrity. Re-importing records does not address orphaned child records.

Question 47Provisioning Common Application Functions

A consultant needs to load reference data such as currency codes and industry values before importing transactional records. Which provisioning step is appropriate?

  1. Create the values manually as custom fields on each object
  2. Load the reference data sets provided for the implementation using the standard import process Correct answer.
  3. Disable validation rules so that missing values are accepted
  4. Skip reference data because transactional imports create it automatically

Explanation

Reference data sets supply the standardized values that transactional records depend on, and they are loaded through the standard import process before dependent data. Custom fields do not replace reference data, and transactional imports do not create missing reference values. Disabling validation would allow corrupt data rather than satisfy the dependency.

Question 48Provisioning Common Application Functions

A security review finds that a group of users can view opportunities outside their territory. Which provisioning area should the consultant examine first?

  1. The import templates used for opportunities
  2. The page layout assigned to the opportunity object
  3. The sandbox publish history
  4. The data security policies and role assignments for the affected users Correct answer.

Explanation

Record visibility is governed by data security policies combined with the roles assigned to users, so an over-broad policy or an incorrect role assignment is the likely cause. Page layouts, publish history, and import templates do not grant record access.

Question 49Provisioning Common Application Functions

A consultant is told that a custom object must be available only to users in a specific business unit. Which combination of provisioning steps best meets this requirement?

  1. Assign the internal administrator role to all users in the business unit
  2. Create the object in the mainline and rely on page layouts to restrict visibility
  3. Create the object in a sandbox, define its relationships, and attach a data security policy scoped to the business unit Correct answer.
  4. Import the object's records only for the target business unit

Explanation

The object structure and relationships are built in a sandbox, and a data security policy scoped to the business unit limits which users can access its records. Page layouts and selective imports do not enforce access. Granting administrator privileges is excessive and unrelated to scoping the object.

Question 50Provisioning Common Application Functions

A team reports that a validation rule deployed from a sandbox does not fire for records created through a bulk import. What is the most likely cause?

  1. The user lacks the privilege to run the rule
  2. The sandbox was never published, so the rule does not exist
  3. The import process bypasses certain object validation, so the rule must be enforced through an import-specific validation or trigger Correct answer.
  4. The rule was written for the wrong object

Explanation

Bulk import paths can bypass some object-level validation, so constraints must be reinforced through import-specific validation or a trigger that runs during the load. An unpublished sandbox would mean the rule is absent altogether, but the scenario states it was deployed. Object targeting and user privilege would produce different symptoms.