Discuss SAS A00-260 Exam Topic 13 Question 36

When using the Table Loader transformation to load an existing target table that contains one or more indexes in SAS Data Integration Studio, which statement is true?

AIndexes are removed when the Table Loader executes and must be re-created using the Table Structure transformation.

BIndexes are automatically preserved when the Table Loader executes.

CIndexes are removed at the beginning of the load process and must be re-created in a subsequent job step.

DIndexes can be removed or preserved at the beginning of the process depending on options chosen. Additional table loader options specify whether to re-create the index at the end of the process.

Suggested Answer: C

Get Premium A00-260 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

37 comments · newest first

Avery 12 months ago

I agree with D too! Flexibility is key in these processes.

Beckie 12 months ago

Wait, are you guys serious? I thought indexes were always dropped!

Marisha 1 year ago

I’m leaning towards C, but I’m not 100% sure.

Crista 1 year ago

No way, it’s definitely option B! Indexes should stay intact.

Paris 1 year ago

I think option D is correct. It covers all bases.

Eden 1 year ago

I believe the correct answer is that indexes can be preserved or removed based on the options we choose in the Table Loader.

Dominga 1 year ago

I’m a bit confused about whether indexes are removed at the start or if they stay intact. I need to double-check that.

Millie 1 year ago

I feel like we practiced a question similar to this, and it mentioned that indexes could be removed depending on the options selected.

Gracia 1 year ago

I think I remember that indexes are preserved automatically, but I'm not entirely sure if that's always the case.

Tyisha 1 year ago

This seems like a classic event-driven integration pattern. The key details are that Salesforce is capturing the order details, and the remote system needs to be notified to process the order. I think the "Fire and Forget" option is the best fit here.

Brandee 1 year ago

Hmm, I'm a bit confused by the ACI Cobra SDK part. I'll need to review my notes on that before I can confidently answer this question.

Renato 1 year ago

This question seems straightforward - I think the correct answer is A, which covers the key elements of IS strategy like planning, organizing, and controlling information applications.

Celia 1 year ago

The combination of BlazingText in Batch Skip-gram mode with an RNN sounds interesting. It might enhance capturing sequential context, but isn't that more complex than necessary?

Jolene 2 years ago

I once accidentally removed all the indexes on a production table. Took me weeks to fix that mess. D is the way to go, no doubt.

Allene 1 year ago

↳ replying to Jolene

It's definitely a relief to know that there are options to choose whether to remove or preserve the indexes.

Annabelle 1 year ago

↳ replying to Jolene

I learned my lesson the hard way, never again will I forget to preserve the indexes.

Denise 1 year ago

↳ replying to Jolene

I always make sure to double check my options before running the Table Loader transformation.

Tegan 2 years ago

Ha! Removing the indexes and then having to re-create them? What a pain! I'm going with D for sure.

William 1 year ago

↳ replying to Tegan

User1: Same here, it just makes the process smoother.

Patrick 1 year ago

↳ replying to Tegan

User3: I always go with option D in that case.

Gerald 1 year ago

↳ replying to Tegan

User2: Yeah, it's definitely easier if you can choose whether to remove or preserve them.

Catarina 1 year ago

↳ replying to Tegan

User1: I agree, having to re-create indexes sounds like a hassle.

Quinn 1 year ago

↳ replying to Tegan

D is definitely the way to go to manage indexes effectively in the Table Loader transformation.

Justine 1 year ago

↳ replying to Tegan

I always choose D when dealing with indexes in SAS Data Integration Studio.

Luann 1 year ago

↳ replying to Tegan

I think D is the most efficient choice when using the Table Loader transformation.

Mozell 1 year ago

↳ replying to Tegan

I agree, it can be a pain to have to re-create indexes. D seems like the best option.

Katheryn 2 years ago

B is tempting, but I'm not sure I trust that the indexes will be automatically preserved. I think D is the safer bet.

Vonda 1 year ago

↳ replying to Katheryn

User1: It's always better to be safe than sorry when it comes to preserving indexes.

Alesia 1 year ago

↳ replying to Katheryn

User3: I always prefer to have more control over the process, so D makes sense to me too.

Marjory 1 year ago

↳ replying to Katheryn

I think so too, let's go with D.

Jerrod 1 year ago

↳ replying to Katheryn

I agree, D seems like the safer option.

Darnell 1 year ago

↳ replying to Katheryn

User2: Yeah, I think it's better to have control over whether the indexes are removed or preserved.

Tamesha 2 years ago

↳ replying to Katheryn

User1: I agree, D seems like the safer option.

Alease 2 years ago

I'm not sure, but I think A is also a possibility. Indexes might need to be re-created after the Table Loader executes.

Hobert 2 years ago

Option D sounds like the best choice here. I want to preserve my indexes, but also have the flexibility to re-create them if needed.

Beatriz 2 years ago

I agree with Mira, D seems like the most flexible option for handling indexes during the loading process.

Mira 2 years ago

I think the answer is D, because you can choose whether to remove or preserve indexes in the Table Loader.

SAS A00-260 Exam - Topic 13 Question 36 Discussion