<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Raj Cloud Technologies on Medium]]></title>
        <description><![CDATA[Stories by Raj Cloud Technologies on Medium]]></description>
        <link>https://medium.com/@rajcloudtechnologies?source=rss-1f9b764f982c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*DIq-qvN3obKg9BW6</url>
            <title>Stories by Raj Cloud Technologies on Medium</title>
            <link>https://medium.com/@rajcloudtechnologies?source=rss-1f9b764f982c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:51:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rajcloudtechnologies/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Top 25 Real-Time Snowflake Realtime Interview Questions — Managerial Round (2nd Round) — 2027]]></title>
            <link>https://rajcloudtechnologies.medium.com/top-25-real-time-snowflake-realtime-interview-questions-managerial-round-2nd-round-2027-c5e524b2bec5?source=rss-1f9b764f982c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5e524b2bec5</guid>
            <category><![CDATA[interview-questions]]></category>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[snowflake]]></category>
            <category><![CDATA[dbt]]></category>
            <category><![CDATA[data-engineering]]></category>
            <dc:creator><![CDATA[Raj Cloud Technologies]]></dc:creator>
            <pubDate>Sat, 14 Nov 2026 18:27:49 GMT</pubDate>
            <atom:updated>2026-11-14T18:29:42.436Z</atom:updated>
            <content:encoded><![CDATA[<p>Top 25 Real-Time Snowflake Realtime Interview Questions — Managerial Round (2nd Round) — 2027</p><p>1. Explain your current Snowflake project architecture end to end. <br>2. Explain one of the most challenging issues you faced in your Snowflake project. How did you resolve it?<br>3. Suppose your daily ETL pipeline, which normally takes 30 minutes, suddenly starts taking 3 hours. How would you investigate and resolve the issue?<br>4. Have you ever handled a production failure in Snowflake? Explain the complete incident-resolution process.<br>5. Suppose you receive duplicate records from the source system every day. How would you implement an incremental load without creating duplicates?<br>6. Your source system sends 10 million records daily, but one day only 6 million records are loaded into Snowflake. How would you identify the missing 4 million records?<br>7. Have you implemented SCD Type 1 and Type 2 in a real-time project? Explain the business scenario and implementation.<br>8. Suppose a business user reports that the dashboard is showing incorrect data even though the Snowflake pipeline completed successfully. How would you investigate?<br>9. Explain how you have implemented Snowflake Streams and Tasks in your project. What happens if a Task fails?<br>10. Suppose your Snowflake warehouse cost increases by 40% compared with the previous month. How would you identify and reduce unnecessary costs?<br>11. How do you handle late-arriving data in Snowflake when previous days’ data has already been processed?<br>12. Suppose the source team adds new columns or changes the existing data type. How would you handle schema evolution without breaking your Snowflake pipeline?<br>13. Have you worked on any data migration project from an existing database or data warehouse to Snowflake? Explain your migration strategy.<br>14. How do you implement role-based access control (RBAC) and secure sensitive data in a Snowflake project?<br>15. Suppose you have multiple production issues and two critical development tasks assigned to you on the same day. How would you prioritize and manage them?<br>16. If your manager gives you a completely new business requirement to build a Snowflake data pipeline, how would you approach it from requirement gathering to production deployment?<br>17. Have you ever disagreed with a technical lead, architect, or business analyst regarding a proposed solution? How did you handle the situation?<br>18. Suppose management wants faster pipeline execution, but increasing the Snowflake warehouse size will significantly increase costs. How would you balance performance and cost?<br>19. Explain your experience deploying Snowflake code from development to testing and production environments.<br>20. If a junior developer in your team introduces incorrect transformation logic that impacts production reporting, how would you handle the situation?<br>21. What is the biggest contribution you made to your current project? Explain what you personally developed rather than what your team delivered.<br>22. How much data are you processing daily? Be prepared with approximate data volumes, number of tables, file sizes, execution times, and warehouse sizes.<br>23. What would you improve in your current Snowflake architecture if you had the opportunity?<br>24. If you are assigned a requirement with an aggressive deadline, how would you ensure delivery without compromising data quality?<br>25. Why are you looking for a change, and what responsibilities are you expecting in your next organization?</p><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>🚀 <strong>Preparing for your next Snowflake Data Engineer interview?</strong></p><p>Clearing the first technical round is just one step. The real challenge is demonstrating your ability to handle production issues, troubleshoot complex data pipelines, optimize performance, manage costs, and take ownership of real-time projects.</p><p>📌 <strong>Save these 25 Managerial Round Interview Questions</strong> and prepare with real-time project scenarios before attending your next interview.</p><p>At <strong>Raj Cloud Technologies</strong>, we focus on practical, job-oriented training that helps professionals build confidence in real-world project requirements and technical interviews.</p><p>💬 <strong>How many of these questions can you confidently answer based on your project experience?</strong> Share your answer in the comments!</p><p>🔔 Follow <strong>Raj Cloud Technologies</strong> for more:</p><p>Real-time interview questions</p><p>Snowflake, dbt &amp; Azure Data Engineering</p><p>ADF with Cortex AI</p><p>Project-based technical discussions</p><p>Interview preparation by experienced trainers</p><p>📞 Contact: 9380487284<br>🌐 <a href="https://rajcloudtech.com/">https://rajcloudtech.com</a></p><p><strong>Learn practically. Build confidently. Grow professionally.</strong></p><p>#Snowflake #SnowflakeInterviewQuestions #SnowflakeDeveloper #SnowflakeDataEngineer #ManagerialRound #DataEngineering #DBT #AzureDataFactory #CortexAI #RealTimeProjects #InterviewPreparation #RajCloudTechnologies</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5e524b2bec5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Prevent Duplicate Records in ServiceNow Using Business Rules — Real-Time Project Scenario]]></title>
            <link>https://rajcloudtechnologies.medium.com/how-to-prevent-duplicate-records-in-servicenow-using-business-rules-real-time-project-scenario-70153b4c7c47?source=rss-1f9b764f982c------2</link>
            <guid isPermaLink="false">https://medium.com/p/70153b4c7c47</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[it-service-management]]></category>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Raj Cloud Technologies]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 09:17:16 GMT</pubDate>
            <atom:updated>2026-11-09T09:17:16.492Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>A practical ServiceNow Developer guide with GlideRecord examples, troubleshooting techniques, and interview insights.</strong></p><h3>Introduction</h3><p>Have you ever faced a situation where a single incident update creates multiple records in a custom ServiceNow table?</p><p>This is a common type of production issue that ServiceNow Developers may encounter when working with Business Rules, GlideRecord, and automated record creation.</p><p>Duplicate records can lead to incorrect reporting, unnecessary database operations, data inconsistencies, and operational challenges.</p><p>In this article, let’s understand how to identify the root cause and implement a reliable solution using ServiceNow Business Rules and GlideRecord.</p><h3>1. Understanding the Real-Time Scenario</h3><p>Imagine you are working as a ServiceNow ITSM Developer in an enterprise environment.</p><p>Your organization has a requirement:</p><p>Whenever an incident is resolved, the system should automatically create a corresponding record in a custom table for reporting and tracking purposes.</p><p>You develop an After Update Business Rule on the Incident table.</p><p>During testing, you notice that updating the incident multiple times creates duplicate records in the custom table.</p><p><strong>The business raises the following concern:</strong></p><p>“Why is ServiceNow creating multiple records for a single incident, and how can we prevent this?”</p><p>Let’s explore the solution.</p><h3>2. Why Do Duplicate Records Occur?</h3><p>Some common reasons include:</p><ul><li>Business Rules executing without appropriate conditions.</li><li>Multiple updates triggering the same logic.</li><li>Unnecessary current.update() calls inside Business Rules.</li><li>Missing duplicate validation before inserting records.</li><li>Multiple automation mechanisms creating the same record.</li><li>Concurrent transactions attempting to insert identical records.</li></ul><p>Identifying the actual cause is the first step before changing the implementation.</p><h3>3. Solution 1: Configure Appropriate Business Rule Conditions</h3><p>Instead of executing the Business Rule every time an incident is updated, restrict execution to the required state transition.</p><p>For example, execute the logic only when the incident moves to the Resolved state.</p><pre>if (current.state.changesTo(6)) {<br>    // Execute required logic<br>}</pre><p>This prevents the logic from running for unrelated updates.</p><p>Note: Verify the Resolved choice value in your ServiceNow instance.</p><h3>4. Solution 2: Check Whether a Record Already Exists Using GlideRecord</h3><p>Before inserting a record into the custom table, query the table to check whether a record already exists for the incident.</p><p>Example:</p><pre>var gr = new GlideRecord(&#39;u_custom_table&#39;);</pre><pre>gr.addQuery(&#39;u_incident&#39;, current.sys_id);<br>gr.setLimit(1);<br>gr.query();</pre><pre>if (!gr.next()) {</pre><pre>    var rec = new GlideRecord(&#39;u_custom_table&#39;);<br>    rec.initialize();</pre><pre>    rec.u_incident = current.sys_id;<br>    rec.insert();</pre><pre>}</pre><p><strong>How does this work?</strong></p><ol><li>GlideRecord accesses the custom table.</li><li>addQuery() filters records using the Incident reference.</li><li>query() executes the database query.</li><li>next() checks whether a matching record exists.</li><li>If no matching record is found, a new record is inserted.</li></ol><p>This provides basic duplicate checking.</p><h3>5. Solution 3: Follow Business Rule Best Practices</h3><p>A few important practices can help avoid unnecessary executions:</p><ul><li>Use appropriate Business Rule conditions.</li><li>Avoid unnecessary current.update() calls inside Before Business Rules.</li><li>Use changes() and changesTo() to detect relevant field changes.</li><li>Avoid duplicate automation across multiple Business Rules and Flows.</li><li>Use appropriate logging for troubleshooting.</li><li>Test different incident update scenarios.</li></ul><h3>6. Important Production-Level Consideration</h3><p>One important point that experienced ServiceNow Developers should understand is that checking for an existing record before insertion does not guarantee duplicate prevention under concurrent transactions.</p><p>For example, two transactions might check the table simultaneously, both find no matching record, and both attempt to insert.</p><p>For critical duplicate-prevention requirements, consider enforcing uniqueness at the database level using an appropriate unique index on the identifying field or combination of fields.</p><p>Also, make the insertion logic idempotent so repeated executions do not create additional records.</p><h3>7. Real-Time ServiceNow Interview Question</h3><p><strong>Question: How do you prevent duplicate records using Business Rules in ServiceNow?</strong></p><p><strong>Interview-ready answer:</strong></p><p>“In ServiceNow, I prevent duplicate records by first identifying why the Business Rule is executing multiple times.</p><p>I configure appropriate conditions so that the Business Rule runs only when the required field changes.</p><p>Before inserting a new record, I use GlideRecord to check whether a matching record already exists in the target table.</p><p>If a record exists, I skip the insertion. Otherwise, I create the new record.</p><p>I also avoid unnecessary current.update() calls inside Before Business Rules and consider database-level uniqueness constraints for critical scenarios involving concurrent transactions.</p><p>Finally, I test the implementation with multiple updates and concurrent execution scenarios to ensure data consistency.”</p><h3>8. Key Takeaways</h3><p>Preventing duplicate records is not just about writing a GlideRecord query. It requires understanding Business Rule execution, database operations, transaction behavior, and proper development practices.</p><p>As a ServiceNow Developer, always focus on:</p><ul><li>Writing efficient Business Rules.</li><li>Understanding GlideRecord operations.</li><li>Preventing unnecessary database updates.</li><li>Implementing reliable duplicate prevention.</li><li>Maintaining data integrity in production environments.</li></ul><p><strong>The best ServiceNow solutions are not just functional; they are scalable, maintainable, and reliable.</strong></p><h3>Learn ServiceNow ITSM with Raj Cloud Technologies</h3><p>Want to develop practical expertise in ServiceNow ITSM and real-time development?</p><p>Raj Cloud Technologies provides industry-oriented training and interview preparation covering:</p><ul><li>ServiceNow ITSM, ITOM and CSM</li><li>Business Rules and Client Scripts</li><li>GlideRecord and GlideAjax</li><li>Script Includes and Flow Designer</li><li>Service Catalog and CMDB</li><li>Real-time project scenarios and interview preparation</li></ul><p>📍 ServiceNow Training in Bangalore and Hyderabad</p><p>⭐ 4.9/5 Google Rating | 1,546 Reviews</p><p>🌐 <a href="https://rajcloudtech.com/">https://rajcloudtech.com/</a></p><p>📞 9380487284</p><p><strong>Learn Practically. Build Real-Time Skills. Grow Your IT Career with Raj Cloud Technologies.</strong></p><p>#ServiceNow #ServiceNowDeveloper #ServiceNowITSM #BusinessRules #GlideRecord #ServiceNowInterviewQuestions #ITSM #RajCloudTechnologies</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70153b4c7c47" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>