Comp90015 - Statistics

Jump to: Answer Stats | Score Distribution | Your Scores

General Stats

This quiz has been taken 3 times
The average score is 0 of 125

Answer Stats

Hint	Answer	% Correct
Transparency Expecations	Access	0%
	access control	0%
	addname	0%
Microkernel provides these basic abstractions	Address space	0%
	arbitrary	0%
	Asynchronicity	0%
	at least once	0%
	at most once	0%
	Availability	0%
	availability	0%
	block	0%
	broken passwords	0%
	Checksum	0%
	Client	0%
Architectural Models	Client-server	0%
	cluster	0%
	commit	0%
	communication	0%
Components of RPC system	Communication	0%
	Communication Manager	0%
Benefits of Threads \| Consequences of using DS	Concurrency	0%
Possible failures in UDP	Data corruption	0%
	Data types	0%
	delayed-write	0%
	device	0%
Modules in a file system (DFS)	directory	0%
	Dispatcher	0%
XML > JSON	Displayable	0%
	distributed message queue	0%
	distributed shared memory	0%
	DOS	0%
attack types	eavesdropping	0%
Reasons to use DS	Economy	0%
worst case assumptions	exposed interface	0%
Threads in java	Extend Thread	0%
	Failure	0%
	file	0%
	file access	0%
	getnames	0%
	Global Clock	0%
	Heterogeneity	0%
	idempotent	0%
	Implement Runnable	0%
	insecure network	0%
	integrity	0%
Navigation types	iterative	0%
threat categories	leakage	0%
	Location	0%
directory service operations	lookup	0%
	masquerading	0%
invocation semantics	maybe	0%
	Mechanism	0%
	Memory Manager	0%
	mobile agent	0%
	Mobility	0%
	Modularity	0%
	multicast	0%
OS-level concurrency	Multitasking	0%
Application-level concurrency	Multithreading	0%
	multi-tier	0%
thread life cycle	new	0%
	Non-blocking	0%
	non-recursive server	0%
	non-runnable	0%
Types of failures	omission	0%
	Omission failure	0%
	Order	0%
What does DOS share that NOS does not?	OS	0%
	p2p	0%
	Performance	0%
OS basic components	Policy	0%
Security goals	privacy	0%
OS Components	Process Manager	0%
	proxy server	0%
Indirect communication systems	publish subscribe	0%
	Reactive UI	0%
	Readable	0%
caching strategies	read-ahead	0%
	recursive server	0%
	Reliability	0%
Components of RMI system	Remote interface	0%
	replaying	0%
Failure mitigations	Replication	0%
Remote invocation protocols	Request	0%
	Request-Reply	0%
	Request-Reply-Acknowledge	0%
	resourced attacker	0%
	runnable	0%
	running	0%
	Scalability	0%
	Scaling	0%
	Servant Component	0%
	Server	0%
	Server stub	0%
JSON > XML	Simpler	0%
	source code available	0%
	space uncoupling	0%
How is FFS different from UNIX	stateless	0%
	Stub procedure	0%
	Supervisor	0%
	Supports arrays	0%
	tampering	0%
	TCP	0%
	terminated	0%
	thin client	0%
	Thread Manager	0%
	Thread per connection	0%
	Thread per object	0%
	Thread per request	0%
	threads	0%
Aspects of indirect communication	Time uncoupling	0%
	timing	0%
	tuple space	0%
	two-tier	0%
Socket Protocols	UDP	0%
	unname	0%
Kernel modes	User	0%
	vandalism	0%
	web applet	0%
Thread Architectures	Worker pool	0%
Caching policy options	write-through	0%