Select Two (Multi-Select) Questions

The supplier is automatically invited to participate in a Sourcing event.

Why it fails: Qualification does not automatically trigger a sourcing event invitation. Suppliers must still be manually invited to specific RFX projects by sourcing managers. This separation of duties ensures that procurement professionals maintain control over which qualified suppliers are invited to participate in specific competitive bidding processes.

The supplier is automatically blocked from further registration updates.

Why it fails: Qualification does not prevent a supplier from updating their profile. Suppliers are still encouraged to provide current information, and they can submit profile updates or new certification documents at any time. Blocking updates would be counterproductive to the goal of maintaining accurate, up-to-date supplier master data.

The supplier is automatically assigned a performance scorecard.

Why it fails: Performance scorecards are not automatically assigned at the qualification stage. Scorecards are created via SPM project templates once a relationship has matured or specific metrics need to be tracked. Assigning them at the qualification phase would be premature as no transaction history exists to calculate meaningful performance data.

Historical spend analysis reports.

Why it fails: Spend analysis is typically handled within the SAP Ariba Spend Analysis module rather than the Supplier 360 profile. While the profile provides a link to supplier information, the analytical reporting on spend categories and trends involves complex data cubes and external warehousing, which are not stored directly within the basic profile view.

Internal employee payroll records.

Why it fails: Internal employee payroll data is sensitive HR information that is completely decoupled from the supplier management domain. Accessing or storing such information in the supplier profile would be a massive security breach and is functionally illogical, as the supplier module only deals with external vendors and their associated business data.

The supplier's historical performance scorecards from prior review periods.

Why it fails: Historical performance scorecards come from performance management projects and are referenced as data, not configured inside a qualification template. Qualification templates define evaluation structure and lifecycle behavior. Embedding historical scorecards would blur the boundary between qualification and performance management, which are separate processes.

The supplier's bank account and remittance details used for payment processing.

Why it fails: Bank account and remittance details are supplier master data, typically maintained in the supplier's registration or financial profile, not in a qualification template. Qualification templates focus on evaluation criteria and lifecycle settings. Including payment data would mix master data governance with qualification logic and is not how the template is structured.

The purchase order approval workflow and spending limits for the supplier's commodity.

Why it fails: Purchase order approval workflows and spending limits belong to procurement and invoicing configuration, not to supplier qualification templates. Qualification templates evaluate supplier capabilities and compliance. Conflating them with purchasing controls would misplace governance responsibilities and is not supported by the qualification template design.

Preferred supplier status assignment rule

Why it fails: Preferred supplier status is an outcome that may follow successful qualification, not a component of the qualification evaluation itself. Assigning preferred status does not evaluate internal requirements or external risk. It is a downstream designation, so including it in the qualification process design does not help the manager assess suppliers against the two categories described.

Supplier registration self-service portal customization

Why it fails: Customizing the registration portal affects how suppliers enter their own data during onboarding. While useful for branding and data capture, it does not evaluate suppliers against internal requirements or external risk factors. The scenario asks for evaluation capabilities within qualification, not for portal presentation changes, so this option does not satisfy the requirement.

Supplier performance scorecard with historical KPI trends

Why it fails: A performance scorecard evaluates a supplier's past delivery against KPIs, which is useful for ongoing performance management but not for initial qualification. New suppliers have no performance history, and the scenario focuses on qualification design rather than post-award performance review. Including it would not address the stated requirement for internal criteria and external risk factors.

A purchase order template pre-populated with the supplier's qualification status.

Why it fails: Purchase order templates govern transactional ordering and do not form part of the qualification process. While qualification status may inform downstream purchasing, embedding it in a PO template does not help evaluate suppliers or record qualification decisions. This is a transactional artifact, not a qualification component, and including it would not support the stated goals of consistent evaluation and traceability.

A sourcing auction configured to run immediately after the supplier submits the qualification questionnaire.

Why it fails: Sourcing auctions are separate from supplier qualification and are used to obtain competitive bids. Qualification determines whether a supplier meets criteria, not whether they win business through an auction. Coupling the two is not required and may even conflict with process design. This element does not contribute to consistent evaluation or decision traceability in the qualification process itself.

A supplier performance scorecard that automatically disqualifies suppliers with low scores.

Why it fails: Performance scorecards evaluate ongoing supplier performance, which is distinct from initial qualification. Automatically disqualifying based on performance conflates two separate processes and is not a standard qualification component. While performance data can inform future decisions, it does not provide the evaluation criteria or decision logic needed to qualify a supplier, so it is not essential to the qualification process design.

A scheduled task in the supplier's registration project that sends a reminder email to the supplier contact.

Why it fails: Reminder tasks only nudge a supplier about work already assigned; they do not decide which questionnaire content applies. If the enhanced module was never added to the project, a reminder cannot create it, so this option addresses follow-up communication rather than risk-based triggering of the questionnaire itself.

A manual approval task assigned to the category manager to confirm the supplier's risk level.

Why it fails: A manual approval task introduces human confirmation but does not automatically select or deliver the enhanced questionnaire. It also depends on the buyer noticing the risk condition, which is precisely the manual effort the program lead wants to remove, so it does not satisfy the automatic triggering requirement.

A supplier-facing preferred status that is set when the supplier completes basic registration.

Why it fails: Preferred status reflects a sourcing or qualification outcome and is not a trigger for questionnaire content. Setting a supplier to preferred after basic registration would not add an enhanced due-diligence module, and it conflates a status label with the rule-based logic needed to detect and respond to risk.

The number of open purchase orders currently issued to the supplier in the SAP Ariba sourcing pipeline.

Why it fails: Open purchase orders reflect transactional activity, not inherent risk. The inherent risk calculation is independent of current order volume; a supplier with many open orders is not automatically riskier. Transactional data may inform reporting or spend analysis, but it does not feed the inherent risk score in the risk engagement.

The supplier's declared annual revenue and employee headcount recorded on the supplier profile.

Why it fails: Revenue and headcount are descriptive profile attributes used for segmentation and reporting, but they are not direct inputs to the inherent risk score. A very large supplier is not inherently riskier than a small one in the model; risk derives from exposure factors such as geography and category, not from company size metrics.

The supplier's preferred status in the supplier master and the date that status was granted.

Why it fails: Preferred status is an internal designation reflecting the buying organization's relationship preference, not an external risk factor. It does not change the supplier's exposure to geopolitical, financial, or operational threats. The inherent risk model deliberately excludes internal relationship labels so that risk reflects objective exposure rather than procurement preferences.

Each supplier must be assigned to exactly one commodity, which then scopes all of its qualifications.

Why it fails: Suppliers are not limited to a single commodity. A supplier can be associated with multiple commodities, and qualification is evaluated per commodity, so a supplier may be qualified in one category and not another. Requiring exactly one commodity would misrepresent how qualification scoping works and would prevent multi-category suppliers from being modeled accurately.

Performance data is stored outside the supplier record and must be manually reconciled to the supplier.

Why it fails: Performance data is associated with the supplier record rather than held in an unlinked store requiring manual reconciliation. Keeping it linked is what enables a unified supplier view and supports lifecycle decisions based on combined qualification and performance evidence. Manual reconciliation would defeat the purpose of an integrated supplier management record and introduce error.

Qualification templates are global objects that cannot be scoped to specific commodities or regions.

Why it fails: Qualification templates can be scoped so that different commodities or regions use different question sets and approval paths. Treating them as strictly global would force every supplier through identical questions regardless of category, which contradicts how qualification is designed. Scoping is precisely what allows a high-risk commodity to demand more evidence than a low-risk one.

Configure the questionnaire to automatically approve all suppliers to speed up onboarding.

Why it fails: Automatic approval bypasses necessary reviews and violates internal policies that require verification. It defeats the purpose of collecting information and ensuring compliance. The manager should not skip approvals, as this could lead to onboarding unqualified or non-compliant suppliers.

Enable the 'Allow Multiple Responses' option to let suppliers submit multiple registrations.

Why it fails: Allowing multiple responses is not typically desired for a single supplier registration, as it can create duplicate records and confusion. This option is used in survey-type questionnaires, not standard supplier registration, and does not align with capturing essential information once per supplier.

Use only open-ended text fields to allow suppliers maximum flexibility in their responses.

Why it fails: While open-ended fields provide flexibility, they are not efficient for capturing structured data like certifications or financial figures. Using only text fields makes analysis and validation difficult. A mix of field types (e.g., dropdowns, dates, numbers) is recommended for accurate and consistent data capture.

The supplier's preferred status in the supplier directory

Why it fails: Preferred status is a directory categorization indicating a buyer's preference, not a risk measurement. It does not feed risk indicators or weights in a risk project, so it has no effect on the computed risk score. Confusing it with a risk input would misstate how exposure is derived.

The count of contract workspaces linked to the supplier

Why it fails: Linked contract workspaces represent existing agreements and their terms. While useful context, the number of contracts is not a scored risk indicator in the risk project calculation and does not alter the supplier's risk score. Treating it as an input would misrepresent the scoring model.

The number of sourcing events the supplier participated in

Why it fails: Sourcing event participation reflects commercial activity, not risk exposure. It is not a defined input to the risk score calculation in a supplier risk project, so including it would not change the supplier's calculated risk. This metric belongs to sourcing analytics, not to supplier risk scoring.

The supplier's preferred status flag set during registration approval

Why it fails: Preferred status reflects a supplier's standing for sourcing and is typically applied after qualification or performance evaluation. It does not determine which qualification process the supplier undergoes. Using preferred status to drive template selection would invert the intended sequence, since qualification generally precedes or contributes to preferred designation.

The supplier's bank account information captured during registration

Why it fails: Bank account details are payment-related attributes and do not influence which qualification template or process is applied. They may be validated during onboarding, but they are not a driver of qualification logic. Using banking data to route qualification would be both incorrect and a potential control weakness.

The sourcing project template used for the supplier's first event invitation

Why it fails: Sourcing project templates govern event structure, bidding rules, and award scenarios, not supplier qualification. While a sourcing event may reference qualified suppliers, the project template itself does not select or configure the qualification process. Relying on it would leave the qualification template assignment unaddressed.

The supplier has completed a performance scorecard for the previous period

Why it fails: Performance scorecards measure historical delivery against metrics and are relevant only after a supplier has been transacting. Requiring a scorecard before onboarding would be impossible for a brand-new supplier with no transaction history, and scorecard completion is not a gate for making a supplier eligible for sourcing or purchase orders.

The supplier has at least one risk alert recorded on its profile

Why it fails: Risk alerts are outputs of monitoring that indicate potential concerns; they are not a requirement for onboarding and would in fact be undesirable. A supplier with no alerts is perfectly usable. Treating the presence of an alert as a prerequisite inverts the purpose of risk monitoring, which exists to flag problems, not to enable eligibility.

The supplier has signed a multi-year master purchasing agreement

Why it fails: A master agreement is a commercial outcome of specific negotiations and is not a precondition for a supplier to be eligible for sourcing events or purchase orders. Many suppliers transact without any master agreement in place, so requiring one at onboarding would block legitimate suppliers and misstate how eligibility actually works.

Buying organization's marketing spend forecast

Why it fails: Marketing spend forecast is unrelated to supplier risk. It does not reflect the supplier's risk profile or exposure. Risk exposure scores are based on supplier-specific data, not on the buying organization's internal marketing plans, so this option is not a valid input.

Supplier's internal employee satisfaction survey results

Why it fails: Employee satisfaction surveys are not a standard data source for supplier risk exposure in SAP Ariba. They are internal to the supplier and not systematically collected or integrated. Risk exposure relies on financial, compliance, and operational data, not on the supplier's internal HR metrics.

Supplier's social media follower count

Why it fails: Social media follower count is not a recognized risk metric in SAP Ariba Supplier Risk. It does not indicate financial, compliance, or operational risk. The system uses structured data from qualifications, external feeds, and internal performance records, not social media popularity.

Sourcing project templates from SAP Ariba Sourcing.

Why it fails: Sourcing project templates are used to manage sourcing events and are unrelated to risk exposure model configuration. They do not provide inherent risk dimensions or mitigation controls. Including them would not contribute to the risk model's calculation of inherent or residual risk, and they are not part of the Supplier Risk configuration.

Supplier registration questionnaires from the supplier onboarding process.

Why it fails: Supplier registration questionnaires collect onboarding data such as company details and certifications. While some data might be used in risk assessment, they are not a component of the risk exposure model configuration. The model requires risk factors and mitigation controls, not registration questionnaires, to compute risk scores.

Supplier performance scorecards from the Supplier Performance Management module.

Why it fails: Performance scorecards are part of Supplier Performance Management and focus on operational metrics like quality and delivery. They are not directly used in risk exposure model configuration in Supplier Risk. While performance can inform risk, the risk exposure model specifically uses risk factors and controls, not performance scorecards, to calculate inherent and residual risk.

Use a qualification questionnaire to collect performance ratings from buyers.

Why it fails: Qualification questionnaires are designed for onboarding and compliance assessment, not for ongoing performance ratings. Using them for performance feedback would conflate qualification with performance management and would not integrate with the scorecard's metric structure. The requirement calls for scorecard metrics, so a qualification questionnaire is the wrong instrument.

Enable supplier self-assessment so the supplier reports its own performance scores.

Why it fails: Supplier self-assessment captures the supplier's own view, not internal stakeholder feedback or objective transactional data. While self-assessment can be useful, it does not fulfill the stated requirement for objective transactional metrics and subjective internal survey input. Relying on it alone would introduce bias and omit the transactional data the manager explicitly wants.

Attach historical sourcing event results as a document to the performance project.

Why it fails: Attaching documents provides reference material but does not create scorecard metrics or collect survey feedback. Historical sourcing results would not automatically populate performance scores, and the attachment would not satisfy the requirement for both transactional and subjective inputs. Scorecard metrics must be configured explicitly to appear in the performance scorecard.

A supplier registration template with mandatory diversity questions

Why it fails: Diversity questions on a registration template collect demographic or certification data, which is unrelated to assigning qualification templates or scheduling performance reviews. While diversity data can inform segmentation values, the template itself does not create the mapping between segmentation and outcomes, so it is not one of the required configuration elements in this scenario.

A preferred supplier designation applied to all tier-one suppliers

Why it fails: Marking suppliers as preferred is a lifecycle status outcome, not a configuration element that drives template assignment or review cadence. Preferred status may result from a qualification decision, but it does not itself define how segmentation influences templates or schedules. Treating it as a required configuration step confuses a status with the rules that produce it.

A background verification integration connected to an external credit bureau

Why it fails: A background verification integration enriches supplier risk data from external sources, but it does not establish how segmentation values map to qualification templates or review frequency. It operates in a different part of the supplier management process. While useful for risk scoring, it is not a prerequisite for segmentation to drive template and review decisions.

Set the supplier's status to 'Preferred' so that they are exempt from future risk assessments.

Why it fails: Marking a supplier as Preferred does not exempt them from risk assessments. Preferred status is a designation for sourcing preference, not a waiver of risk monitoring. This option misrepresents the purpose of the Preferred status and would not achieve the goal of ongoing risk detection.

Manually review each supplier's profile every quarter and update the qualification status by editing the supplier record.

Why it fails: Manual quarterly reviews are not automated and do not leverage scheduled or triggered processes. While manual reviews can be part of a process, the question asks for actions that can be scheduled or triggered. This option is labor-intensive and does not provide the timely detection that automated alerts or recurring questionnaires offer.

Enable automatic approval of all supplier registration requests to reduce cycle time.

Why it fails: Automatic approval of all registrations would bypass necessary vetting and is not a valid configuration for ongoing qualification. It would undermine the control environment and is not a supported mechanism for maintaining qualification validity. This action does not relate to scheduled qualification or risk monitoring.

The supplier's internal organizational chart with employee names

Why it fails: The Supplier 360 profile does not contain internal organizational charts or employee names of the supplier. Such information is proprietary and not typically shared or stored in the buyer's supplier management system. The profile focuses on business-level data relevant to the buyer-supplier relationship, such as certifications and performance metrics.

A list of all sourcing events the supplier has participated in

Why it fails: While sourcing event participation might be referenced in the supplier's history, the Supplier 360 profile does not provide a comprehensive list of all sourcing events. It may show recent awards or contracts, but not the full event history. This information is typically found in sourcing project reports or the supplier's event history, not the 360 profile.

Detailed financial statements from the supplier's last fiscal year

Why it fails: While financial data may be collected during qualification, the Supplier 360 profile does not typically display detailed financial statements. It may show summary metrics or risk scores derived from financial data, but not the full statements. Accessing detailed financials would require navigating to specific documents or external sources, not the Supplier 360 profile.

Number of years the supplier has been in business alone

Why it fails: Years in business may appear in a supplier profile, but it is not a standalone input to the risk exposure calculation in SAP Ariba Supplier Risk. The calculation depends on engagement context and external risk indicators. Longevity alone does not determine exposure, and the product does not use it as a primary risk factor.

Supplier's internal employee satisfaction survey results

Why it fails: Employee satisfaction survey results are not part of SAP Ariba Supplier Risk data inputs. The solution focuses on external risk indicators such as financial, operational, and compliance data, not on a supplier's internal HR metrics. Including this would not align with how risk exposure is calculated in the product.

Supplier's marketing campaign performance metrics

Why it fails: Marketing campaign performance is not a data input for SAP Ariba Supplier Risk. The solution evaluates risk categories such as financial, compliance, and operational risk, not the supplier's marketing effectiveness. Using this metric would not contribute to how the product calculates a supplier's risk exposure.

The supplier's risk score must be calculated before access is granted

Why it fails: Risk score calculation is part of supplier risk management and typically occurs after or alongside qualification, not as a gate for registration questionnaire access. Requiring a risk score before registration would be circular, since much of the data needed for risk assessment comes from the registration itself. This is not a standard prerequisite for supplier access.

The supplier must complete a modular questionnaire before the registration questionnaire

Why it fails: Modular questionnaires are used for incremental data collection after registration or during qualification. They are not a prerequisite for the initial registration questionnaire. Requiring a modular questionnaire first would invert the normal lifecycle and is not how SAP Ariba Supplier Lifecycle and Performance is designed to onboard new suppliers.

The supplier must be assigned to a sourcing category before registration

Why it fails: Sourcing category assignment is used in sourcing and contract processes, not as a prerequisite for registration questionnaire access. A supplier can complete registration without being assigned to a sourcing category. Requiring category assignment before registration would unnecessarily block onboarding and is not part of the standard access setup.