Question 42 of 500
Platform Features and IntegrationhardMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is to implement a queue-based integration using Flow Designer to process updates asynchronously with a controlled rate, because this directly addresses the root cause of the 429 Too Many Requests errors by decoupling the external system from synchronous writes to the REST API. By submitting requests to a queue and processing them server-side at a throttled pace, you prevent overwhelming the /api/now/table/alm_asset endpoint while still updating data as quickly as the instance can handle, effectively solving the rate limiting issue without degrading performance. On the ServiceNow Certified Application Developer CAD exam, this scenario tests your understanding of asynchronous processing patterns and API rate limits—a common trap is choosing to simply increase the API rate limit or batch requests without throttling, which ignores ServiceNow’s platform guardrails. Remember the mnemonic “Queue to Curb the 429”: queuing asynchronous work curbs the flood of requests that triggers the error.

SNOW-CAD Platform Features and Integration Practice Question

This SNOW-CAD practice question tests your understanding of platform features and integration. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A global company is using ServiceNow for IT Service Management. They have an external asset management system that needs to update asset records in ServiceNow in real-time. The integration is implemented using REST API calls from the external system to ServiceNow. Recently, the integration started failing intermittently with HTTP 429 (Too Many Requests) errors. The external system is sending a high volume of update requests (up to 1000 per minute) to the /api/now/table/alm_asset endpoint. The administrator noticed that the instance performance is degraded during peak times. The company wants to resolve the 429 errors while ensuring data is updated as quickly as possible, but without overloading the instance. Which course of action should the administrator take?

Question 1hardmultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Implement a queue-based integration using Flow Designer to process updates asynchronously with a controlled rate.

Option C is correct because it addresses the root cause of the 429 errors—overwhelming the REST API endpoint with synchronous requests—by decoupling the external system from direct writes. Using Flow Designer with a queue (e.g., via the ServiceNow Queue or a custom table) allows the external system to submit requests asynchronously, and then a scheduled flow or script processes them at a controlled rate (e.g., using a rate limiter or batch size). This ensures data is updated as quickly as possible without exceeding the instance's API rate limits or degrading performance, as the processing is throttled server-side.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Increase the API rate limit in the instance's system properties.

    Why it's wrong here

    Increasing rate limit may worsen performance and cause instability.

  • Reduce the number of requests from the external system to 500 per minute.

    Why it's wrong here

    The external system may not be able to reduce its rate, and 500 might still be too high.

  • Implement a queue-based integration using Flow Designer to process updates asynchronously with a controlled rate.

    Why this is correct

    Queuing allows decoupling and rate control, preventing 429 errors.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Switch the authentication method from basic to OAuth to reduce overhead.

    Why it's wrong here

    Authentication method does not affect rate limiting.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often assume increasing rate limits (Option A) or reducing external request volume (Option B) are sufficient fixes, but they overlook the need for a controlled, asynchronous processing pattern to prevent instance degradation while maintaining near-real-time updates.

Detailed technical explanation

How to think about this question

Under the hood, ServiceNow's REST API rate limiting is enforced by the 'glide.rest.api.rate_limit' system property (default 40 requests per second per user), and hitting this limit triggers a 429 response. A queue-based integration using Flow Designer can leverage the 'sn_fd_queue' table or a custom 'Queue' record, where the external system inserts a record via a lightweight REST call (e.g., to a custom scripted REST API that just queues the data), and a scheduled Flow or Business Rule processes the queue in batches (e.g., 50 records every 10 seconds) using GlideRecord updates, thus smoothing the load and preventing spikes. In real-world scenarios, this pattern is critical for high-volume integrations like CMDB syncs or asset updates from IoT systems, where burst traffic can easily overwhelm default limits.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the SNOW-CAD exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related SNOW-CAD practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SNOW-CAD practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this SNOW-CAD question test?

Platform Features and Integration — This question tests Platform Features and Integration — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Implement a queue-based integration using Flow Designer to process updates asynchronously with a controlled rate. — Option C is correct because it addresses the root cause of the 429 errors—overwhelming the REST API endpoint with synchronous requests—by decoupling the external system from direct writes. Using Flow Designer with a queue (e.g., via the ServiceNow Queue or a custom table) allows the external system to submit requests asynchronously, and then a scheduled flow or script processes them at a controlled rate (e.g., using a rate limiter or batch size). This ensures data is updated as quickly as possible without exceeding the instance's API rate limits or degrading performance, as the processing is throttled server-side.

What should I do if I get this SNOW-CAD question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This SNOW-CAD practice question is part of Courseiva's free ServiceNow certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SNOW-CAD exam.