Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Question 1
Which of the following is immutable in Java?
String
StringBuffer
StringBuilder
Both B and C
Question 2
What is the key difference between StringBuffer and StringBuilder?
StringBuffer is thread-safe, StringBuilder is not
StringBuilder is synchronized, StringBuffer is not
StringBuffer is immutable, StringBuilder is mutable
StringBuilder consumes more memory than StringBuffer
Question 3
Which of the following will compile successfully?
StringBuffer sb = "Hello";
No, it will not compile
Yes, it will compile
Yes, but with a warning
Only if sb is declared as final
Question 4
Which class should be used when multiple threads need to modify the same string?
String
StringBuffer
StringBuilder
None of the above
Question 5
What will be the output of the following code?
String s1 = "Java";
String s2 = s1.concat(" Programming");
System.out.println(s1);
Java
Java Programming
Compilation Error
Runtime Exception
Question 6
Which of the following methods exists in StringBuffer but not in String?
append()
concat()
charAt()
length()
Question 7
What will be the output of the following code?
StringBuilder sb = new StringBuilder("Hello");
sb.append(" World");
System.out.println(sb);
Hello
Hello World
World
Compilation Error
Question 8
Which is the fastest for string modifications in a single-threaded environment?
String
StringBuffer
StringBuilder
All are equally fast
Question 9
What happens if multiple threads try to modify a StringBuilder instance?
It will throw a ConcurrentModificationException
It may cause unexpected results due to lack of synchronization
It will execute sequentially
It will behave the same as StringBuffer
Question 10
What will be the output of the following code?
StringBuffer sb1 = new StringBuffer("Java");
StringBuffer sb2 = sb1;
sb1.append(" Programming");
System.out.println(sb2);
Java
Java Programming
Compilation Error
Runtime Exception
There are 10 questions to complete.