Full questions with full answers — no sign-in required.
hardCross-Module Integration and Non-Functional Architecture
1. You are the lead architect for a multi-country cutover where testing evidence shows regression failures in tax calculation for two countries just 48 hours before the planned go-live weekend. How would you architecturally approach the go/no-go decision and mitigation?
Convene an emergency go/no-go review using pre-defined exit criteria: isolate whether the defect is scoped to specific countries or a global object, assess business impact (statutory filing risk vs workaround feasibility), and evaluate rollback cost versus partial go-live (excluding affected countries into a later wave). Decide based on data, not schedule pressure, and if proceeding, define a manual workaround and fast-track fix plan with defined SLA before those countries' next tax filing deadline.
hardCross-Module Integration and Non-Functional Architecture
2. You are asked to define a reference architecture for a multi-country S/4HANA rollout spanning ECC-integrated legacy subsidiaries and greenfield S/4HANA entities. What core architectural patterns would you include?
I would define a common data model and master data governance layer (e.g. centralized MDG) to keep legacy ECC and S/4HANA entities consistent, an integration layer using SAP Integration Suite or middleware for coexistence during phased rollout, and a template-based core model with country-specific localization layers kept outside the clean core. I would include a phased rollout sequencing plan by country/entity, a shared BTP extension layer for cross-entity custom logic, and clearly defined interfaces for financial consolidation across both ECC and S/4HANA entities during transition.
mediumCross-Module Integration and Non-Functional Architecture
3. Your organization needs to expose a set of S/4HANA business APIs to multiple non-SAP consumer applications with varying authentication and throttling needs. How would you architect the API management layer?
Front the S/4HANA OData/REST APIs with SAP API Management (part of Integration Suite) to centralize authentication (OAuth2 client credentials or SAML bearer assertion depending on consumer type), apply per-consumer rate limiting and quota policies, and version APIs so breaking changes don't disrupt existing non-SAP consumers. Use API proxies to transform payloads where consumers require different formats, and enable centralized logging/analytics for usage monitoring and chargeback. Avoid exposing raw backend endpoints directly to external consumers to maintain a governed access layer.
hardCross-Module Integration and Non-Functional Architecture
4. Describe a typical landscape pattern for an S/4HANA Private Cloud deployment on a hyperscaler, including how DEV, QA, and PROD systems interact with BTP services and identity providers.
A common pattern has separate DEV, QA, PROD system groups on the hyperscaler (via RISE or customer-managed), each with corresponding BTP subaccounts mirroring the landscape stage, connected through Cloud Connector for on-premise-style integration or direct connectivity for private cloud. Identity Authentication Service federates with corporate IdP for SSO across stages. Transport of ABAP changes flows through the classic three-system landscape, while BTP-side extensions use their own CI/CD pipelines, requiring coordinated release management between the two tracks.
mediumCross-Module Integration and Non-Functional Architecture
5. During Fit-to-Standard workshops using Signavio process models, the business insists on retaining a legacy custom approval workflow that conflicts with S/4HANA standard. How do you handle this as the architect facilitating testing strategy?
I'd document the gap in the fit-gap log with business justification and quantify the cost of customization versus standard adoption, including impact on future upgrades and test scope. I'd propose a workshop to explore configuration-only alternatives (e.g., flexible workflow via Business Workflow or Fiori app extensibility) before agreeing to a custom build. If customization is approved, it gets flagged as a delta requiring dedicated test scripts in the testing strategy and regression coverage for every future release cycle.
mediumCross-Module Integration and Non-Functional Architecture
6. Your organization is moving from a project-based delivery model to a permanent product-based support model after S/4HANA go-live. How would you design the production operating model using Signavio for process governance?
Define product teams aligned to business capabilities (e.g., Order-to-Cash, Record-to-Report) each owning a set of processes, with Signavio process models serving as the single source of truth for as-built process documentation. Establish a RACI linking process owners, product owners, and support teams, and require any change request to reference the affected Signavio process model so impact is assessed before implementation. Set up a governance cadence for process model updates tied to release cycles.
