Skip to content

Latest commit

 

History

History
738 lines (568 loc) · 25.9 KB

angular-quiz.md

File metadata and controls

738 lines (568 loc) · 25.9 KB
Raw

Angular

Q1. What is the purpose of the ViewChild decorator in this component class?

@Component({
    ...
    template: '<p #bio></p>'
})
export class UserDetailsComponent {
    @ViewChild('bio') bio;
}
  • It provides access from within the component class to the ElementRef object for the <p> tag that has the bio template reference variable in the component's template view.
  • It indicates that the <p> tag be rendered as a child of the parent view that uses this component.
  • It makes the <p> tag in the template support content projection.
  • It makes the <p> tag visible in the final render. If the #bio was used in the template and the @ViewChild was not used in the class, then Angular would automatically hide the <p> tag that has #bio on it.

Q2. What method is used to wire up a FormControl to a native DOM input element in reactive forms?

  • Add the string name given to the FormControl to an attribute named controls on the element to indicate what fields it should include.
  • Use the square bracket binding syntax around the value attribute on the DOM element and set that equal to an instance of the FormControl.
  • Use the formControlName directive and set the value equal to the string name given to the FormControl.
  • Use the string name given to the FormControl as the value for the DOM element id attribute.

Q3. What is the difference between the paramMap and the queryParamMap on the ActivatedRoute class?

  • The paramMap is an object literal of the parameters in a route's URL path. The queryParamMap is an Observable of those same parameters.
  • The paramMap is an Observable that contains the parameter values that are part of a route's URL path. The queryParamMap is a method that takes in an array of keys and is used to find specific parameters in the paramMap.
  • paramMap is the legacy name from Angular 3. The new name is queryParamMap.
  • Both are Observables containing values from the requested route's URL string. The paramMap contains the parameter values that are in the URL path and the queryParamMap contains the URL query parameters.

Q4. Based on the following usage of the async pipe, and assuming the users class field is an Observable, how many subscriptions to the users Observable are being made?

<h2>Names</h2>
<div *ngFor="let user of users | async">{{ user.name }}</div>
<h2>Ages</h2>
<div *ngFor="let user of users | async">{{ user.age }}</div>
<h2>Genders</h2>
<div *ngFor="let user of users | async">{{ user.gender }}</div>
  • None. The async pipe does not subscribe automatically. None.
  • None. The template syntax is not correct.
  • Three. There is one for each async pipe.
  • One. The async pipe caches Observables by type internally.

Q5. How can you use the HttpClient to send a POST request to an endpoint from within an addOrder function in this OrderService?

export class OrderService {
    constructor(private httpClient: HttpClient) { }

    addOrder(order: Order) {
      // Missing line
    }
}
  • this.httpClient.url(this.orderUrl).post(order);
  • this.httpClient.send(this.orderUrl, order);
  • this.httpClient.post(this.orderUrl, order);
  • this.httpClient.post(this.orderUrl, order).subscribe();

Q6. What is the RouterModule.forRoot method used for?

  • Registering any providers that you intend to use in routed components.
  • Registering route definitions at the root application level.
  • Indicating that Angular should cheer on your routes to be successful.
  • Declaring that you intend to use routing only at the root level.

Q7. Which DOM elements will this component metadata selector match on?

@Component({
    selector: 'app-user-card',
    . . .
})
  • Any element with the attribute app-user-card, such as <div app-user-card></div>.
  • The first instance of <app-user-card></app-user-card>.
  • All instances of <app-user-card></app-user-card>.
  • All instances of <user-card></user-card>.

Q8. What is the correct template syntax for using the built-in ngFor structural directive to render out a list of productNames?

  • [ ]
<ul>
  <li [ngFor]="let productName of productNames">{{ productName }}</li>
</ul>
  • [ ]
<ul>
  <li ngFor="let productName of productNames">{{ productName }}</li>
</ul>
  • [x]
<ul>
  <li *ngFor="let productName of productNames">{{ productName }}</li>
</ul>
  • [ ]
<ul>
  <? for productName in productNames { ?>
  <li>{{ productName }}</li>
  <? } ?>
</ul>

Q9. What are the two component decorator metadata properties used to set up CSS styles for a component?

  • viewEncapsulation and viewEncapsulationFiles.
  • There is only one and it is the property named css.
  • css and cssUrl.
  • styles and styleUrls.

Q10. With the following component class, what template syntax would you use in the template to display the value of the title class field?

@Component({
  selector: 'app-title-card',
  template: '',
})
class TitleCardComponent {
  title = 'User Data';
}
  • {{ 'title' }}
  • {{ title }}
  • [title]
  • A class field cannot be displayed in a template via the template syntax.

Q11. What is the purpose of the valueChanges method on a FormControl?

  • It is used to configure what values are allowed for the control.
  • It is used to change the value of a control to a new value. You would call that method and pass in the new value for the form field. It even supports passing in an array of values that can be set over time.
  • It returns a Boolean based on if the value of the control is different from the value with which it was initialized.
  • It is an observable that emits every time the value of the control changes, so you can react to new values and make logic decisions at that time.

Q12. What directive is used to link an <a> tag to routing?

  • routeTo
  • routerLink
  • routePath
  • appLink

Q13. What is the Output decorator used for in this component class?

@Component({
    selector: 'app-shopping-cart',
    . . .
})
export class ShoppingCartComponent {
    @Output() itemTotalChanged = new EventEmitter();
}
  • It makes the itemTotalChanged class field public.
  • It provides a way to bind values to the itemTotalChanged class field, like so: <app-shopping-cart [itemTotalChanged]="newTotal"></app-shopping-cart>.
  • It provides a way to bind events to the itemTotalChanged class field, like so: <app-shopping-cart (itemTotalChanged)="logNewTotal($event)"></app-shopping-cart>.
  • It is simply a way to put a comment in front of a class field for documentation.

Q14. What is the difference between these two markup examples for conditionally handling display?

<div *ngIf="isVisible">Active</div>
<div [hidden]="!isVisible">Active</div>
  • The ngIf is shorthand for the other example. When Angular processes that directive, it writes a div element to the DOM with the hidden property.
  • They are fundamentally the same.
  • The ngIf directive does not render the div in the DOM if the expression is false. The hidden property usage hides the div content in the browser viewport, but the div is still in the DOM.
  • The ngIf is valid, but the use of the hidden property is wrong and will throw an error.

Q15. How can you disable the submit button when the form has errors in this template-driven forms example?

<form #userForm="ngForm">
  <input type="text" ngModel name="firstName" required />
  <input type="text" ngModel name="lastName" required />
  <button (click)="submit(userForm.value)">Save</button>
</form>
  • [ ]
<button (click)="submit(userForm.value)" disable="userForm.invalid">Save</button>
  • [x]
<button (click)="submit(userForm.value)" [disabled]="userForm.invalid">Save</button>
  • [ ]
<button (click)="submit(userForm.value)" [ngForm.disabled]="userForm.valid">Save</button>
  • [ ]
<button (click)="submit(userForm.value)" *ngIf="userForm.valid">Save</button>

Q16. You want to see what files would be generated by creating a new contact-card component. Which command would you use?

  • ng generate component contact-card --dry-run
  • ng generate component contact-card --no-files
  • ng generate component component --dry
  • ng generate component --exclude

Q17. Based on the following component, what template syntax would you use to bind the TitleCardComponent's titleText field to the h1 element title property?

@Component({
  selector: 'app-title-card',
  template: '<h1 title="User Data"> {{titleText}}</h1>',
})
export class TitleCardComponent {
  titleText = 'User Data';
}
  • <h1 data-title="titleText">{{ titleText }}</h1>
  • <h1 title="titleText">{{ titleText }}</h1>
  • <h1 [title]="titleText">{{ titleText }}</h1>
  • <h1 titleText>{{ titleText }}</h1>

Q18. What are Angular lifecycle hooks?

  • loggers for tracking the health of an Angular app
  • providers that can be used to track the instances of components
  • built-in pipes that can be used in templates for DOM events
  • reserved named methods for components and directives that Angular will call during set times in its execution, and can be used to tap into those lifecycle moments

Q19. Pick the best description for this template syntax code:

<span>Boss: {{job?.bossName}} </span>
  • The ? is shorthand for the async pipe. The job value must be an Observable.
  • It is using the safe navigation operator (?) on the job field. If the job field is undefined, the access to the bossName will be ignored and no error will occur.
  • There is an error in the template syntax. The ? is not valid here.
  • It is diplaying the job value if it has one; otherwise it is displaying the bossName.

Q20. How would you configure a route definition for a UserDetailComponent that supports the URL path user/23 (where 23 represents the id of the requested user)?

  • { path: 'user/:id', component: UserDetailComponent }
  • { url: 'user/:id', routedComponent: UserDetailComponent }
  • { routedPath: 'user/:id', component: UserDetailComponent }
  • { destination: new UserDetailComponent(), route: 'user/:id' }

Q21. What are the HostListener decorators and the HostBinding decorator doing in this directive?

@Directive({
  selector: '[appCallout]',
})
export class CalloutDirective {
  @HostBinding('style.font-weight') fontWeight = 'normal';

  @HostListener('mouseenter')
  onMouseEnter() {
    this.fontWeight = 'bold';
  }

  @HostListener('mouseleave')
  onMouseLeave() {
    this.fontWeight = 'normal';
  }
}
  • They are setting the CalloutDirective.fontWeight field based on whether or not the mouse is over the DOM element. The HostListener then sets the font-weight CSS property to the fontWeight value.
  • They are setting up the directive to check the DOM element that it is on. If it has event bindings added for mouse enter and leave it will use this code. Otherwise nothing will happen.
  • This is an incorrect use of HostListener and HostBinding. The HostListener and HostBinding decorators do not do anything on directives; they work only when used on components.
  • If the DOM element that this directive is placed on has the CSS property font-weight set on it, the mouseenter and mouseleave events will get raised.

Q22. What Angular template syntax can you use on this template-driven form field to access the field value and check for validation within the template markup?

<input type="text" ngModel name="firstName" required minlength="4" />
<span *ngIf="">Invalid field data</span>
  • You can make use of a template reference variable and the exportAs feature that the ngModel directive has.
  • You can use the ngModel directive in combination with the input field name.
  • You can use a template reference variable for the HTML input element and then check the valid property off of that.
  • It is not possible to get access to the field value with template-driven forms. You must use reactive forms for that.

Q23. What is the value type that will be stored in the headerText template reference variable in this markup?

<h1 #headerText>User List</h1>
  • an Angular ElementRef, a wrapper around a native element
  • the inner text of the <h1> element
  • a header component class
  • the native DOM element type of HTMLHeadingElement

Q24. What is the difference, if any, of the resulting code logic based on these two provider configurations?

[{ provide: FormattedLogger, useClass: Logger }][{ provide: FormattedLogger, useExisting: Logger }];
  • They are the same. Both will result in a new instance of Logger that is bound to the FormattedLogger token.
  • The useClass syntax tells the injector to make a new instance of Logger and bind that instance to the FormattedLogger token. The useExisting syntax refers to an already existing object instance declared as Logger.
  • Both of them are wrong. A strong type connot be used for useClass or useExisting.
  • They are the same. Both will result in the FormattedLogger token being an alias for the instance of Logger.

Q25. What is the purpose of the data property (seen in the example below) in a route configuration?

   {
       path: 'customers',
       component: CustomerListComponent,
       data: { accountSection: true }
   }
  • a key/value mapping for setting @Input values on the routed component instance
  • a way to include static, read-only data associated with the route that can be retrieved from the ActivatedRoute
  • a property on the route that can be used to load dynamic data for the route
  • an object that will get auto-injected into the routed component's constructor.

Q26. How does the built-in ngIf structural directive change the rendered DOM based on this template syntax?

@Component({
  selector: 'app-product',
  template: '<div *ngIf="product">{{ product.name }}</div>',
})
export class ProductComponent {
  @Input() product;
}
  • The <div> acts as a placeholder. If the product class field is "truthy," the <div> will get replaced by just the product.name value; if not, then nothing will get rendered.
  • The <div> will always be rendered, and if the product field is "truthy," the <div> element will contain the product.name value; otherwise it will render the <div> element with no value in it.
  • It produces an error, since ngIf is not a built-in structural directive.
  • If the product class field is "truthy," then the rendered DOM will include the <div> with the value of the product.name field. If it is not "truthy,' the rendered DOM will not contain the <div> element.

Reference (angular.io)

Q27. What does this code accomplish?

@NgModule({
  declarations: [AppComponent],
  imports: [BrowserModule],
  bootstrap: [AppComponent],
})
export class AppModule {}

platformBrowserDynamic().bootstrapModule(AppModule);
  • It executes a unit test for an NgModule.
  • It provides a way to code the document structure of an Angular application. The @NgModule is a form of inline code commenting that gets ignored by the TypeScript compiler but will show up with special formatting in code editor applications.
  • It declares an Angular module named AppModule and makes it available for lazy loading throughout the application.
  • It declares an Angular module named AppModule that contains a bootstrapped component named AppComponent. Then it registers that module with Angular, so the app can start up.

Q28. Which choice best describes what the resolve property does in this route configuration?

{
   path: ':id',
   component: UserComponent,
   resolve: {
     user: UserResolverService
   }
}
  • Prior to loading the UserComponent, the router will subscribe to the Observable returned by a resolve method in the UserResolverService. This technique can be used to get preloaded data for a route.
  • After the route is done resolving, and the component is loaded and rendered, the UserResolverService will have a method named user run that will clean up any open data connections.
  • There is an error. The correct property name is onResolve.
  • The UserComponent will have a parameter in its constructor for user, and the router will handle injecting in a value for that from a call to a user method in the UserResolverService.

Reference (angular.io)

Q29. What is the purpose of the ContentChildren decorator in this component class?

@Component({
 . . .
 template: '<ng-content></ng-content›'
})
export class TabsListComponent {
 @ContentChildren(TabComponent) tabs;
}
  • If any TabsComponent elements are added to the TabsListComponent template, they will get put into the element at runtime.
  • It creates TabComponent components in the TabsListComponent template when a TabsListComponent is instantiated.
  • It provides access from within the component class to any TabComponent components that were content projected into the for this component.
  • It restricts the allowed elements that can be put into a TabsListComponent element to allow only TabComponent elements.

Reference (betterprogramming.pub)

Q30. In order for Angular to process components in an application, where do the component types need to be registered?

  • within a script tag in the index.html file
  • in an NgModule decorator metadata tag named components
  • No registration is needed simply include the component files in an app directory.
  • in an NgModule decorator metadata property named declarations

Reference (angular.io)

Q31. What is the purpose of the fixture.detectChanges() call in this unit test?

TestBed.configureTestingModule({
  declarations: [UserCardComponent],
});
let fixture = TestBed.createComponent(UserCardComponent);

fixture.detectChanges();

expect(fixture.nativeElement.querySelector('h1').textContent).toContain(
  fixture.componentInstance.title,
);
  • It tracks any potential Ul changes and will fail the unit test if any are made.
  • It is used to ensure component template stability across multiple unit tests in the entire test suite.
  • It forces Angular to perform change detection, which will render the UserCardComponent before you can validate its template.
  • It is used to log change-detection events to the console during unit test runs.

Reference (angular.io)

Q32. What will the URL segment look like based on the following call to the Router.navigate method when goToUser is passed the value 15?

export class ToolsComponent {
 constructor (private router: Router) { }
 goToUser (id: number) {
   this.router.navigate(['user', id]);
 }
}
  • /user/15
  • /user?id=15
  • /user:15
  • /user;id=15

Reference (angular.io)

Q33. When a service is provided for root and is also added to the provider's configuration for a lazy-loaded module, what instance of that service does the

injector provide to constructors in the lazy-loaded module?

  • A new instance of that service is created when the module is lazy loaded.
  • Providing a service of the same type at a lazy-loaded module level is not allowed.
  • If an instance of the service has not been created at the root level yet. it will create one there and then use it.
  • A single instance of that service is always instantiated at root and is the only one ever used, including within lazy modules.

Q34. What is the HostBinding decorator doing in this directive?

@Directive ({
 selector: ' [appHighlight] '
})
export class HighlightDirective {
 @HostBinding('class.highlighted') highlight = true;
}
  • It is adding the CSS class named highlighted to any DOM element that has the appHighlight directive on it.
  • HostBinding does not do anything on directives, only on components.
  • It is specifying if the host element gets the highlighted class added to its class attribute, then the directive class field highlight will get set to true; and if it is not added on the host it will get set to false.
  • It is creating an inline style on the host element with a CSS property named highlight set to true.

Q35. In reactive forms, what Angular form class type is used on the native DOM element to wire it up?

  • FormArray
  • FormControl
  • FormGroup
  • all of these answers

Q36. Assuming the username FormControl has been configured with a minLength validator, how can you set up an error display in the following reactive

forms markup for the username field?

<form [formGroup]="form"›
  <input type="text" formControlName= "username"›
  ...
</form>
  • []
    <span *ngIf="username.minLength.invalid"›
        Username length is not valid
    </span>
  • [ ]
<input type="text" formControlName="username" [showMinLength]="true"›
  • [ ]
    <span *ngIf="form.get('username').getError('minLength') as minLengthError"> 
      Username must be at least {{ minLengthError.requiredLength }} characters. 
    </span>
  • [x]
<input type="text" formControlName="username" #userName="ngModer>
    <span *ngIf="userName.errors.minlength"›
      Username must be at least {{ userName.errors.minlength.requiredLength }} characters. 
    </span>

Q37. How does the emulated view encapsulation mode handle CSS for a component?

  • It renders the CSS exactly how you wrote it without any changes.
  • It makes use of shadow DOM markup and CSS.
  • It creates unique attributes for DOM elements and scopes the CSS selectors you write to those attribute ids.
  • It renders all of the CSS rules you write as inline CSS on all of the DOM elements you use them on in the template.

Q38. With the following TestBed setup, what can be used to access the rendered DOM for the UserCardComponent?

TestBed.configureTestingModule({
 declarations: [ UserCardComponent ]
});
let fixture = TestBed.createComponent(UserCardComponent);
  • fixture.componentTemplate
  • fixture.getComponentHtml()
  • fixture.nativeElement
  • fixture.componentInstance.template

Q39. Given these two components, what will get rendered to the DOM based on the markup usage?

@Component({
 selector: 'app-card',
 template: '<h1>Data Card</h1><ng-content></ng-content>'
})
export class CardComponent { }

@Component({
 selector: 'app-bio',
 template: '<ng-content></ng-content>.
})
export class BioComponent { }

// markup usage:
<app-card><app-bio>Been around for four years.</app-bio></app-card>
  • [ ]
 <app-card>
  <h1>Data Card</hl>
  <app-bio>
   Been around for four years.
  </app-bio> 
 </app-card>
  • [ ]
<h1>Data Card</h1>
 <app-bio>
  Been around for four years. 
 </app-bio>
  • [ ]
<app-card>
  <h1>Data Card</hl>
  <ng-content></ng-content>
  <app-bio>
   Been around for four years.
   <ng-content></ng-content>
  </app-bio> 
</app-card>
  • [ ]
<app-card>
  <h1>Data Card</hl> 
</app-card>

Q40. Given the app-title-card component in the code below, what DOM will the app-user-card component render?

@Component({
   selector: 'app-user-card',
   template: '<app-title-card></app-title-card><p>3enny Smith</p>'
})

@Component({
   selector: 'app-title-card', 
   template: '<h1>User Data</hl>'
})

// usage of user card component in parent component html 
<app-user-card></app-user-card>
  • [ ]
<app-user-card>
    <app-title-card>
     <h1>User Data</h1> 
    </app-title-card> 
    <p>genny Smith</p>
</app-user-card>
  • [ ]
<h1>User Data</h1> 
<p>Jenny Smith<p>
  • [ ]
<app-user-card>
    <app-title-card></app-title-card> 
</app-user-card>
  • [ ]
<div app-user-card>
    <h1 app-title-card>User Data</h1> 
    <p>Jenny Smith</p>
</div>

Q41. Pick the matching code for the custom provider registration that the @Inject () decorator is looking for:

constructor(@Inject('Logger') private logger) { }
  • [ ]
providers: [ 
    Logger
]
  • [ ]
providers: [
    { provide: 'Logger', useClass: Logger }
]
  • [ ]
@Injectable({ 
    providedln: 'root'
})
  • [ ]
providers: [
    { provide: 'Logger' }
]

Q42. Which choice best describes the following usage of the HttpClient . get method in the getsettings class method?

export class SettingsService {  
    constructor(private httpClient: HttpClient) { }
    ...

getSettings()
{
    return this.httpClient.get < Settings > (this.settingsUrl)
        .pipe(
            retry(3)
        );
}}
  • The RxJs pipe method is an alias for the subscribe method, so a call to getSettings will execute the get query. The retry operator is used to tell
    the pipe call to retry the get query three times.
  • It will produce an error at runtime because the pipe method is not available off of the Httpclient.get call.
  • Every single call to the getSettings method will result in the Httpclient making three total get requests to the settingsUrl, which is not ideal
    because there will always be two extra calls that are not needed. The retry operator should not be used in this manner.
  • When the result of the getSettings method is subscribed to, the HTTP GET call will be made; if it fails, it will be retried up to three times before it gives up and returns an error.