Scenario practice questions

A buying organization has configured a modular questionnaire in SAP Ariba Supplier Management. During a qualification project, the internal category manager needs to provide an assessment of the supplier's technical capabilities. The category manager is not a supplier user and does not have a supplier account. Which type of questionnaire should be used to collect this internal feedback?

Trap 1: Modular questionnaire template

A modular questionnaire template is a reusable structure that can be used to create both internal and external questionnaires. It is not a type of questionnaire itself. The category manager needs a specific questionnaire type that supports internal respondents, not just a template.

Trap 2: External questionnaire

An external questionnaire is intended for suppliers or other external parties to complete. It is typically sent to a supplier contact who logs in to the SAP Ariba supplier portal. Since the category manager is internal and has no supplier account, an external questionnaire would not be appropriate for collecting this feedback.

Trap 3: Registration questionnaire

A registration questionnaire is part of the supplier registration process and is used to collect information from prospective suppliers when they first register. It is not designed for internal stakeholders to provide assessments of an existing supplier's capabilities during a qualification project.

A
Modular questionnaire template
Why it fails: A modular questionnaire template is a reusable structure that can be used to create both internal and external questionnaires. It is not a type of questionnaire itself. The category manager needs a specific questionnaire type that supports internal respondents, not just a template.
B
External questionnaire
Why it fails: An external questionnaire is intended for suppliers or other external parties to complete. It is typically sent to a supplier contact who logs in to the SAP Ariba supplier portal. Since the category manager is internal and has no supplier account, an external questionnaire would not be appropriate for collecting this feedback.
C
Registration questionnaire
Why it fails: A registration questionnaire is part of the supplier registration process and is used to collect information from prospective suppliers when they first register. It is not designed for internal stakeholders to provide assessments of an existing supplier's capabilities during a qualification project.
D
Internal questionnaire
An internal questionnaire is designed to be completed by internal stakeholders, such as category managers or other employees, who do not have supplier user accounts. It allows the buying organization to gather assessments and feedback from within the company as part of the qualification or performance management process.

Question 2mediummultiple choice

A buying organization runs a modular questionnaire during supplier registration. The template includes a 'Business License Number' question of type 'Text'. A supplier enters a value that does not match the required alphanumeric pattern, yet the registration still submits successfully. The template designer needs to block submission until the format is correct. Which configuration should the designer apply to the question?

Trap 1: Mark the question as 'Internal Only' so suppliers cannot see or…

'Internal Only' hides the question from suppliers and prevents their input, which conflicts with the need to collect the license number from the supplier. It also provides no format enforcement. This setting is used for buyer-side notes or scoring, not for validating supplier-provided data, so it fails the scenario's requirement entirely.

Trap 2: Change the question type to 'Attachment' so the supplier uploads a…

Changing to 'Attachment' removes the text entry and instead asks for a file, which does not enforce a format on a license number. This does not solve the requirement to validate the alphanumeric pattern at submission. The scenario specifically needs format validation on a text value, so an attachment type is inappropriate and would not block an incorrectly formatted entry.

Trap 3: Enable 'Allow Multiple Responses' on the question to let the…

'Allow Multiple Responses' permits repeated answers but does not validate the format of any response. The supplier could still submit an invalid license number. This option addresses response multiplicity, not data validation, and therefore does not prevent submission of a malformed value. It is unrelated to regex or format enforcement in modular questionnaires.

A
Mark the question as 'Internal Only' so suppliers cannot see or edit it.
Why it fails: 'Internal Only' hides the question from suppliers and prevents their input, which conflicts with the need to collect the license number from the supplier. It also provides no format enforcement. This setting is used for buyer-side notes or scoring, not for validating supplier-provided data, so it fails the scenario's requirement entirely.
B
Change the question type to 'Attachment' so the supplier uploads a scanned copy of the license.
Why it fails: Changing to 'Attachment' removes the text entry and instead asks for a file, which does not enforce a format on a license number. This does not solve the requirement to validate the alphanumeric pattern at submission. The scenario specifically needs format validation on a text value, so an attachment type is inappropriate and would not block an incorrectly formatted entry.
C
Enable 'Allow Multiple Responses' on the question to let the supplier correct the value later.
Why it fails: 'Allow Multiple Responses' permits repeated answers but does not validate the format of any response. The supplier could still submit an invalid license number. This option addresses response multiplicity, not data validation, and therefore does not prevent submission of a malformed value. It is unrelated to regex or format enforcement in modular questionnaires.
D
Set the question as Required and add a validation rule using a regular expression (regex) pattern.
Required ensures the field is populated, and a regex validation rule enforces the exact alphanumeric format so the supplier cannot submit until the value matches. This directly addresses the scenario where an incorrectly formatted license number was accepted. In SAP Ariba Supplier Management, modular questionnaire questions support validation rules, including regex patterns, making this the correct configuration.

Question 3hardmultiple choice

A category manager is building a qualification process for a new region. The process must require suppliers to submit a valid ISO 9001 certificate, and the supplier must not be able to submit the questionnaire until the certificate file is uploaded. The category manager also wants the certificate to expire automatically after 12 months so the supplier is prompted to renew. Which combination of configuration elements should the manager use?

Trap 1: A free-text question asking the supplier to type the certificate…

A free-text question cannot enforce that an actual certificate file is uploaded, so a supplier could type any number and proceed. A reminder task also depends on someone manually configuring and maintaining it and does not automatically invalidate the certificate. This approach fails the requirement that submission be blocked until the file exists and that the certificate expire on its own.

Trap 2: A supplier registration template with a document question and a…

Registration templates apply to onboarding new suppliers, not to a qualification process for an existing region, and a background verification integration checks third-party data rather than enforcing an uploaded certificate. Neither element gates questionnaire submission on the attachment nor manages a 12-month document expiry, so the requirement would not be satisfied.

Trap 3: A supplier qualification template with a mandatory approval task…

An approval task controls internal review after submission; it does not force the supplier to attach a file before submitting. It also does not create an automatic expiration on the document. While approvals are useful in qualification, they address a different control point and leave both the gating and the 12-month expiry requirement unmet in this scenario.

A
A free-text question asking the supplier to type the certificate number, plus a reminder task scheduled 12 months out
Why it fails: A free-text question cannot enforce that an actual certificate file is uploaded, so a supplier could type any number and proceed. A reminder task also depends on someone manually configuring and maintaining it and does not automatically invalidate the certificate. This approach fails the requirement that submission be blocked until the file exists and that the certificate expire on its own.
B
A supplier registration template with a document question and a background verification integration
Why it fails: Registration templates apply to onboarding new suppliers, not to a qualification process for an existing region, and a background verification integration checks third-party data rather than enforcing an uploaded certificate. Neither element gates questionnaire submission on the attachment nor manages a 12-month document expiry, so the requirement would not be satisfied.
C
A supplier qualification template with a mandatory approval task assigned to the category manager
Why it fails: An approval task controls internal review after submission; it does not force the supplier to attach a file before submitting. It also does not create an automatic expiration on the document. While approvals are useful in qualification, they address a different control point and leave both the gating and the 12-month expiry requirement unmet in this scenario.
D
A required attachment question with an expiration date, and a prerequisite condition that gates the questionnaire
A required attachment question enforces that the ISO 9001 file must be uploaded before submission, and the expiration date field causes the system to flag the document as expired after 12 months. A prerequisite condition on the questionnaire prevents the supplier from proceeding until that attachment is provided. Together these three elements satisfy both the gating requirement and the renewal prompt.

Question 4mediummultiple choice

Why should an administrator use 'Process Projects' instead of simple registration projects for high-risk, complex supplier onboarding?

Trap 1: They allow for unlimited storage of supplier documents.

While they do manage documents, the storage capacity is determined by the Ariba subscription, not the project type. The main advantage of process projects is their workflow orchestration capability, not their storage limits. Relying on storage limits as a justification for process choice is an incorrect understanding of Ariba's architecture and features.

Trap 2: They are the only projects that can be synced with an ERP system.

Standard registration projects can also be integrated with ERP systems. The sync capability is a function of the system configuration and master data integration settings, not a unique feature of process projects. Limiting the definition of process projects to this single function is incorrect and ignores their primary value in workflow orchestration.

Trap 3: They automatically lower the supplier's risk score in the dashboard.

There is no mechanism that automatically lowers a risk score simply by choosing a different project type. Risk scores are based on the data collected and the outcomes of the assessment tasks. Process projects improve the rigour of the assessment, which helps in managing risk, but they do not artificially manipulate the metrics.

A
They allow for unlimited storage of supplier documents.
Why it fails: While they do manage documents, the storage capacity is determined by the Ariba subscription, not the project type. The main advantage of process projects is their workflow orchestration capability, not their storage limits. Relying on storage limits as a justification for process choice is an incorrect understanding of Ariba's architecture and features.
B
They provide advanced orchestration and dependency management for complex workflows.
Process projects are designed for flexibility and complexity. They enable administrators to define intricate workflows with task dependencies, where the completion of one phase (e.g., risk assessment) triggers the next (e.g., contract negotiation). This is crucial for high-risk suppliers where standard registration processes do not provide sufficient rigor or oversight.
C
They are the only projects that can be synced with an ERP system.
Why it fails: Standard registration projects can also be integrated with ERP systems. The sync capability is a function of the system configuration and master data integration settings, not a unique feature of process projects. Limiting the definition of process projects to this single function is incorrect and ignores their primary value in workflow orchestration.
D
They automatically lower the supplier's risk score in the dashboard.
Why it fails: There is no mechanism that automatically lowers a risk score simply by choosing a different project type. Risk scores are based on the data collected and the outcomes of the assessment tasks. Process projects improve the rigour of the assessment, which helps in managing risk, but they do not artificially manipulate the metrics.

Question 5hardmultiple choice

Refer to the exhibit. What is the current status of the overall supplier qualification process based on the displayed tasks?

Exhibit

Task Name | Status | Owner | Due Date
--------------------------------------------
Doc Review | Pending | John Doe | 2023-10-01
Tax Vetting | Approved | System | N/A
Risk Check | Overdue | Sarah Smith | 2023-09-15

Trap 1: The process is complete.

The process cannot be considered complete while a task remains 'Overdue'. Since the 'Risk Check' task has not been finalized and is currently past its deadline, the overall qualification workflow is still active and waiting on manual intervention to move to the next stage of the lifecycle.

Trap 2: The process will automatically complete tomorrow.

There is no mechanism in SAP Ariba that automatically completes tasks just because time has passed. Overdue tasks require active participation from the assigned owner to provide the necessary approvals or information, as they represent a failure to meet the scheduled project timeline defined in the template.

Trap 3: The process is cancelled.

An overdue task does not imply cancellation. The project remains in an active state, just delayed. Cancellation would require an explicit action by a project manager to stop the workflow, which is not indicated by the current task status list provided in the exhibit.

A
The process is complete.
Why it fails: The process cannot be considered complete while a task remains 'Overdue'. Since the 'Risk Check' task has not been finalized and is currently past its deadline, the overall qualification workflow is still active and waiting on manual intervention to move to the next stage of the lifecycle.
B
The process is blocked due to an overdue task.
An overdue task in a qualification workflow signifies that a critical step has not been finished. Since the 'Risk Check' is mandatory for qualification, the entire process is effectively blocked. The owner must complete the task before the system can transition the supplier's status to fully 'Qualified'.
C
The process will automatically complete tomorrow.
Why it fails: There is no mechanism in SAP Ariba that automatically completes tasks just because time has passed. Overdue tasks require active participation from the assigned owner to provide the necessary approvals or information, as they represent a failure to meet the scheduled project timeline defined in the template.
D
The process is cancelled.
Why it fails: An overdue task does not imply cancellation. The project remains in an active state, just delayed. Cancellation would require an explicit action by a project manager to stop the workflow, which is not indicated by the current task status list provided in the exhibit.