SAP Cloud Connector (SCC) plays a crucial role in integrating on-premise systems with SAP BTP (Business Technology Platform). If you’re preparing for an interview, here are some essential questions and answers to help you ace it!
1️⃣ What is SAP Cloud Connector (SCC)?
✅ Answer: SAP Cloud Connector is a lightweight application that creates a secure tunnel between SAP BTP and on-premise systems, enabling seamless connectivity without exposing internal networks.
2️⃣ How does SCC ensure security in communication?
✅ Answer: SCC uses mutual authentication, TLS encryption, IP whitelisting, and role-based access control to secure communication between SAP BTP and on-premise systems.
3️⃣ What are the main features of SAP Cloud Connector?
✅ Answer:
• Secure tunnel for hybrid cloud connectivity
• Role-based authorization and access control
• HTTP and RFC protocol support
• Logging and monitoring capabilities
• High availability setup
4️⃣ What are the deployment models of SAP Cloud Connector?
✅ Answer: SCC supports both standalone and high-availability (HA) deployment models. HA ensures failover capability, minimizing downtime.
5️⃣ How do you troubleshoot connectivity issues in SAP Cloud Connector?
✅ Answer:
• Check the status of SCC in the administration panel.
• Verify the cloud-to-on-premise mappings and logs.
• Ensure firewall and proxy settings allow communication.
• Use diagnostic tools like ping and telnet.
6️⃣ What are the prerequisites for setting up SAP Cloud Connector?
✅ Answer:
• A supported OS (Windows/Linux)
• Java Runtime Environment (JRE)
• SAP BTP subaccount credentials
• Necessary firewall and network settings
7️⃣ Can multiple SAP Cloud Connectors be connected to a single SAP BTP subaccount?
✅ Answer: Yes, multiple SCC instances can be connected for load balancing and redundancy, ensuring high availability.
8️⃣ What is Principal Propagation in SAP Cloud Connector?
✅ Answer: Principal Propagation ensures that user identities from SAP BTP are maintained when accessing on-premise systems, allowing secure and role-based access control.
0 Comments