C is the correct answer.
Customizations captured in update sets are restricted to the scope for the application being changed. A scope may contain several update sets, but an update set cannot cross application scopes. Consequently, an update set name could appear identical in more than one scope, but is actually different (due to the namespace), a consideration for the naming policy.
Changes made within a named Update Set in a different application scope are not captured because each application scope in ServiceNow is designed to be a separate and isolated environment.
"1. Limitations of update sets: The biggest limitation is that an update set cannot capture updates across the different application scopes. In order to capture updates across different application scopes, you need to create multiple update sets catering to each application scope."
A is the correct answer.
The change is indeed captured by ServiceNow, even though it may be in a separate Update Set due to scope differences. The question likely aims to assess whether the change is tracked at all, rather than the specifics of how it's managed across scopes (batches and children)
upvoted 3 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
zensailorman
Highly Voted 6 months, 3 weeks agodoode
5 months, 2 weeks agoAlexA1457
Most Recent 4 weeks agoRavn888
1 month, 1 week ago3bfb6df
3 months, 1 week ago