• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

scwcd companion question

 
Ranch Hand
Posts: 380
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What is the effect of this declaration?

I answered : A & C
The book says : C & D

Why it should not be D : Because it is restricting PUT and DELETE for specific resources with the file path in it and not ALL Resources.

Or is the language used ambigious???

Regards,
Shivani
 
Author
Posts: 836
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's a subtle point in the language: option A says that this constraint prevents any PUT or DELETE operations from occuring [end of statement]. However, this isn't true, because any user authenticated under the 'admin' role can use PUT and DELETE operations and they will be successful (this is the correct option D). So A is incorrect because it doesn't stop any PUT or DELETE, only those where the user is not in the 'admin' role. Option D is the correct alternative.

I admit the question could have been slightly better phrased, but the answer made it clear to me what was/wasn't true when I re-read it.
 
Consider Paul's rocket mass heater.
    Bookmark Topic Watch Topic
  • New Topic