Online Access Free E_C4HYCP_12 Practice Test

You enable the automatic reset in the Backoffice Framework configuration.When is the reset triggered?Note: There are 2 correct answers to this question.

• A.After you logout
• B.On the next server startup
• C.After you login again
• D.After the next compilation

Where can you find SAP knowledge base articles (KBAs) to search for known issues?Note: There are 2 correct answers to this question.

• A.SAP ONE Support Launchpad
• B.SAP Support Portal
• C.SAP Help Portal
• D.SAP Community

You are deploying the OAuth2 user credentials in SAP Cloud Integration.Where do you configure the OAuth Client data?

• A.SAP Commerce Backoffice|SAP Cloud Integration Web UI
• B.SAP BTP cockpit|SAP Cloud Integration Web UI
• C.SAP Commerce Backoffice|Administration Console
• D.SAP BTP cockpit|SAP Commerce Backoffice

A customer reports an error and provides the following snippet of a log file:INFO | jvm 1 | srvmain
| 2013/11/15 21:36:38.829 | ERROR [ImpExWorker<1/4>] (000000RS-ImpEx-Import) [MultiThreadedImpExImportReader] line 11 at main script: worker 1 got error com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint
'PK 3819157796645776366'. Cannot insert duplicate key in object 'dbo.users'. The duplicate key value is (8796126019588).INFO | jvm 1 | srvmain | 2013/11/15 21:36:38.876 | de.hybris.platform.jalo.JaloSystemException: com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK 3819157796645776366'. Cannot insert duplicate key in object 'dbo.users'. The duplicate key value is (8796126019588).[HY--1]What could be the root cause of the error?Note: There are 2 correct answers to this question.

• A.A primary key is used in the database instead of a unique index.
• B.The current PK sequence value is corrupt.
• C.The database engine verifies that the key is NOT unique and reports an exception
• D.SAP Commerce verifies that the key is NOT unique and reports an exception.

A customer reports a performance problem with DefaultStockService. After checking the customer's system by running SELECT COUNT(*) FROM {StockLevelHistoryEntry}, you discover that there are hundreds of millions of instances of StockLevelHistoryEntry.What would you do to resolve this performance issue?Note: There are 2 correct answers to this question.

• A.Run Cleanup Type System in the SAP Commerce Administration Console.
• B.Delete the content of the StockLevelHistoryEntry table directly from the database to immediately improve performance.
• C.Implement a CronJob that will clean the StockLevelHistoryEntry table according to customer business needs.
• D.Suggest an improvement by creating a maintenance request for the customer.